Payment Test Data Generator
-
85 IBAN countries + India, US, Canada & more
-
Runs entirely in your browser
Generate structurally valid dummy IBANs, BICs, bank & branch codes, account numbers and test card numbers for testing payment flows. Pick a country and the tool builds one consistent record, broken out into the fields a real system actually reads — each one labelled by exactly which check it passes, so you know what will survive a strict validator and what won’t. Nothing you generate is uploaded or stored; every value is computed locally.
A payment identifier can be valid at two very different levels, and most confusion in testing comes from mixing them up:
mod-97
for IBANs, Luhn for cards, national schemes for some account
numbers. Everything this tool generates is valid at this level.directory —.So if you paste a generated German IBAN into a strict checker, the IBAN check digit passes but you may see “account check digit not correct” and “the bank cannot be identified”. That is expected: the tool labels each field so you can feed whichever one your system under test actually validates.
Not every country uses IBAN. India, the United States, Canada, Australia, China, Japan and others use their own national formats — IFSC, ABA routing numbers, BSB, CNAPS and so on. Those are in the Non-IBAN group of the dropdown, decomposed into their own fields. Where the scheme has a real check digit (the US routing number and Mexico’s CLABE), it is computed correctly; the rest are structure-valid.
No. It is structurally correct and passes the mod-97 check, but it is not tied to any real bank or account and must never be used for a real transfer. It is for sandbox and unit testing only.
Some countries carry an extra check digit inside the account number (Germany, Spain, Belgium, Norway and others). Computing it needs bank-specific rules — in Germany, one of roughly 150 methods selected by the real bank code — so this tool fills that position without computing it. The IBAN-level mod-97 is always correct; the tool flags the countries where this inner check applies.
The card numbers pass the Luhn check and use real network prefix ranges, but they are random and unissued. For a specific gateway sandbox, prefer the processor’s own published test cards (Stripe, Adyen and so on), because those trigger scripted behaviour.
No. The whole tool is JavaScript running in your browser. Nothing is uploaded, logged or stored.