KEY TAKEAWAYS
- Generates unique Luhn-valid synthetic numbers per brand.
- 100% client-side — nothing is transmitted.
- Ideal for fixtures, staging data and validator tests.
- Never probe live gateways with generated numbers.
- Generated test numbers are checksum-valid and never chargeable.
- Every the number generator result class should map to a defined workflow action.
Need many unique, well-formed test numbers for QA, fixtures or load testing? This generator creates Luhn-valid numbers for any supported brand, entirely in your browser. No number is ever sent anywhere, and generated values are synthetic — they are not real accounts.
How the generator works
- Picks a brand-appropriate IIN prefix.
- Fills random digits up to length − 1.
- Computes the final check digit with the Luhn algorithm.
Every generated number passes the checksum, which means format validators, sandbox form fields and your own test suite will accept them. The generator complements the standard sandbox test numbers page and the check digit calculator.
Good uses
- Unit-testing Luhn validators and brand detectors.
- Seeding staging databases with realistic-looking rows.
- Load-testing list importers and CSV parsers.
- Testing masked-card displays (front 6 / last 4).
Bad uses
Generating numbers solely to probe live gateways wastes checks and can violate your provider's terms. Only verify cards you are authorised to verify — see the terms of service.
The card number generator is the batch-first sibling of the generator: choose a brand, request hundreds or thousands of numbers, and receive instantly usable fixtures with correct prefixes, lengths and checksum digits. It exists so test suites never need to round-trip through an external service for sample data.
All generation happens in the browser. Nothing is transmitted, nothing is stored, and the output is safe to commit into test fixtures because it cannot be charged.
Key points about the number generator
- Brand-aware formats generated in bulk
- Instant output for large fixture sets
- Copy or export directly
- No network traffic at any point
Using the number generator: step by step
- Choose the brand and count.
- Generate and skim for the shape you expect.
- Copy the batch into your fixtures.
The number generator: from request to result
Rate limits, formats and latency all come from the provider side, which is why per-gateway configuration exists instead of one global setting. Unknown means no definitive answer was received — often an issuer challenge or soft decline — so the card remains unclassified and deserves at most one fallback pass. Dead means the account is closed, blocked or invalid. It is a final answer for the current state of the card and should never be retried blindly. Live means the issuer answered and the account is active and chargeable at that moment; it is strong evidence, not a promise about a future charge. Write it down; the number generator workflows live and die on small consistencies.
Rate limits, formats and latency all come from the provider side, which is why per-gateway configuration exists instead of one global setting. A verification answer reflects the issuer's view at the moment of the request; nothing about it changes the card, the account or the cardholder. Live means the issuer answered and the account is active and chargeable at that moment; it is strong evidence, not a promise about a future charge. It sounds obvious until a real run tests it.
A working routine for the number generator
Log request identifiers and outcomes, never full card numbers. Debugging rarely needs a PAN, and storing one is a liability. Start with a pilot of fifty cards. It surfaces format mismatches and routing surprises while the cost of being wrong is still measured in cents. Watch two numbers over time: the classified rate and the error rate. Together they explain almost every surprise in monthly spend. For recurring workloads, schedule the run before the moment the answer is needed — ahead of a billing cycle, a payout batch or an onboarding window. The habit costs nothing and removes a recurring class of mistakes.
Validation helpers for the number generator
The test card generator produces checksum-valid numbers for development, and they are never chargeable by design. Pair the generator with the Luhn validator when building test fixtures; checksum-valid numbers exercise real validation paths. IBAN validation follows country-specific rules and verifies the checksum, covering the payout side of card operations. It sounds obvious until a real run tests it.
Using the number generator on the right side of the line
When a proposed use cannot be explained to a compliance reviewer in one sentence, it is probably not a fit. Check only cards you own or are authorised to process; verification is not a shortcut around cardholder authorization. The platform does not trade card data, and nothing in the system is designed to bypass a cardholder's consent. In the number generator work, that is the difference between a signal and a guess.
The number generator in numbers
When the classified rate moves, the cause is usually a route or provider change rather than the underlying cards. Aggregate numbers describe populations, not individual cards. Use them to size timeouts and retry budgets, never to judge one account. The reference BIN table covers hundreds of thousands of issuer ranges, and it is deliberately separate from account-status data: one describes issuers, the other describes cards. Latency percentiles matter more than averages: the p90 and p99 tell you what a slow run actually feels like. It sounds obvious until a real run tests it.
Running the number generator as a process
Alert on classified-rate drops, not just on errors; silent degradation is the expensive kind. Schedule recurring checks ahead of the decisions they inform, not after them. Treat provider outages as routing problems: switch routes, recover the unclassified remainder, keep the answers you already paid for. Budget verification against the cost of failure, not against zero; the comparison is what makes spend defensible. Keep it in mind whenever the number generator results are reviewed.
Common mistakes around the number generator
Treating an error as a dead card in the number generator throws away cards that were never classified, and errors are the cheapest outcomes to recover. Running the number generator without a fallback means one degraded provider turns an entire batch into unknowns. Running the number generator without a written triage rule turns a clean batch into manual archaeology.
- Retrying a dead card during the number generator spends balance for an answer that will not change within the run.
- Using BIN reference data as account status in the number generator confuses two different questions and produces confident, wrong decisions.
- Storing card data beyond the needs of the number generator creates risk without adding value.
- Comparing the number generator routes on list price instead of classified rate hides the real economics.
Boundaries of the number generator
Operators remain responsible for the legal basis on which they hold and process card data. The platform does not trade card data, and nothing in the system is designed to bypass a cardholder's consent. A check does not move money, does not create a charge and does not touch the cardholder's credit file. It sounds obvious until a real run tests it.
Interpreting outcomes in the number generator
A live answer is evidence about the account, not a guarantee about a specific future transaction; issuer rules can change between the check and the charge. Conflating outcomes is the most expensive habit in this area — an error treated as a dead card discards real inventory, and an unknown treated as live inflates confidence. The four result classes are a decision matrix, not a score: live proceeds, dead recovers, unknown gets one careful retry, error returns to the queue. A result is only as fresh as its timestamp. High-value decisions should use checks that ran close to the moment of the decision. Remember it the next time the number generator produces an ambiguous answer.
What aggregate data says about the number generator
When the classified rate moves, the cause is usually a route or provider change rather than the underlying cards. Aggregate numbers describe populations, not individual cards. Use them to size timeouts and retry budgets, never to judge one account. The reference BIN table covers hundreds of thousands of issuer ranges, and it is deliberately separate from account-status data: one describes issuers, the other describes cards. Latency percentiles matter more than averages: the p90 and p99 tell you what a slow run actually feels like. In the number generator work, that is the difference between a signal and a guess.