Payment card checksum checker
Check the syntax and Luhn checksum of a card number locally. Results are masked. This does not verify a card, bank or payment.
One number, 13–19 digits and at most 128 input characters. No remote validation, issuer guessing or payment authorization. Output always masks all but the last four digits. A checksum match is not evidence of a usable card. Public test number shown as an example. Enter one 13–19 digit number only. Do not include names, expiry dates or security codes. Up to 128 characters. Results update as you type. Up to 128 characters.
Your result
How to use Payment card checksum checker
- Enter one number using digits and optional spaces or hyphens.
- Review syntax and Luhn as separate results, keeping their limits in mind.
- Download the masked JSON report if needed, then clear the input.
Useful next steps
Check a number's mathematical checksum
Enter one number containing 13 to 19 ASCII digits, with optional spaces or hyphens. The result separates accepted syntax from the Luhn checksum. A failed checksum can indicate a copying error, but this tool does not propose a replacement or generate card numbers.
A checksum match is not card verification
A number can pass Luhn and still be unissued, expired, blocked or declined. This tool does not check a bank, account balance, security code, ownership or authorization. Some payment schemes do not require Luhn. Use a payment provider's documented test numbers when testing software.
Keep sensitive input out of the report
Calculation stays in this browser tab. The number is not saved as a setting or sent in tool analytics. Results and the downloaded JSON report show only the last four digits. Do not enter names, expiry dates or security codes. Use Clear when finished; browser or device features outside the tool may have their own history behavior.