Loading...
Start the authentication process by confirming the available mechanisms to authenticate the payer based on a payment method. Availability of this feature in production depends on your allowed live configuration. Please contact Global Payments before coding this feature to confirm it will be available to you when you go live.
Bearer access token value used to authorize and access the API. Must always begin with the string "Bearer".
Integrator generated value submitted in the request header that is checked to ensure the same value has not been seen in the last 24 hours. It is used to ensure idempotency is maintained with this action.
The version of the API to execute the request.
Format of the message body.
A meaningful label that better identifies the account.
Describes whether the transaction was processed in a face to face(CP) scenario or a Customer Not Present (CNP) scenario.
CP - A Customer Present transaction is when the payer and the merchant are in direct face to face contact when exchanging payment method information to fulfill a transaction. e.g. in a store and paying at the counter that is attended by a clerk.CNP - A Customer NOT Present transaction is when the payer and the merchant are not together when exchanging payment method information to fulfill a transaction. e.g. a transaction executed from a merchant's website or over the phoneThis is the country the merchant is domiciled in. For example, if the merchant is based in Canada it must be set to CA. if the merchant is based in England it must be set to GB. if the merchant is based in USA it must be set to US. The country in ISO-3166-1(alpha-2 code) format.
The amount to transfer between Payer and Merchant for a SALE or a REFUND. It is always represented in the lowest denomination of the related currency. and with no decimal point. Note for European merchants: This field is mandatory for SCA.
The currency of the amount in ISO-4217(alpha-3).
Merchant defined field to reference the authentication.