Free Credit Card Generator for Testing

How to Use the Credit Card Generator

1. Choose a card network, or Random to mix all seven.
2. Choose how many records you need: 1, 5, 10 or 20, or type any number up to 50.
3. Tick the optional fields you want: a future expiry date, a security code and a fictional name.
4. Select Generate test data (or press G).
5. Copy a single value, copy a whole record, or download the batch as CSV or JSON.
6. Use the results in development and test environments, such as form validation and UI tests, never for payments.

What Is a Test Credit Card Number?

A test credit card number is a made-up number that follows the same structural rules as real card numbers, so software can be tested without using anyone’s real details. Those rules are public:

• Prefix. The first digits indicate the card network. Every Visa number starts with 4, for example, and American Express numbers start with 34 or 37.
• Length. Each network uses particular lengths, such as 16 digits for most Visa and Mastercard numbers and 15 for American Express.
• Check digit. The last digit is calculated with the Luhn algorithm so that the whole number passes a checksum.

A number that meets all three rules is well-formed. That’s all it is. Being well-formed doesn’t show that an account exists, and it doesn’t mean a payment would be authorised. Those decisions are made by the card issuer, not by the digits.

Supported Card Networks

The prefixes below are the ranges this tool generates from. They are a subset of the ranges recognised by Braintree’s open-source credit-card-type (opens in a new tab) library, which also supplies the lengths, spacing and security-code details. Every generated number is checked against that library before it’s shown.

The network tells you nothing about whether a card is credit, debit or prepaid, or which bank issued it. This tool doesn’t generate or label those attributes.

How the Luhn Algorithm Works

The Luhn (or “mod 10”) check catches most single-digit typos and swapped neighbouring digits. To check a number:

1. Start from the rightmost digit and move left.
2. Double every second digit, starting with the one just left of the check digit.
3. If doubling gives a number greater than 9, subtract 9 (so 16 becomes 7).
4. Add up all the digits, including the ones you didn’t double.
5. If the total is divisible by 10, the number passes.

Worked example

To find the check digit for 7992739871, double every second digit starting from the right-hand end (it will sit next to the check digit):

The values add up to 67. The check digit is whatever brings the total to the next multiple of 10: 3, giving 79927398713, which passes the check. This example is verified by the tool’s automated tests.

Common Use Cases

• Payment form formatting: checking that numbers group correctly as people type, including Amex’s 4-6-5 pattern.
• Front-end validation: testing that forms accept well-formed numbers and reject wrong lengths or failed checksums.
• Checkout UI development: filling realistic-looking data into designs and prototypes.
• QA fixtures: exporting CSV or JSON records for test suites and seed data.
• Automated form tests: feeding varied networks and lengths into end-to-end tests.
• Network detection: confirming that your form shows the right network as digits are entered.

For testing the payment itself, such as authorisations, declines, 3-D Secure or refunds, use your payment provider’s sandbox and its published test cards. Stripe, for example, documents specific test card numbers for its testing environments and asks that real card details are never used for testing (Stripe Docs (opens in a new tab)).

Privacy: Browser-Based Generation

Here is exactly what happens when you use the generator:

• Numbers, expiry dates, security codes and names are created by JavaScript running in your browser, using its built-in secure random number generator.
• Copying uses your browser’s clipboard. CSV and JSON files are built in the browser and saved directly to your device.
• Generated values are not sent to our server or any other service, and they aren’t stored in cookies or local storage. The “Earlier this session” list lives only in the open page and disappears when you reload or leave.

As with any website, loading the page itself involves a normal request to our web server, which may record standard technical details such as the time and the page requested. That request happens before you generate anything and doesn’t contain generated data.

Important Limitations

Generated values:

• are not real payment credentials and aren’t linked to any bank account;
• say nothing about whether a card is active, has a balance or belongs to anyone;
• may pass a checksum but will still be declined by payment gateways;
• use random expiry dates, security codes and placeholder names that don’t correspond to any account;
• must not be used for purchases, sign-ups that require payment, or any unauthorised activity.

Frequently Asked Questions