Checkout.com Test Card Numbers

How Checkout.com test cards work

Checkout.com test cards work in the sandbox environment (https://{prefix}.api.sandbox.checkout.com) with your sandbox API keys. Never use real card numbers there. The sandbox keeps payments for 30 days, so finish each test flow within that time.

Use any future expiry date (MM/YY or MM/YYYY) and any valid CVV: three digits for Visa and Mastercard, four for American Express. Some cards respond to the amount: 4242 4242 4242 4242 with an amount of 101 returns 20051 (insufficient funds), and cards 5333 1700 0000 0008 and 5318 7730 0000 0008 are approved up to 100.00 and declined above it.

When a 3D Secure test is challenged, you are redirected to a simulator page. Enter the password Checkout1! to complete it.

Decline and error response codes

Each card returns the response code shown. Checkout.com documents more cards per code, including Mastercard versions.

3D Secure 2 test cards

Visa and Mastercard cards per 3DS2 outcome. Checkout.com also lists American Express, Cartes Bancaires and UnionPay cards for each outcome.

Other test triggers

• Amounts: 4242 4242 4242 4242 with amount 101 → 20051 Insufficient funds. 5333 1700 0000 0008 and 5318 7730 0000 0008 → approved up to 100.00, 20051 above.
• CVV results (with 4659 1055 6905 1157 or 5305 4847 4880 0098): CVV 204 → D (did not match), empty → N, 205 → P (not performed), 202 → U (issuer does not support CVV); any other 3-digit value matches.
• AVS results: put Test_A, Test_N, Test_R, Test_U, Test_Y or Test_Z in billing_address.address_line1 (with a ZIP) to get that AVS code.
• Expired card: create an instrument with a past expiry date; the payment returns 20054. Update it to a future date and it returns 10000.
• 3DS not enabled: sending 3ds.enabled: true with a non-enrolled card returns 20150.

Testing Checkout.com payments step by step

1. Create a sandbox account and generate secret and public keys in the Dashboard.
2. Tokenize a card with Frames or Flow, or send the card in the payment request, and pay with an approved card.
3. Repeat with the decline cards to cover the response codes your app maps to messages.
4. Send 3ds.enabled: true with the 3DS cards and complete the challenge with Checkout1!.
5. Test CVV results with 4659 1055 6905 1157 (Visa): CVV 204 does not match, 205 is not checked, 202 is not supported by the issuer.

Common errors and fixes

20150 “Card not 3D-Secure enabled”

You sent 3ds.enabled: true with a card that isn’t enrolled. Use a card from the 3DS table.

Unexpected 20051

Check the amount: some test cards decline above 100.00, and 4242 4242 4242 4242 declines at 101.

Payment missing after a month

The sandbox keeps payments for 30 days.

Sources

Every number on this page was copied from Checkout.com’s official documentation and passes the Luhn check. Checked October 2026; gateways change their test data from time to time, so if a number stops working, check the source:

• Checkout.com docs – Test cards
• Checkout.com docs – Simulate card verification outcomes
• Checkout.com docs – AVS check testing
• Checkout.com docs – Payments testing
• Checkout.com docs – API response codes