An Adyen test CVV is a card verification value used only with Adyen sandbox test card numbers. It does not validate a real card or authorize a live payment; it lets developers test checkout flows without touching live card data.
What an Adyen test CVV is
Adyen calls the card verification value a CVC. In a test environment, the CVC is a fixed value published with a test card number. The sandbox checks the value against Adyen's test data, not against a bank or card issuer. That means a test CVV can help confirm that your payment form sends the CVC field correctly, but it says nothing about a real cardholder.
Test CVVs are not secret credentials and they are not live card data. They belong in sandbox integrations, automated tests, and developer demos. A value that works in test mode will not authorize a production transaction.
Common Adyen test CVV examples
Adyen's published test cards usually pair a test card number with a fixed CVC or CID. Commonly referenced examples include:
- Visa test card 4111 1111 1111 1111: CVC 737
- Mastercard test card 5555 5555 5555 4444: CVC 737
- American Express test card 3700 000000 00002: CID 7373
Confirm the current values in Adyen's test card documentation before you build them into a test suite. Test data can change, and card brand rules can affect which fields are required.
How to use a test CVV in the Adyen sandbox
- Use sandbox API credentials, not live credentials.
- Choose a published test card number and its matching expiry date and CVC.
- Submit the payment through the same integration path you use for production.
- Review the response to confirm success, refusal, or error handling.
- Keep test values out of production configuration and logs.
Why you cannot legitimately buy a real CVV
A live CVV is sensitive authentication data. PCI rules prohibit storing it after authorization, and legitimate payment providers do not sell CVVs. Searches for where to buy a CVV should not lead to a purchase; live card data is not a legitimate product. Using stolen card data is carding fraud and can lead to chargebacks, account termination, and legal exposure.
Testing best practices
- Use only Adyen's documented test cards in sandbox.
- Test CVC missing, invalid, and valid cases.
- Check that your form does not store CVC values.
- Use separate credentials for test and live environments.
- Log response codes, not full card data.