Testing

Our sandbox environment provides an excellent opportunity to make sure everything is working perfectly. Sign up for your test account, then use the information on this page to try out your integration before going live.\ Get test account

📘

Data retention
Data is held in sandbox for 7 days before being deleted. Unused accounts are deleted after one month of inactivity.

👍

I've finished testing. How do I go live?
To get started, contact your dedicated sales manager, or get in touch with our sales team.

Test keys

Always use your test keys when testing your integration, this is how we know to link all test payments to your sandbox account. You can find your test keys in our sandbox version of the Hub under your channel settings — test keys use the prefix sk_test and pk_test.

Test card numbers

Genuine card numbers will produce an error in your test environment. To simulate payments, use any of the following test card details provided in the table below.

📘

Expiry date
Use any future expiry date (mm/yy) with our test cards.

Credit cards

🚧

If you use any of the following Visa or Mastercard cards in a 3D Secure payment request, they will default to 3DS 2.0 authentication.

Card typeNumberCVV
Visa4242 4242 4242 4242100
Visa4543 4740 0224 9996956
Mastercard5436 0310 3060 6378257
Mastercard2223 0000 1047 9399299
Mastercard5199 9923 1264 1465010
AMEX3456 789012 345641051
AMEX3782 822463 100051000
DinersClub3012 345678 9019257
Discover6011 1111 1111 1117100
JCB3530 1113 3330 0000100

Debit cards

🚧

If you use one of the cards below to test a 3D Secure payment, it will default to 3DS 2.0 authentication.

Card typeNumberCVV
Visa4658 5840 9000 0001257
Mastercard5000 1866 2234 6654257

Commercial cards

🚧

If you use one of the cards below to test a 3D Secure payment, it will default to 3DS 2.0 authentication.

Card typeNumberCVV
Visa4484 0700 0003 5519257
Mastercard5352 1515 7000 3404100

Non-3DS enabled cards

If you want to test a card payment without 3D Secure authentication, use one of the following cards with a transaction value of 5000 or 5029.

Card typeNumberCVV
Visa4484 0700 0003 5519257
Mastercard5352 1515 7000 3404100

Response codes

Create a payment with the amounts in the table below to simulate and trigger the listed response codes. To use them, just change the amount of your test payment. If you use any other amount, your payment will return as approved (response code 10000).

📘

If an amount contains an x you can replace it with any number of your choosing, for example, xxx05 could be used as 12305.

AmountResponse codeDescription
xxx0520005Declined - Do not honour
xxx1220012Invalid transaction
xxx1420014Invalid card number
xxx5120051Insufficient funds
xxx5420087Bad track data
xxx6220062Restricted card
xxx6320063Security violation
999820068Response received too late / timeout
xxx150
(3D Secure payments only)
20150Card not 3D Secure enabled
6900
(3D Secure payments only)
20150Unable to specify if card is 3D Secure enabled
5000 - 5029
(3D Secure payments only)
201533D Secure system malfunction
6510 / 6520 / 6530 / 6540201543D Secure Authentication Required
xxx3330033Expired card - Pick up
400140101Payment blocked due to risk
400840108Gateway Reject – Post code failed
2011200R1Issuer initiated a stop payment (revocation order) for this authorization
2013200R3Issuer initiated a stop payment (revocation order) for all payments
🚧

Testing the 2011 and 2013 amounts
When testing the amounts 2011 and 2013, the response codes 200R1 and 200R3 will only be returned on the first attempt. Additionally, if multiple attempts are made using a non-Visa credit card, this will lead to the card being locally blacklisted. You will need to whitelist it via the risk settings.

Bypassing the response codes

You can turn off this feature so that the payment will be approved no matter which amount is provided. To do so, simply set the card's expiry date to 01/2099.

📘

Please note:

Response codes related to 3D Secure (xxx150, 6900, and 5000 - 5029) will not be bypassed.

Address Verification Service (AVS) check

You can simulate various AVS checks by including any of the following values in address_line1 of billing_address in a payment request.

Address line 1AVS checkDescription
Test_AAStreet Match
Test_BBStreet Match Postal Not Verified
Test_CCStreet and Postal Not Verified
Test_DDStreet and Postal Match (D-Int'l only)
Test_EEAddress Match Error
Test_FFStreet and Postal Match (U.K. only)
Test_GGNot Verified or Not Supported (Int'l only)
Test_IIStreet and Postal Not Verified (Int'l only)
Test_MMStreet and Postal Match (M-Int'l only)
Test_NNNo Address Match
Test_OOAVS Not Requested
Test_PPStreet Not Verified Postal Match
Test_RRAVS Not Available
Test_SSAVS Not Supported
Test_UUMatch Not Capable
Test_WW9 Digit Postal Match
Test_XXStreet and 9 Digit Postal Match
Test_YYStreet and 5 Digit Postal Match
Test_ZZ5 Digit Postal Match
Test_AE1AE1Cardholder Name Incorrect but Postal/ZIP Match (Amex Only)
Test_AE2AE2Cardholder Name Incorrect, but Street and Postal/ZIP Match (Amex Only)
Test_AE3AE3Cardholder Name Incorrect, but Street Match (Amex Only)
Test_AE4AE4Cardholder Name Match (Amex Only)
Test_AE5AE5Cardholder Name and Postal/ZIP Match (Amex Only)
Test_AE6AE6Cardholder Name, Street and Postal/ZIP Match (Amex Only)
Test_AE7AE7Cardholder Name and Street Match (Amex Only
📘

Any other value in the address_line1 field will return AVS check S.

CVV check

You can simulate various CVV checks by including any of the following values as the card CVV in a payment request.

Card's CVVResponse codeCVV checkDecription
20120087XNo CVV2 information available.
20220087UThe Issuer has not certified, or has not provided the encryption keys, to the interchange.
20320087PCard Verification not performed, CVD was not on the card. Not all cards have a CVD value encoded.
20420087DCard Verification was done and CVD was invalid
20520087NAuthorising entity has not attempted card verification or could not verify the CVD due to a security device error.
Valid CVV10000 (if other information is valid)YCard Verification was done and CVD was valid.
Empty CVV10000 (if other information is valid)--An empty CVV value will only be accepted if 'CVV Optional' is enabled for the merchant account.\ Find out more

3D Secure

When simulating a 3D Secure (3DS) payment, you will receive a redirect URL to a 3DS Authentication simulator page. The password for the 3DS simulator is Checkout1!.

3DS test cards

By default, the simulator will return a successful authentication response. If you want to test a different flow or transaction status, use one of the card numbers below in your authentication request.

Frictionless flow

DescriptionCard numberCVVCard type
Authentication successful4485 0403 7153 6584100Visa
5588 6861 1642 6417100Mastercard
Not authenticated4539 6283 4711 7863100Visa
5309 9617 5546 4047100Mastercard

Challenge flow

DescriptionCard numberCVVCard type
Authentication successful4573 8231 6871 0907100Visa
4242 4242 4242 4242100Visa
5385 3083 6013 5181100Mastercard
Not authenticated4243 7542 7170 0719100Visa
5258 9015 0774 1160100Mastercard

3DS 1.0 fallback

DescriptionCard numberCVVCard type
Card not enrolled4484 0700 0003 5519257Visa
5352 1515 7000 3404100Mastercard

Chargebacks

You can simulate a chargeback by using the following payment methods and corresponding amounts in a payment request. Any of the test card numbers listed here will work.

Payment methodAmountReason code triggeredChargeback reason
Visa10.410.4Fraudulent
Mastercard48.554855Product / service not received
Amex45.164561Unrecognized

Testing alternative payment methods

To test the below alternative payment methods, please follow the links to the methods' testing details.

Cards

Wallets

Cash and ATM payment

Bank transfers

Direct debit

Can we help?

Thanks for using Checkout.com. If you need any help or support, then message our support team at [email protected].