Card Validator

Credit Card Number Validator

Paste card numbers, one per line, to check whether they are correctly formed. Results show only masked numbers. A passing check does not prove that a card exists, is active or can be charged.

Back

1. Card numbers

Syntax only · nothing is sent

Only enter card numbers — never a CVV, expiry date, PIN, name or address. A passing Luhn check does not prove a card exists, is active, has funds or can be used for payment.

2. Results

Masked numbers only
0Total
0Valid
0Invalid
0Duplicates
0Empty lines
Enter one card number per line, then press Validate.
Card number results (masked)
LineNumber (masked)ResultLikely networkDetails

About this tool

About Credit Card Number Validator

Credit Card Number Validator checks whether card numbers are correctly formed, one at a time or in bulk. For each line it checks the allowed characters, normalises spaces and hyphens, verifies the length and the Luhn checksum, and identifies the likely network from published static prefix ranges. Results, copies and reports only ever show masked numbers, and nothing is sent or stored.

Typing mistakes in card numbers cause failed payments and support requests. Checking the format first — for example when testing a checkout form or cleaning test data — catches mistyped or swapped digits instantly. Because the check is purely mathematical and local, no payment system or card data service is involved.

How to use

Step by step

  1. Paste card numbers, one per line, or press Load test numbers.
  2. Press Validate.
  3. Review the counts and the masked results table.
  4. Use the Show filter to focus on invalid entries or duplicates.
  5. Copy the masked valid or invalid results, or download a CSV or TXT report.
  6. Press Reset to clear everything.
Key features

What it offers

  • Bulk checking with one number per line
  • Allowed-character check with space and hyphen normalisation
  • Length check (12–19 digits) and network-specific lengths
  • Luhn checksum verification
  • Likely network from static prefix ranges
  • Masked numbers only in results, copies and reports
  • Valid, invalid, duplicate and empty-line counts
  • No CVV, expiry, name or other payment details requested
Best practices

Tips for best results

  • Use published test numbers when testing payment forms.
  • Never paste real card numbers into tools or documents you don’t control.
  • Treat a passing result as a format check only — the issuer must authorise any payment.
  • Clear the tool with Reset after use, especially on shared computers.
  • Check the reason given for each invalid line to find typing mistakes.
Benefits

Why people use it

Instant

Catch typos before a payment attempt.

Masked

Full numbers are never shown in results.

Private

No data leaves your browser.

Honest

Clear about what a syntax check can and cannot prove.

FAQ

Common questions

That each entry contains only digits, spaces and hyphens, has 12–19 digits, passes the Luhn checksum, and has a length that fits the network suggested by its first digits.
No. It only means the number is correctly formed. It does not show whether the card exists, is active, has funds, belongs to anyone in particular or can be used for a payment — only the card issuer can confirm that.
From published static prefix ranges — for example 4 for Visa, 51–55 and 2221–2720 for Mastercard, 34 and 37 for American Express. Some ranges overlap between networks, so the result is shown as “likely”.
To protect them. Only the last four digits are ever shown, in the table, copies and downloads. Very short entries show only their digit count.
No. Checks run entirely in your browser. Nothing is uploaded, stored or logged, and the input is cleared on Reset and when you leave the page.
No — and you shouldn’t. The tool only checks the card number, and entries containing other details are rejected.
Yes, with the published test numbers (the Load test numbers button), which pass the Luhn check but are not real cards.
Private by design

This runs entirely in your browser

No file or text you enter here is uploaded. Encoding and decoding happen on your device using native browser APIs — close the tab and nothing remains on a server.

Install Toolisco Add it to your device for offline, one-tap access.