A dummy card number v10 is a versioned list of test card numbers that developers paste into a payment sandbox to check a checkout flow. The digits pass format checks, including the Luhn checksum, but no bank account sits behind them. They work in test mode only, and a live gateway will reject them.

Dummy Card Number V9 Guide: Where to Buy CVV

What is a dummy card number v10?

Test card numbers copy the shape of real cards: 16 digits (or 15 for American Express), a valid issuer prefix, and a correct check digit. The "v10" tag marks the tenth revision of a public list. New revisions add fresh BIN ranges and push expiration dates forward.

Dummy Card Number v8: Safe Payment Testing Guide

The label is informal. No card network ships a product called v10. Developer communities, QA teams, and test data repositories use version numbers to track edits over time.

read more

Do test card numbers have any real value?

No. Every number on these lists is published for free by payment processors. There is no cardholder, no balance, and no card verification value tied to a person.

read more

Selling a test list is selling public data. Using numbers that belong to real cardholders is a federal crime in the US under 18 U.S.C. 1029, and a dummy number cannot stand in for one. A sandbox checks the format. It never moves money.

Which test card numbers do the main processors publish?

Stripe, Braintree, and most gateway vendors post their own lists. The numbers below are the ones most teams memorize.

  • 4242 4242 4242 4242: Visa, approves in Stripe test mode
  • 4000 0566 5566 5556: Visa debit
  • 5555 5555 5555 4444: Mastercard
  • 3782 822463 10005: American Express, 15 digits
  • 6011 1111 1111 1117: Discover
  • 4111 1111 1111 1111: Visa, used by Braintree and other gateways

Each vendor also publishes decline numbers. Stripe uses 4000 0000 0000 0002 for a generic decline and 4000 0000 0000 9995 for insufficient funds. Those let you test failure paths without editing code.

Does a dummy card number pass a Luhn check?

Yes, when the number is built with care. Luhn is a checksum that catches typos and random digits.

  1. Write the digits and start from the rightmost position.
  2. Double every second digit moving left.
  3. If a doubled value is 10 or more, subtract 9.
  4. Add all values together.
  5. If the total ends in 0, the number is Luhn valid.

Most published test numbers are Luhn valid, which is why gateways accept them at the format stage. A random string of digits fails about 90 percent of the time.

How do you generate a test number of your own?

  1. Pick a prefix from a known issuer range, such as 4 for Visa or 5 for Mastercard.
  2. Fill the middle digits with any numbers.
  3. Compute the check digit with the Luhn formula.
  4. Keep the result inside a sandbox key and never a live key.

Open source libraries in Python, JavaScript, and PHP do the math for you. A script that prints 100 numbers takes a few lines.

Why does a dummy number fail on a live checkout page?

A live gateway sends the number to the card network. The network looks for a matching account, finds none, and returns an error. Typical responses include "invalid card number," "card declined," and "do not honor."

Some merchants block known test BINs before the request leaves their server. Others run velocity checks that flag repeated attempts from one IP. Either way, the transaction does not complete.

Common mistakes with test cards

  • Using a live API key instead of a test key, which turns a harmless test into a failed charge attempt.
  • Testing one card brand only. Amex is 15 digits and needs a 4 digit CVV.
  • Assuming sandboxes enforce expiration dates. Test mode skips that check, live mode does not.
  • Hardcoding a test number into production code.
  • Treating a passing test as proof the integration works. Test mode skips fraud checks, 3D Secure, and issuer rules.

How should teams store test card data?

Keep test numbers in the repo under clear names, such as fixtures or seeds, so nobody confuses them with real data. PCI DSS treats any card number in a production environment as sensitive, and that includes test values pasted into a live database.

Better still, generate numbers at runtime and delete them after the test. A test card sitting in a production log looks like a data breach to an auditor.

FAQ

Can a dummy card number v10 buy anything?

No. There is no account behind it and no funds to move.

Do test cards need a CVV?

Sandboxes accept any three digits, or four for Amex. Some processors tie a specific CVV to a specific response, so read the vendor docs before you script it.

Are dummy card numbers legal?

Publishing or using them in a test environment is legal. Presenting one to a merchant to obtain goods or services is fraud.

What does the "v10" in the name mean?

It is a version label for a list. The number set changes, the concept does not.