Checkout.com integration guide
Checkout.com is a gateway that allows to you collect card payments. This guide is intended to help you implement Checkout.com based on your preferred integration workflow.
Services and compatibility
Supported payment types |
|
Supported transaction types | |
Supported processing currencies | AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BWP, BYN, BZD, CAD, CDF, CHF, CLP, CNY, COP, CRC, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ETB, EUR, FJD, FKP, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HRK, HTG, HUF, IDR, ILS, INR, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RUB, RWF, SAR, SBD, SCR, SEK, SGD, SHP, SLL, SOS, SRD, SVC, SZL, THB, TJS, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW |
3D Secure 1.x supported | Yes |
3D Secure 2.x supported | Yes |
External 3D Secure supported | Yes |
Installments supported | No |
Gateway-specific information
- Supporting the customer redirect workflow is required. For the 3D Secure Workflow, see 3DS requirements.
- Configuring and utilizing webhooks is necessary as part of the 3DS workflow. For information about webhooks, see the Webhooks topic.
- The security code must be present for the first transaction through CKO, meaning customers with cards on file will need to re-enter the CVV. For documentation about the security code on the first transaction, see Enabling security code verification.
paymentType
is supported.
Configuration
Work with Integrations Support to add Checkout.com as a connection. You will need the following credentials from Checkout.com:
- public key
- private key
Required fields
There are no additional required fields.
If you are having issues with transactions that are rejected by Checkout.com because of potential fraud, include the clientIp
parameter in the payment request and explicitly set the value as the IP address of the device where the customer is submitting the payment information. If you do not explicitly set a value, it looks to Checkout.com as if the exact same IP address is sending out an inordinate amount of traffic and it is not possible to separate out the valid and invalid requests.
Testing data
Use the following test card information to test your Checkout.com configuration.
Brand | Card number | Expiration date | Security code | Cardholder name | 3DS Password | 3DS Result | Transaction Result |
---|---|---|---|---|---|---|---|
Visa | 4242424242424242 | Any future date | 100 | Any | Checkout1! | Success | Success |
Visa | 4242424242424242 | Any | 123 | Any | Checkout1! | Success | Decline |
Visa | 4543474002249996 | Any future date | 956 | Any | None | Success | Success |
Visa | 4543474002249996 | Any future date | 123 | Any | None | Success | Decline |
Mastercard | 5436031030606378 | Any future date | 257 | Any | None | Success | Success |
Mastercard | 5436031030606378 | Any future date | 123 | Any | None | Success | Decline |
Mastercard | 2223000010479399 | Any future date | 299 | Any | Checkout1! | Success | Success |
Mastercard | 2223000010479399 | Any future date | 123 | Any | Checkout1! | Success | Decline |
Mastercard | 5199992312641465 | Any future date | 10 | Any | None | Success | Success |
American Express | 345678901234564 | Any future date | 1051 | Any | N/A | The three DS system appears to be down. Please get a new payment form. | Success |
American Express | 378282246310005 | Any future date | 1000 | Any | N/A | The three DS system appears to be down. Please get a new payment form. | N/A |
Discover | 6011111111111117 | Any future date | 100 | Any | Checkout1! | Success | Success |
Discover | 6011111111111117 | Any future date | 123 | Any | Checkout1! | Success | Decline |
JCB | 3530111333300000 | Any future date | 100 | Any | N/A | The three DS system appears to be down. Please get a new payment form. | Success |
Visa | 4484070000035519 | Any future date | 257 | Any | N/A | N/A | Success |
Mastercard | 5352151570003404 | Any future date | 100 | Any | N/A | N/A | Success |
Status workflows
The status of a successful transaction with Checkout.com varies, depending on the options you choose.
Sale | When isAuthOnly is false , successful sale transactions will have the following statuses:
|
Auth only | When isAuthOnly is true , successful sale transactions will have the following status:
|
Capture | Successful capture transactions will have the following statuses:
|
Void | Successful void transactions will have the following status:
|
Refund | Successful refund transactions will have the following statuses:
|
*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10
, meaning "authorized", in the response when querying transactions (for more information about transactionStatus
, see the appropriate transactionStatus
table).
If you have any additional questions or feedback, contact us.
See also
Updated 15 days ago