A dummy card number is a fake payment card number that a processor publishes for software testing. It matches the format of a real card, passes basic checks such as the Luhn algorithm, and works only in a sandbox or test mode, so it can never charge an account. The "v10" in dummy card number v10 usually marks the tenth revision of a test data set or the tenth batch in a published list of sample numbers, not a separate card product.
What makes a number a dummy card number
Test numbers are built to imitate real card data closely enough that a checkout form accepts them, while staying disconnected from any live account. The usual traits are:
- Correct length and prefix for the brand being simulated, such as a 16 digit Visa style or 15 digit Amex style sequence.
- A valid Luhn checksum, so client side validation does not reject the entry before the request reaches the gateway.
- Recognition only inside a provider's test environment, which runs on separate endpoints from production.
- No linked account, so a live authorization attempt returns a decline rather than a charge.
Why "v10" shows up in the name
Test data gets maintained the same way other developer assets do. When a processor adds new decline scenarios, updates a card brand's rules, or retires an old sample, the list is reissued with a new revision label. A file or page called dummy card number v10 is simply the tenth version of that working set. Version labels help QA teams confirm that two testers are running the same scenarios and comparing the same expected results.
Where dummy card numbers come from
Legitimate test numbers are published by the payment companies themselves. Stripe, PayPal, Braintree, Adyen, and Worldpay all maintain developer documentation that lists sample numbers along with the response each one triggers. Those pages also explain which expiration dates, CVV values, and postal codes the sandbox expects, because test environments often accept any future expiry date while rejecting a mismatched security code on purpose.
How to use a dummy card number in a test flow
- Confirm the integration is pointed at the provider's test keys and sandbox endpoints, not live credentials.
- Pull the sample number from that provider's own documentation so the expected result is documented.
- Pair the number with the test expiry and CVV rules the provider lists, then run a successful authorization.
- Repeat with the decline samples to check that error messaging, retries, and order states behave as designed.
- Keep test records out of production reporting and never copy sandbox data into a live database.
What dummy numbers cannot do
A test number cannot purchase anything, verify a real account, or unlock a service. Sending one to a live gateway produces a decline, and repeated attempts can trip fraud monitoring on the merchant side. Test cards exist to exercise code paths, nothing more.
Why real card data is not a substitute
Using a real card number or CVV that belongs to someone else, with or without a purchase, is card fraud and is illegal in the United States and most other countries. Buying or selling card data is a criminal offense as well. PCI standards also require merchants to keep real card data out of development and test systems, which is exactly why sandbox numbers exist. If a project needs realistic payment behavior, the correct path is a provider's test suite or a tokenized sandbox account, not a live card.
Short FAQ
Does a dummy card number work on any website?
No. It works only in the environment that published it. The same digits will be declined by an unrelated live checkout because no account backs the number.
Is a test card number the same as a prepaid card?
No. A prepaid card holds real funds. A test number holds nothing and is not issued to any person.
Do I need a special account to get test numbers?
You need a developer account with a payment provider. The sample numbers are then listed in that provider's public documentation.