JWT Verifier
Check a JWT signature against a secret or a public key, and see why it fails.
Generate Luhn-valid test card numbers that no processor will ever charge.
These pass a checksum and correspond to no account anywhere. No processor will authorise one. For a payment gateway sandbox, use the numbers that gateway documents — they trigger specific decline paths.
The Test Credit Card Generator produces Luhn-valid numbers using the prefixes each scheme reserves for testing, with a matching CVV and expiry — numbers that pass a form’s validation and that no processor will ever authorise.
Generates card numbers that pass the Luhn checksum and are recognised as the right scheme, so a payment form's validation can be tested end to end. A CVV of the right length and a future expiry date come with each one.
These are test values and nothing more. They use the prefixes the card schemes reserve for testing, they correspond to no account at any bank, and no processor will authorise one — which is exactly the point. Using them for anything other than testing your own form is fraud and will not work in any case. For testing against a payment gateway's sandbox, use the specific numbers that gateway documents instead: those trigger particular decline and 3-D Secure paths.
The right prefix and length for each scheme, so a form that detects the card type detects it correctly.
Four digits for American Express and three for everything else, which is a check forms genuinely make.
Amex groups as 4-6-5 and the rest as 4-4-4-4, which is what a card input shows.
Visa, Mastercard, Amex, Discover, JCB, Diners Club, UnionPay and Maestro.
These test a form, not a gateway. For a sandbox, use the numbers that gateway documents — they trigger specific decline paths.
Visa, Mastercard, Amex, Discover, JCB, Diners or UnionPay.
One number, or a batch for an automated test suite.
Number, CVV, expiry and a cardholder name.
It will pass format validation and fail every real authorisation.
No. They pass a checksum and nothing more. There is no account behind them, so every authorisation fails. Attempting a real purchase with one is fraud and also pointless.
A checksum that catches single-digit errors and most transpositions. Every card number ends with a digit chosen so the whole number passes it, which is how a form rejects a typo before contacting a bank.
No. Use the test numbers those gateways document, because they trigger specific behaviours — a decline, an insufficient-funds response, a 3-D Secure challenge. These are for testing your own form validation.
It catches typos, which is its job. It says nothing about whether the card exists, has funds, or belongs to the person entering it — only an authorisation does.
What people who use the Test Credit Card Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Test Credit Card Generator. It takes half a minute and no account.
Write the first reviewCheck a JWT signature against a secret or a public key, and see why it fails.
Convert a hexadecimal string to Base64, standard or URL-safe.
Build and edit URL query strings without breaking the encoding.
Turn a CSV export into INSERT statements, with column types inferred.
Generate Nano IDs — shorter than a UUID, and URL-safe by design.
Convert Base64 back to hexadecimal, with your choice of separator.
Convert file permissions between octal, symbolic and checkboxes.
Strip every optional byte from a JSON document and see what you saved.