Free tool · checked locally
Free Card Number Validator
Check card number format, length, Luhn checksum, and supported card network information directly in your browser.
no account · no credits · no card data sent
Numbers, spaces, and hyphens are supported. Checked locally in your browser.
Your card number is checked locally in your browser. Do not enter CVV, PIN, passwords, or other sensitive payment information.
What is a card number validator?
A card number validator checks whether a payment card number follows the structural rules it should: the digits it carries, the length its network issues, and whether the checksum works out. It answers a question about the number you typed.
That is a different question from whether the card works. Validation never touches an account, so it cannot confirm a balance, an authorization or an identity — it reads formatting, length, checksum and the network a prefix belongs to, and it stops there.
How does card number validation work?
Four steps, all of them local. No step in the sequence needs a server, and none of them asks for anything beyond the number itself.
Normalize
Spaces and hyphens come off so the digits can be read. Nothing is rewritten, and nothing is sent anywhere for this step.
Check the length
The digit count is compared against the lengths card networks actually issue — 15 for American Express, 16 for Mastercard, 13, 16 or 19 for Visa.
Run the Luhn check
The checksum is calculated: double every second digit from the right, subtract nine from anything over nine, and the total must end in zero.
Detect the network
The leading digits are matched against published prefix ranges, which names a network where one applies — and reports an unknown network where none does.
What is the Luhn algorithm?
The Luhn algorithm is a checksum — a way of catching accidental mistakes in long identification numbers. It is the reason a single mistyped digit or a swapped pair is usually caught before anyone tries to charge anything.
- It catches the slips people actually make: one wrong digit, or two digits in the wrong order.
- It is arithmetic over the digits — no lookup, no network, no account involved.
- Passing it means the number is internally consistent.
- It is a checksum on the writing, not a signal about the account.
So a pass means one thing: the number passes the checksum. It does not mean the card is active.
What card networks can be detected?
Detection is prefix matching against published card-number ranges — the numbers below are the ones this tool implements, read from the same rules the checker runs.
Visa
13 / 16 / 19 digits
Mastercard
16 digits
American Express
15 digits
Discover
16 / 19 digits
JCB
16 / 17 / 18 / 19 digits
Diners Club
14 / 16 / 19 digits
UnionPay
16 / 17 / 18 / 19 digits
A prefix that matches no rule comes back as an unknown network — and an unknown network is not an invalid number. Plenty of issuers and regional schemes sit outside these ranges, and no local rule list should pretend otherwise.
Card number validation vs. card verification.
One reads the number. The other needs systems, permissions and data that a free tool has no business touching.
| Check | This free validator |
|---|---|
| Number format | Yes |
| Length | Yes |
| Luhn checksum | Yes |
| Network detection | Where a published prefix matches |
| Cardholder identity | No |
| Card balance | No |
| Card activation status | No |
| Transaction authorization | No |
| CVV verification | No |
| Payment processing | No |
The “No” rows are the scope of the tool, not a list of missing features. None of them can be answered from a number alone.
What does a card number validator not check?
Six questions this tool is often assumed to answer, and the honest answer to each.
Whether the card is active
No. A mathematically valid number may belong to an account that was never issued, is closed, or is frozen. Only the issuer knows which.
The balance
No. A balance is account data held by the issuer. The validator reads the digits you type and reaches nothing else.
Whether a payment would be authorized
No. Authorization is a conversation between a payment processor and an issuing bank. This tool is not part of it.
Who the cardholder is
No. A card number does not identify a person. No structural check turns a number into an identity.
Whether the CVV is correct
No. The CVV exists for the issuer to check during an authorization. This tool never asks for it and could not verify it.
Whether a transaction would succeed
No. A well-formed number can still be declined for a dozen reasons that have nothing to do with how it is written.
use cases
What can you use a card number validator for?
Format-level checks, in the places a mistyped number costs something — with test numbers rather than anyone's real card.
Validating checkout form input
Catch a mistyped digit where the person can still fix it, instead of in a failed payment attempt.
Catching digit-entry errors
The checksum catches the common slips — a single wrong digit, or two digits swapped.
Testing front-end validation
Check which inputs your own form rules accept before you ship them, using test numbers rather than real ones.
Checking imported test data
Confirm the card numbers in a fixture or seed dataset are structurally sound before the tests depend on them.
Validating payment-form formatting
See how a number reads once the separators are removed, and which network the prefix belongs to.
Developer QA
Exercise the accepted lengths and prefixes your payment form has to handle across networks.
Use the published test numbers when you are testing. Never enter someone else’s card number into a tool — including this one — and never use validation to probe whether a real card exists.
Is the card number checked locally?
Yes. The format, length, checksum and network checks run in your browser and do not need to send the card number to the MultiValidator API — or to any other service.
the flow
card number → your browser → normalize → length → Luhn → network → result
- The check makes no network request, so there is nothing to intercept, log or replay.
- The number is not stored — not in localStorage, not in sessionStorage, not in a cookie.
- It is not put into the URL, and it is not included in analytics or error reporting.
- It is not displayed again either: the result panel shows a masked form, and the live region only ever receives that masked form.
- The input does not opt into browser card autofill, so a saved card is not offered into a free tool.
- This tool never asks for a CVV, a PIN, an expiry date, a cardholder name or a billing address — it does not need them.
Never enter your CVV, PIN, password, or other sensitive payment information into this tool.
Need BIN information?
The two are different questions. This free validator checks the number itself — its length, checksum and prefix. A BIN lookup works on the leading digits as an issuing range, and can return the scheme, brand, funding type, country, currency and issuing institution that range belongs to.
Neither one verifies an individual card: a BIN identifies a range shared by every card issued from it, and it performs no authorization.
Card number validator FAQ.
What the checks prove, what they cannot prove, and why the number never leaves your browser.
A tool that checks whether a payment card number follows the expected structural rules: the digits it carries, the length its network issues, and whether it passes the Luhn checksum. It validates the number, not the account.
Related free tools
Each tool checks one layer. To run the full pipeline — MX lookup, live SMTP probe and catch-all detection with a reason and a score — use the API.