Use the test card numbers published in Adyen's own test card reference, run them against the test environment with a test API key, and choose the number based on the outcome you need to reproduce. A test card is a sandbox instrument. It carries no funds and no cardholder behind it, and it returns only the result that Adyen built into that specific number. Pick the card for the brand and response you are checking, keep live credentials out of the sandbox, and confirm your integration handles declines, 3DS challenges and error responses as carefully as it handles approvals.
What to look for when choosing a test card
- Coverage of every brand you accept. Adyen lists separate numbers for Visa, Mastercard, American Express and the other schemes enabled on your account. A checkout that works for one brand can still break on another because of field length or CVC rules.
- Numbers tied to specific outcomes. The reference includes cards that return an approval, cards that return particular refusal reasons, and cards that trigger a 3D Secure challenge instead of a frictionless flow. Testing only the approved path leaves the interesting half of your code unexercised.
- 3D Secure variants. Adyen documents separate test cards for frictionless authentication, challenge flow and failed authentication. Map each one to the branch of your checkout logic it exercises.
- Recurring and stored payment scenarios. If you support card-on-file or subscription charges, look for test cards that behave correctly across shopper-initiated and merchant-initiated transactions.
- A clear note on what is simulated. Test cards do not touch a real issuer. Anything that depends on issuer behavior, such as some soft declines, will not behave the way it does in production.
Parameter bands worth knowing
- Card number. Use only values from the official reference. Most are Luhn-valid so they pass client-side formatting checks, but a Luhn-valid number you invented will not produce a useful server response.
- Expiry date. Any future date is accepted. Pick one and keep it fixed in your fixtures so test runs stay reproducible.
- Security code. Any three digits work for Visa and Mastercard, four for American Express. Do not build business rules around a specific CVC value.
- Amount. Keep test amounts small and in a currency enabled for your test merchant account. Some flows, including 3D Secure and certain regional methods, behave differently below or above threshold values.
- Environment. Test endpoint, test API key, test merchant account. Mixing any one of these with live values is the most common reason a documented test card appears to fail.
Pitfalls to avoid
- Entering a real card number in a sandbox to see what happens. It violates card network rules and puts cardholder data somewhere it was never meant to live.
- Assuming a decline means your integration is broken. Check the documented result code for that test card before you debug.
- Hard-coding a single test card across every scenario, then declaring the integration complete.
- Leaving test keys or test card defaults in a production configuration file.
- Ignoring the refusal and error paths because the approval path looked clean.
FAQ
Are Adyen test cards real credit cards?
No. They are published sandbox numbers that exist only to produce predictable responses from the test environment.
Adyen Card Check System Guide: Sell CVV Online Safely
Will a test card work against the live environment?
No. Live and test use separate credentials and endpoints, and a sandbox number is rejected outside the sandbox.
Adyen Card Authentication Process
Which test card should I use first?
Start with the standard approval card for your most common brand, then add the 3D Secure challenge card and at least one refusal card to your test suite.
Adyen Card Inspection Guide: Ensuring Security and Compliance
Can I use my own card for testing?
Keep personal cards out of automated tests. Use the documented sandbox numbers so no real cardholder data enters your logs or your test database.