Start with the sandbox, not the market

If you search for card test data v1 because you need to test a checkout flow, the correct source is your payment processor's developer documentation. Test card numbers are published for sandbox use and cost nothing. They carry no real account behind them, so they cannot be used to move money. A file or service that offers real card numbers, CVVs, or fresh data is not test data. Buying, selling, or using real CVVs is illegal in the United States and most other countries. Legitimate payment testing uses synthetic values that a gateway recognizes and handles in a test environment.

What card test data v1 usually means

Vendors use version labels such as v1 to manage changes in test card sets, error codes, and 3D Secure scenarios. There is no universal card test data v1 standard. One processor's v1 set may include different card brands, decline triggers, and address verification responses than another's. Treat the label as an internal version, not a global specification. Always match the test data to the processor and API version you integrate.

What to look for

  • Official source: test numbers come from the payment gateway or acquirer that will process your live traffic.
  • Card brand coverage: Visa, Mastercard, American Express, Discover, and any local brands you support.
  • Response coverage: approvals, declines, insufficient funds, expired card, incorrect CVV, and address mismatch.
  • Authentication coverage: 3D Secure challenges, frictionless flows, and authentication failures.
  • Data format rules: valid length, Luhn-compliant numbers, accepted expiry formats, and test CVV values.
  • Clear labeling: the set states that it is for sandbox use only and must never be used in production.

Parameter bands to check

Test data sets vary by gateway, but most provide values across these bands:

  • Card number length: 15 digits for American Express, 16 digits for most Visa and Mastercard test numbers, and 19 digits for some alternative ranges.
  • Expiry: future dates for successful authorizations, past dates for expiry failures.
  • CVV: a fixed test value such as 123 or a card-specific value; production CVV rules do not apply in sandbox.
  • AVS ZIP: matching and non-matching postal codes to trigger address verification outcomes.
  • 3DS: enrolled and non-enrolled test profiles to exercise challenge and frictionless paths.
  • Amount triggers: some gateways use specific amounts to force declines or fraud review.

Pitfalls to avoid

  • Using real card numbers in a test environment. This can violate processor terms and data security rules.
  • Storing CVV after authorization. PCI DSS prohibits keeping sensitive authentication data, even if it came from a test profile.
  • Assuming v1 data works everywhere. Test values are processor-specific and API-version-specific.
  • Hard-coding test cards in production code. Keep test credentials and test card data out of live builds.
  • Buying card test data from unofficial sellers. Real card data resold as test data is a fraud risk and a legal risk.

FAQ

Can I buy card test data v1? No. Legitimate test card numbers are free from your payment processor. If someone sells real card numbers or CVVs, that is not test data.

Is a test CVV a real CVV? No. A sandbox CVV is a dummy value that only works in a test environment. It has no connection to a real account.

How often should I update test data? Review it when you change API versions, add card brands, or update 3D Secure rules. Version labels such as v1 may be retired by the vendor.

What if my gateway has no test data? Use the sandbox tools it provides. If none exist, ask the provider for a test merchant account and documented test values.

The bottom line

Card test data v1 is a development aid, not a product to buy on the open market. Get it from the processor you use, keep it in sandbox only, and never mix it with real cardholder data. If a source offers to sell CVVs or live card numbers, walk away and report it. Safe payment testing protects your customers, your business, and your ability to accept cards.