A free card test is a format check. It confirms that a card number passes the Luhn checksum, that the first six to eight digits map to a real issuing bank and card network, and that the length matches that network's rules. It does not contact an issuer, does not check a balance, and cannot tell you whether a card is open or funded. Run these tests on published sandbox test numbers or on your own card, never on a card you do not own.
What a free card test confirms
- Checksum validity: the number passes the Luhn formula, so it is not a typo or a random string.
- BIN match: the leading digits belong to a known issuer range for Visa, Mastercard, Amex, Discover, or another network.
- Length and prefix: 16 digits for most Visa and Mastercard numbers, 15 for Amex, 14 for Diners Club.
- Format of expiry and CVV: two digits for month, four for year, three or four digits for the security code.
What a free card test cannot confirm
- Whether the account is open, funded, or frozen.
- Whether the CVV or expiry matches what the issuer has on file.
- Whether the card will pass 3-D Secure or an address verification check.
- Whether a charge will authorize for any amount.
Any free tool that claims to check live balances or CVV data is either a scam, a phishing page, or a front for carding. Close the tab.
Prerequisites
- A test card number from your payment processor's sandbox documentation, or your own card number.
- A sandbox account with a processor such as Stripe, Adyen, or Braintree if you want to test an actual authorization flow.
- A text editor or spreadsheet to record which numbers pass and which fail.
How to run a free card test
- Open your payment processor's test card documentation and copy one published test number.
- Paste the number into a free Luhn checker and confirm it returns valid.
- Paste the same number into a free BIN lookup tool and confirm the reported issuer and card type match the documentation.
- Enter the number into your sandbox checkout form with any future expiry date and any three-digit CVV.
- Submit a test charge and read the response code.
- Repeat with a deliberately wrong number, such as one digit changed, and confirm the checker rejects it.
- Log the pass and fail results in your spreadsheet so you can compare gateways.
Where free test numbers come from
Every major processor publishes its own set of sandbox numbers, and they only work in test mode. Stripe's list, for example, includes numbers that always approve, numbers that always decline with a specific reason, and numbers that trigger 3-D Secure. Use the list from the processor you actually integrate with, because decline and 3-D Secure behavior differs between gateways. Generated numbers that pass Luhn are also fine for form validation work, but no gateway will authorize them.
Legal and safety boundaries
Running a card through a validator is legal when the number is a published test number, a number you generated, or your own card. Testing numbers that belong to other people is not a gray area, and it is not what these tools are for. Card networks and the PCI Security Standards Council also prohibit storing the CVV or full track data after an authorization, which is why no legitimate validator will ever ask you to submit a real CVV alongside a real card number. If a site requests both, it is harvesting data.
When a free test is enough
Free format and BIN checks are enough for building checkout forms, writing validation rules, and catching typos before a request leaves the browser. Once you need to know whether a charge will go through, you need a sandbox account with a processor and its test numbers. That is the ceiling of free card testing, and it is a useful ceiling.