Checkout.com Test Cards — Sandbox Card Numbers

Verified Checkout.com sandbox test cards for 3DS2, decline, AVS, and fraud simulation.

verifiedVerified against Checkout.com documentation April 22, 2026
Official docsopen_in_new

Checkout.com provides a full-featured sandbox environment. Test card numbers simulate specific gateway responses including approvals, declines, and 3DS flows. Use your Checkout.com sandbox API keys for all test transactions.

search

Showing 15 of 15 test cards

Card NumberNetworkScenarioCodeCopy
4242 4242 4242 4242TEST ONLY
Visa
Successful payment — approvedGlobal
4543 4740 0224 9996TEST ONLY
Visa
Successful payment (alternate)Global
5436 0310 3060 6378TEST ONLY
Mastercard
Successful paymentGlobal
3456 789012 34564TEST ONLY
Amex
Successful paymentGlobal
4000 0000 0000 0002TEST ONLY
Visa
Declined — soft declineGlobal
soft_decline
4000 0000 0000 0119TEST ONLY
Visa
Declined — processing errorGlobal
processing_error
4659 1052 4276 7134TEST ONLY
Visa
3DS2 — challenge requiredGlobal
4484 0700 0003 5519TEST ONLY
Visa
3DS2 — frictionless successGlobal
4484 0700 0003 5501TEST ONLY
Visa
3DS2 — authentication rejectedGlobal
authentication_failed
4000 0000 0000 0127TEST ONLY
Visa
CVC — mismatchGlobal
cvv_failure
4000 0000 0000 0028TEST ONLY
Visa
AVS — address mismatchUS
4000 0000 0000 0010TEST ONLY
Visa
Flagged — risk reviewGlobal
4917 3008 0000 0000TEST ONLY
Visa
Successful — high value transactionGlobal
5425 2334 3010 9903TEST ONLY
Mastercard
Successful payment (alternate MC)Global
4000 0000 0000 1091TEST ONLY
Visa
Declined — blockedGlobal
blocked

TEST ONLY. These numbers will not process real transactions. Use only in Checkout.com's sandbox environment with test API credentials.

What it does

15 verified test cards

Covers Visa, Mastercard, and Amex with success, decline, and 3DS2 scenarios.

3DS2 challenge and frictionless

Dedicated cards for challenge-required, frictionless success, and authentication-rejected 3DS2 flows.

Fraud and risk review

A card that triggers Checkout.com's risk engine review flow.

CVC-specific

Use CVV 100 with the primary success card (4242...) as documented.

How to use Checkout.com Test Cards — Sandbox Card Numbers

  1. 1
    Create a Checkout.com sandbox account

    Sign up at checkout.com, enable sandbox mode, and get your sandbox public and secret keys.

  2. 2
    Use CVV 100 for success card

    The primary test success card (4242 4242 4242 4242) uses CVV 100. Other cards may use CVV 123 or 257.

  3. 3
    Submit via Checkout.com Frames

    Use the test card with Checkout.com Frames.js or the Payments API.

  4. 4
    Inspect the response code

    Checkout.com returns a response_code in the payment response. 10000 = approved, other codes indicate specific failure types.

Checkout.com sandbox response codes

Checkout.com uses numeric response codes. 10000 means the payment was approved. Soft declines return 20005. Hard declines return specific codes in the 20xxx range. The response_code is in the root of the payment response object, and the response_summary field provides a human-readable description.

Frequently Asked Questions

What CVV does the main Checkout.com test card use?

The primary test success card (4242 4242 4242 4242) uses CVV 100 in Checkout.com's sandbox. The alternate success card (4543 4740 0224 9996) uses CVV 956. Check the Notes column for card-specific CVV requirements.

How do I test 3DS with Checkout.com?

Use 4659 1052 4276 7134 (with CVV 123) to trigger a 3DS2 challenge. Checkout.com redirects to a test ACS page where you can complete or fail the authentication.

Related Tools