A dummy card number v10 is a test card number for payment sandboxes, not a live account. It passes the Luhn checksum and carries a real card network prefix, so a test gateway accepts it and returns a simulated result. No bank is involved, no funds move, and the same number gets declined on any production checkout page.
The "v10" part is a label, not an industry standard. It marks the tenth revision of a list or a generator build. Card networks and payment processors do not certify versions of test numbers.
What Is a Dummy Card Number?
A dummy card number is a string of digits built to look like a bank card while pointing at no account. Developers use it to run checkout flows without touching real customer data. Test numbers come from the processor that runs the sandbox, so a Stripe test card works in Stripe and nowhere else.
- Luhn-valid. The digits pass the checksum every card number must satisfy.
- Prefix-correct. The first six digits match a live issuer range, such as 4242 for Visa.
- Sandbox-bound. The number routes to a simulator, not to a bank.
Does "v10" Mean Anything Official?
No. There is no v10 dummy card number in any published standard. The test-card lists from Stripe, PayPal, and Authorize.net ship without version tags.
The tag shows up in three places:
- Forum and marketplace posts that label each reposted list with a new number.
- Test-data generators that bump a version string with each build.
- Internal test suites where a team versions its own fixture file.
If a page sells a "v10 dummy card number," treat the version as marketing copy. The digits inside are the same public test numbers you can pull from processor docs at no cost.
How Do Test Card Numbers Work?
A test card passes three checks before the gateway simulates a payment. The checks mirror the ones a live transaction runs.
The Luhn algorithm
The Luhn formula doubles every second digit from the right, sums the results, and compares the total against 10. A number that fails Luhn gets rejected at entry. A number that passes is not proof of a real account, which is the gap developers rely on.
Card network prefixes
The first digit or two set the network, and the next few digits set the issuer. Test numbers reuse those ranges so routing code behaves the same way in test mode.
- Visa: 4242 4242 4242 4242
- Visa debit: 4000 0566 5566 5556
- Mastercard: 5555 5555 5555 4444
- American Express: 3782 822463 10005
- Discover: 6011 1111 1111 1117
These come from published processor docs. Each one works in sandbox mode only. Any future expiry date and any three-digit code (four for Amex) will do.
What Can You Test With a Dummy Card Number?
Test numbers cover more than a happy-path approval. Processors ship dedicated numbers that trigger specific responses, and each one returns a known code.
- Approvals and declines (including a card that always fails)
- Insufficient funds and expired card errors
- Refunds, partial refunds, and chargebacks
- 3D Secure authentication prompts
- Recurring billing and subscription renewals
- Currency conversion and address verification (AVS) results
Use one number per scenario so your logs stay readable. Name the fixture after the behavior, not the digits.
Dummy Cards vs Real Cards
- Funding. A dummy card has no account. A real card draws on a credit line or deposit account.
- Scope. Dummy numbers work in one sandbox. Real cards work on live networks.
- Legal status. Test numbers are public and free. Real card data belongs to a cardholder and a bank.
- Criminal value. Zero. A test number cannot buy anything.
Why Buying Card Data Is a Crime
Buying, selling, or trading real card numbers is fraud in the United States and most other countries. U.S. law covers it under 18 U.S.C. § 1029, and penalties scale with the number of accounts and the dollar loss. A test number carries none of that exposure because it is tied to no one.
People sometimes search for a dummy card number v10 hoping to find a working card. That search leads to test data that fails on live sites. The distance between the two is the whole reason test numbers exist.
How to Keep Test Data Clean
- Store fixtures in the repository, not in a shared spreadsheet.
- Label each number with the behavior it triggers.
- Update fixtures when the processor changes its docs.
- Keep real card data out of every test environment, staging included.
FAQ
Do dummy card numbers work on live websites?
No. Live gateways check the issuer and decline the charge. Test numbers work only when the site runs in sandbox or test mode.
Where do I find the right test card for my gateway?
Use the docs for the processor you integrate. Stripe, PayPal, Authorize.net, and Adyen each publish a list with the exact error code each number returns.
Can I create my own dummy card number?
Yes. Start with a valid prefix, pick the remaining digits, then run a Luhn calculator and adjust the final digit until the checksum passes. The result works in any sandbox that accepts Luhn-valid input.
Is it safe to share a dummy card number?
Yes, as long as it comes from a published test set. Never post a real card number, even your own.