Adyen Card Test Tool: Sandbox Payment Testing Guide

What is the Adyen card test tool?

The Adyen card test tool is the Test environment in your Adyen account paired with Adyen's published list of test card numbers. You send those numbers through the same API requests you use in production, and the platform returns simulated results without moving money. It covers approvals, refusals, 3D Secure challenges, and refunds.

more on this topic

No real card is involved at any point. The numbers are fake, they work only against test endpoints, and Adyen discards the data once the request completes.

Adyen Card Test Utility Guide

Where do you find Adyen test card numbers?

Adyen keeps a reference page in its developer docs titled "Test card numbers." It lists numbers by scheme and by the result each one produces.

adyen card test

• Visa: the docs include the standard 4111 1111 1111 1111 number for a successful authorization.
• Mastercard, Amex, Discover, and regional schemes: separate entries, each mapped to a specific outcome.
• Refusal cards: numbers that return a chosen refusal reason, such as insufficient funds or blocked card.
• 3D Secure cards: enrollment-based numbers that force a challenge or a frictionless flow.

Test numbers change as Adyen adds schemes and result codes. Pull them from the docs when you build a fixture instead of hardcoding a list that sits untouched for a year.

adyen card test tool

How do you run a test payment?

A test payment is a normal /payments call sent to the test endpoint with a test card. Five steps cover the basic flow.

1. Create a test account in the Adyen Customer Area and copy the API key from the Test environment.
2. Send a /payments request to the test URL with paymentMethod.type set to scheme.
3. Pass a test card number, any future expiry date, and a 3 or 4 digit CVC.
4. Read the resultCode in the response: Authorised, Refused, RedirectShopper, or IdentifyShopper.
5. Finish the flow with /payments/details for redirects, then test /captures and /refunds against the PSP reference.

The request shape mirrors production, so code you test here ships with few changes. That is the point of the sandbox: the payload stays the same, only the endpoint and credentials change.

How do you simulate a specific refusal?

Adyen's test card list maps each refusal number to one reason code. Pick the card that matches the failure you want to handle, then read the refusalReason field in the response.

This matters for checkout UX. A soft refusal like insufficient funds should show a retry prompt. A hard refusal like stolen card should end the attempt and hide the card form. Test both paths, not just the happy path.

How do you test 3D Secure?

Send a 3DS-enrolled test card and the response returns an action object instead of a final result. Your integration then renders the challenge or handles the redirect and posts back to /payments/details.

• Challenge flow: the shopper sees an authentication screen. The docs list the credentials to enter on the test challenge page.
• Frictionless flow: the payment returns Authorised with 3DS data attached, and no challenge appears.
• Failed authentication: a separate test card returns a refusal after the challenge, which is the case most integrations forget to build for.

What breaks a sandbox test?

Most failed tests come from environment mismatches, not from bad code. Check these four items first.

• Wrong endpoint: test card numbers sent to the live URL return a refusal or an invalid card error.
• Wrong API key: a live key against the test URL returns a 401.
• Wrong merchant account: the request must name a test merchant account tied to your test company.
• Origin rules: Drop-in and Components need the domain you serve from added to the allowed origins list.

Currency is the fourth trap. Zero-decimal currencies such as JPY take amounts in whole units, so a 10.50 value becomes a validation error that looks unrelated to the card.

Frequently asked questions

Do Adyen test card numbers work in live mode?

No. Test numbers exist only in the test environment and are rejected by live endpoints.

Can I use a real card number in the sandbox?

No, and you should not try. Real card data in a test system creates compliance exposure with no benefit, since the test environment never contacts an issuer.

Why does every test card return Refused?

You are likely pointing at the live endpoint, using a live API key, or naming a merchant account that does not exist in the test company. Verify all three before you debug the payload.

Is the test environment free?

Yes. Adyen does not charge for sandbox transactions because no funds move and no acquirer is involved.