Adyen Card Verification Utility: A Comprehensive Guide
Discover how to effectively use the Adyen Card Verification Utility for secure online transactions.
Adyen Card Test: Test Card Numbers and Sandbox Guide
What is an Adyen card test?
An Adyen card test is a payment run in Adyen's test environment that uses a published test card number instead of a real card. Test cards return predictable results, so you can verify authorization, capture, refund, and error handling without moving money. They work only in test mode and are rejected by the live platform.
Where do you find Adyen test card numbers?
Adyen publishes its test card list in the developer documentation under the testing section. Each entry maps a number to a card brand, an issuing country, and the set of outcomes that number can produce.
- The table covers Visa, Mastercard, American Express, Discover, and several regional brands.
- Commonly cited examples include the Visa number 4111 1111 1111 1111 and standard American Express test numbers that use a four digit security code.
- Lists change over time, so confirm any number against current documentation before you hard code it into a suite.
What details do you need to run a test payment?
A sandbox payment request needs the same fields as a live one, minus a genuine card.
- Card number from the published test list.
- Expiry date in the future, unless the scenario is specifically about expired cards.
- Security code, three digits for most brands and four for American Express.
- Cardholder name and a unique shopper reference so you can trace the result.
Test card numbers do not require funding, a real billing address, or a matching bank account.
How do you trigger a specific payment result?
Adyen ties outcomes to the test number you send and, in some cases, to the transaction amount. Some numbers always authorize, others always return a refusal with a named reason, and a few let you force a challenge or a pending state.
Read the result code and refusal reason in the response body to confirm the flow behaved as expected. Building a small case per outcome keeps regression tests readable.
How do you test 3D Secure and risk rules?
Dedicated test cards let you simulate a frictionless authentication, a challenge that the shopper completes, and a challenge the shopper abandons. This matters because liability shift and the final payment status differ across those paths.
Use the same test shopper across runs so risk rules and velocity checks do not distort your results.
Why do test cards fail in live mode?
Adyen and the card networks block known test numbers in the live environment by design. A test number sent to live will be refused rather than authorized, which is exactly the behavior you want.
If a test card declines in sandbox, check the merchant account configuration, the API version, and whether the number is still on the current list.
Is testing with real card numbers allowed?
No. Sending a real card number into a test environment, or handling any card data you are not authorized to use, breaks card network rules and US federal law under 18 U.S.C. 1029. PCI DSS also forbids storing the security code after authorization, even briefly.
Use only the processor's published test values, and keep production card data inside a compliant, tokenized flow.
Frequently asked questions
Do Adyen test cards need a real security code?
No. Use the security code printed alongside the number in the documentation, or any three digit value for numbers that do not require a fixed code.
Can I reuse one test card for every scenario?
No. Each number is tied to a limited set of outcomes, so most test suites hold a small collection of numbers mapped to the cases they cover.
Do test transactions appear in settlement reports?
No. Test transactions never settle and never appear in live payout or settlement reports.