Loading...
This integration gives you:
ctp-request| Benefit | Description |
|---|---|
| Fast, Frictionless Checkout | Stored cards and scheme-side flows improve UX. |
| Netcetera Manages Click to Pay | Identity, card selection, and 3DS handled by their SDK. |
| Global Payments Handles Auth | You never build auth logic or touch PAN/token. |
| Cleaner Compliance | Less PCI exposure and reduced scope. |
You, as the merchant are responsible for integrating the Click to Pay frontend and ensuring the transaction flow completes. Below are your integration steps.
Use the official SDKs provided by Netcetera:
These SDKs:
ctp-request payload)You never handle raw card details.
The following values are needed to initialize the Netcetera SDK. Some come from you, the merchant; others are provided during Click to Pay onboarding by Global Payments.
| Field | Who Provides It | Purpose |
|---|---|---|
srcInitiatorId | Global Payments | Identifies Global Payments to schemes. Shared across all GP merchants. |
acquirerBin | Global Payments | Used to route the transaction through the scheme. |
merchantName | Merchant | Displayed to cardholders during checkout. |
merchantCountryCode | Merchant | ISO 3166-1 alpha-2 country code (e.g. IE, DE). |
merchantUrl | Merchant | Used for scheme registration and domain binding. |
notificationUrl | Merchant (optional) | For async notifications (if supported). |
srcDpaId | Global Payments (via Netcetera) | SDK init token; specific to the merchant and environment (sandbox/production). |
These values are provisioned and managed behind the scenes — you do not need to configure or request them manually:
threeDSRequestorId: Used in 3DS flows; embedded by Netcetera.After 3DS is completed:
Netcetera generates a signed JWS token (the ctp-request)
This token contains the encrypted payload with all transaction data (PAN/token, ECI, CAVV, 3DS ID, etc.)
Netcetera generates a ctp-request and then hands it back to the payment page, the payment page uses that ctp-request to build an auth-ctp.
You do not need to parse, decrypt, or forward this payload.
Global Payments:
Decrypts the ctp-request
Builds a traditional authorization message (ISO 8583 or internal API)
Sends to the issuer
Returns the result (approved/declined) to you
You’ll receive the final result via:
Your existing API callback
Or as part of your redirect/confirmation page
| Field | Description |
|---|---|
result | Success or failure |
orderId | Your transaction reference |
authCode | Issuer-provided authorization code |
eci, cavv | 3DS authentication values (if requested) |
status | Optional – includes CtP-specific success metadata |
We recommend a full end-to-end test before going live.
| Test Area | What You Do |
|---|---|
| SDK Setup | Use Netcetera sandbox SDK and test config |
| Scheme Testing | Use test cards provided |
| Callback Handling | Ensure you can receive and process final result |