Answer
CVV test data v3 is a set of card verification values published by payment processors for use in sandbox environments. The values pass format checks in test mode. They do not authorize charges and are not linked to real accounts.
What the data contains
Test card sets include a card number, expiry date, and CVV. Processors publish these values so developers can test checkout flows, error handling, and 3-D Secure steps. Stripe, Adyen, and PayPal each publish their own test card tables.
- Card number: 16 digits, test BIN ranges
- Expiry: any future date in test mode
- CVV: 3 digits, test value
Where test values come from
Payment processors publish test card numbers and CVVs in developer documentation. The values are fixed and public. They work only when an account is in test mode. A test CVV sent to a live endpoint fails.
What CVV test data is not
Test CVV values are not real card data. Real CVVs are sensitive authentication data under PCI DSS. PCI DSS Requirement 3.2 prohibits storing the CVV after authorization. A site that sells CVV numbers sells stolen card data. Buying or using that data is card fraud.
Lawful use
- Use test values only in sandbox API keys.
- Keep live and test credentials separate.
- Do not store real CVVs in logs or databases.
- Use processor-published test tables, not data from third parties.
Version labels such as v3 refer to a test data set revision. Confirm the current table in the processor's documentation. Test data sets change when processors add card brands or authentication cases.