Card test data v2 is the second generation of a payment processor's sandbox dataset. It is a set of fake card numbers, expiry dates, and CVV values that produce a chosen result in a test environment: an approval, a specific decline code, or a 3D Secure challenge. Nothing in the set belongs to a real cardholder, and nothing in it can be charged.

Card Test Data V10: Guide on Where to Buy CVV

What the v2 dataset contains

• Primary account numbers that always approve, plus numbers mapped to declines such as insufficient funds, expired card, or do not honor.
• Matching expiry dates and CVV values, because many gateways still validate CVV format in test mode.
• Card brand variants: Visa, Mastercard, American Express, and Discover.
• Network token and wallet samples for recurring billing and digital wallet flows.
• 3DS profiles that force a frictionless pass, a challenge, or an authentication failure.

Prerequisites

• A sandbox or test account with your payment processor.
• Test API keys, kept separate from live keys.
• A staging build of your checkout pointed at the processor's test endpoint.

How to run a test with v2 card data

1. Open your processor's test card reference page and copy the number for the outcome you want to reproduce.
2. Point your application at the sandbox endpoint and load the test API key.
3. Submit a payment using the test number, a future expiry date from the same reference, and the listed CVV.
4. Compare the response object against the documented result for that number.
5. Log the response code, the request payload, and the timestamp.
6. Repeat the run for every decline path your checkout handles.
7. Clear the test data from your database before you promote the build to production.

Reading the results

A v2 test number is a trigger, not a simulation of a real issuer decision. The number you pick decides the response code, so the value of the test is in your handling of that code. A decline test passes when your checkout shows the right message and leaves the cart intact. A 3DS challenge test passes when the redirect returns and the order completes.

card test data v8

What changed between v1 and v2

Older v1 sets covered approvals and basic declines with a fixed CVV. The v2 sets add separate handling for network tokens, wallet payloads, partial approvals, and authentication outcomes. Some processors also split the CVV field into its own sample value so that CVV mismatch codes can be tested without changing the primary account number.

related article

Where the data comes from

Every v2 number is published by the processor or acquirer that maintains the sandbox. Stripe, Adyen, and Braintree each publish their own list, and the lists do not overlap. Use the list published by the company whose API you are calling. A number from another provider will not trigger the same response.

read more

What test data is not

Test card numbers are not interchangeable with real card data. Real primary account numbers, CVVs, and full magnetic stripe data must never appear in a test environment. PCI DSS requires test systems to be isolated from production and to use synthetic data only. Sites that sell real CVVs operate outside the law and outside the card networks. Buying or using one is card fraud, not testing, and a page that mixes "live" CVV listings with test card samples is using the test data as cover.