Adyen Test CVV: Sandbox Card Verification Values

An Adyen test CVV is the card verification value you enter when paying with an Adyen test card number in the sandbox environment. It is fake data tied to a fake card, so no real cardholder account is involved. Most Adyen test cards accept any three-digit CVC, while the Amex test card conventionally uses 737.

What a test CVV is used for

Adyen sandbox test cards let you run payment flows end to end before you go live. Each card number is paired with an expiry date in the future and a CVC value that the sandbox uses to simulate a card verification check. The result tells you whether your integration passes the CVC field correctly to Adyen and whether your application reacts properly when a check succeeds or fails.

Test CVVs are not real security codes. They exist only so developers can reproduce checkout behavior, including the verification step that a live issuer would normally handle.

Which CVC values Adyen test cards expect

Adyen publishes a test card page that lists card numbers, expiry dates, and the CVC to use for each scheme. Common examples from that list include:

• Visa: 4111 1111 1111 1111, with a three-digit CVC such as 737
• Mastercard: 5555 4444 4444 4444, with a three-digit CVC such as 737
• American Express: the test card listed by Adyen, which uses the four-digit code 737

For most schemes, the sandbox does not validate the exact digits, so any three-digit value works. Always confirm the current values on Adyen's own test card reference, because card numbers and expected CVCs can be updated.

Testing CVC and address verification

A gateway can return a CVC result of match, no match, or not checked, depending on what the issuer sends back. In the sandbox, several gateways simulate these outcomes through specific test card numbers rather than through the CVV you type. That means you can verify both sides of your logic:

1. Send a normal test card to confirm the CVC field reaches Adyen and a match result is accepted.
2. Send a test card that returns a CVC mismatch to confirm your code asks the shopper for another attempt or routes the order to manual review.
3. Repeat with an address verification mismatch card to see how your rules combine both results.

Testing declines and other outcomes

Adyen lists separate test cards for refusal reasons such as declined, refused, expired card, and blocked card. Pair each one with the CVC from the reference page and log the full response object. Reading the refusal reason codes during development is faster than guessing once you move to live traffic.

How real CVVs must be handled

Real card verification values fall under PCI DSS as sensitive authentication data. They may be used to authorize a transaction, but they must not be stored after authorization, even in encrypted form. Test CVVs are the only ones you should ever keep in a code repository, log file, or screenshot.

Frequently asked questions

Can I use any CVV with an Adyen test card?

For most schemes, yes. The sandbox accepts a three-digit value, and Amex test cards need the four-digit 737. Use whatever Adyen's test card page specifies for the exact card number you choose.

Do test CVVs work in the live environment?

No. Test cards and their CVCs are accepted only by the sandbox. Live transactions require a real card issued by a bank.

Where do I find the current list?

Adyen's developer documentation hosts the test card table, including card numbers, expiry dates, and CVC values, and it is the source you should check before each integration run.