Click to Pay

This integration gives you:

• Full control over the frontend experience via Netcetera’s SDK.
• Zero responsibility for authorization logic, Global Payments handles that for you.

The only thing you need to do is integrate the SDK into your checkout and register. Global Payments handles everything else.

1. Once onboarded, integrate the Netcetera SDK into your checkout.
2. The customer uses Click to Pay and selects a stored card.
3. Netcetera's SDK handles identity and card selection. Global Payments completes 3DS.
4. Your integration sends an auth-ctp request to Global Payments, built from the data returned by the SDK.
5. Global Payments decodes the request and constructs a standard authorization.
6. Global Payments returns the result to you.

You are responsible for integrating the Click to Pay frontend and ensuring that the transaction flow completes.

Before starting, you must do the following:

• Get registered
• Create an app (generate keys)
• Create an access token

Use the official SDKs provided by Netcetera:

The SDKs do the following:

• Loads the Click to Pay button and scheme-branded UI.

• Handles customer identity and card selection.

• Returns the data needed to build the auth-ctp request.

  You never handle raw card details.

These values are provisioned and managed for you. You do not need to manually configure or request them:

• threeDSRequestorId: Used in 3DS flows embedded by Netcetera.
• DPAID: Global Payments holds a scheme-registered DPAID, with a merchant/environment-specific ID issued underneath it. Both are provisioned and managed by Global Payments.
• 3DS logic: Fully handled by Global Payments. No manual challenge handling is required.

1. Authentication

After 3DS is completed, Global Payments receives an auth-ctp request containing the transaction data (PAN/token, ECI, CAVV, 3DS ID, etc.).

You do not need to parse, decode, or forward this payload.

2. Global payments handles the payment result

Global Payments does the following:

• Decodes the auth-ctp request.
• Builds a traditional authorization message (ISO 8583 or internal API).
• Sends to the issuer.
• Returns the result (approved/declined) to you.

You receive the final result via one of the following:

• Your existing API callback.
• As part of your redirect/confirmation page.

We recommend a full end-to-end test before going live.

1. Register with Global Payments ( Sandbox/Production).
2. Integrate SDK into frontend.
3. Confirm sandbox payment success if needed.
4. Enable CTP on Production.
5. Go live.