Adyen Card Test: Test Card Numbers and Sandbox Setup

An Adyen card test is a payment sent to Adyen's test environment using a published test card number in place of real card data. You swap in a test API key and test client key, send the request, and read the result in the API response or the Customer Area. No money moves and no real cardholder is involved.

Top Adyen Card Verification Utility for Selling CVV Online

Adyen keeps a separate test environment for this work. Its docs publish card numbers for each brand, plus cards that fire specific refusal reasons and 3-D Secure outcomes.

adyen card check

How do you run a card test on Adyen?

The flow mirrors a live payment. The difference is the credentials, the endpoint, and the card number in the request.

Adyen Card Validation Tool: What It Checks and How It Works

1. Log into your Adyen Customer Area and open Developers, then API credentials. Create or open a set of test credentials with the Checkout API role.
2. Copy the test API key. For Drop-in or Components, also copy the test client key. Both start life in test mode and do not work against live traffic.
3. Point your integration at the test endpoint, which uses the prefix checkout-test.adyen.com.
4. Send a /payments request with a test card number, a future expiry date, and the CVC listed next to that card in the docs.
5. Read the resultCode in the response. Authorised means the test payment passed. Refused includes a refusalReason. RedirectShopper means a 3-D Secure challenge is waiting.
6. Confirm the async side by checking the AUTHORISATION webhook that lands on your notification URL.

Each successful test appears in the Customer Area under Payments with a test label. You can capture, refund, and cancel it the same way you would a live payment.

adyen card check

Which test card numbers does Adyen use?

Adyen publishes a set of numbers for the major brands. Use the exact values from the docs rather than numbers copied from a blog post, since the list changes.

• Visa: 4111 1111 1111 1111 is the long-standing test number.
• Mastercard: 5555 5555 5555 4444 covers the standard success case.
• American Express: 3700 0000 0000 002 sits in the Amex test range.
• Refusal cards: a separate group returns fixed reasons such as stolen card, insufficient funds, or expired card.
• 3-D Secure cards: another group forces frictionless, challenge, or challenge-failure flows.

These numbers are public test PANs. They are built to fail in a live authorization and cannot be used to move money.

Do test cards need a real expiry date and CVC?

Yes, the fields still go through validation. Use any future expiry date. Use the CVC printed next to the card in the Adyen docs, because a mismatch returns a CVC refusal, which is itself a useful test case.

How do you trigger specific declines and 3-D Secure flows?

Adyen gives you two levers: the card number and the amount. Certain test cards map to a fixed refusal reason, so the response is predictable every time you run it.

For 3-D Secure, pick a card from the 3DS test set. One card completes without a challenge, one shows the challenge page, and one fails authentication so you can watch your integration handle a Refused result after the redirect.

• Test the full redirect loop, not just the API call, or you will miss bugs in your return URL handling.
• Verify that your webhook handler tolerates duplicate notifications. Adyen retries on a non-200 response.
• Run each scenario twice to catch state that only appears on the second attempt.

What changes when you move from test to live?

Three things change: the credentials, the endpoint, and the meaning of a successful payment.

• Credentials: live API keys and live client keys are separate objects. A test key returns an error against the live endpoint.
• Endpoint: live traffic goes to checkout-live.adyen.com instead of the test prefix.
• Money: a live authorization holds funds on a real card. Test authorizations never settle.
• Payment methods: methods must be enabled on the live merchant account. A method that worked in test can come back as not offered in live.

Keep the two sets of keys apart. Mixing them is the most common reason a test suddenly stops working.

Why is my Adyen test card refused?

Most failures trace back to configuration rather than the card itself.

• The request used live credentials or the live endpoint.
• The expiry date sits in the past.
• The payment method is not enabled on the test merchant account.
• The CVC or card number has a typo, including spaces that the API rejects.
• The shopper interaction or recurring flags do not match the card type.
• The client key is paired with a different origin than the one in your allowed list.

Read the refusalReason and refusalReasonCode fields before you change code. They usually name the problem.

Frequently asked questions

Does an Adyen test payment charge money?

No. Test payments run against the sandbox and never touch a card network. Nothing is captured, settled, or paid out.

Can I use my real card in the test environment?

Do not. Sandboxes are not built to hold real cardholder data, and PCI DSS rules treat any real PAN outside a compliant live flow as a problem. Use the published test numbers only.

Do test payments appear in payouts and reports?

They appear in the Customer Area as test transactions, but they stay out of settlement and payout reports. If you need clean reconciliation figures, filter test traffic out of your own reporting.

How long do test payments stay visible?

Test transactions are kept for a limited window and then cleared. Anything you need long term should be exported rather than left in the dashboard.

Can I automate Adyen card tests?

Yes. Point a test suite at the sandbox with a test API key and assert on resultCode and refusalReason. Keep the test cards in config, and run the suite against a fresh merchant account before each release.