Fake IBAN Generator
Generate fake but structurally valid IBANs for testing — correct country length, correct SWIFT-registry BBAN format and real ISO 7064 check digits, for 77 countries. Optional seed for reproducible fixtures. Runs entirely in your browser.
Input
Sets the country code, the total length and the BBAN format.
Leave blank for fresh random IBANs. Any text here makes the same settings produce the same IBANs every time.
Output
| Property | Value |
|---|---|
| No data yet | |
Guides
Test data for anything that touches bank details is awkward: you need IBANs that pass validation, and you very much do not want to use a real one. This generator produces IBANs that are structurally perfect and completely fictitious — right country code, right length, right BBAN format, real ISO 7064 check digits, and no connection to any bank account anywhere.
How to use it
- Pick a country — 77 are supported, or choose Random to get a mixed batch.
- Set how many you want (1–100).
- Choose a format: printed (grouped in fours, the way an IBAN appears on paper) or electronic (no spaces, the way it travels in a payment file).
- Optionally set a seed — see below.
- Click Generate IBANs, then copy or download the list.
Why the seed matters
Leave the seed blank and every run gives you fresh random IBANs. Type anything into it — test-fixtures-v1, a ticket number, your project name — and the same country, count and seed will produce byte-identical IBANs forever.
That's the difference between test data you paste once and test data you can commit. A seeded batch can go straight into a fixture file, a snapshot test or a seeded database, and it'll still be there, unchanged, on someone else's machine next year.
What "structurally valid" actually means
Plenty of generators only get the length right. That's not enough. The SWIFT IBAN Registry fixes, for each country, the character class of every position in the BBAN — the part after the country code and check digits. A UK IBAN opens with a four-letter bank code (GB82 **WEST** …); a German one is all digits; a Turkish one has a single alphanumeric slot in the middle.
Get that wrong and you produce a string that squeaks past a naive MOD-97 check and then gets rejected by anything that validates properly — which is exactly the code you were trying to test. Every IBAN here follows its country's registry format, and the check digits are computed with the real ISO 7064 MOD-97-10 algorithm, so the results pass strict validation.
Is any of this real?
No. The check digits are arithmetically correct, which is the whole point, but the bank and account identifiers are random noise. A generated IBAN will not match a real account, and it cannot be used to move money. Use it for form validation, unit tests, demos and screenshots — never as a substitute for a real payment instruction.
Generation runs entirely in your browser. Nothing is sent to a server, and no IBAN you generate is stored or logged.
How do I check one of these?
Paste it into the IBAN Validator — it uses the same country registry, so anything this tool generates will come back Valid. For the bank identifier side of a transfer, the SWIFT/BIC Validator checks BIC codes.
I need fake card numbers / other mock data too
The Fake Data Generator covers names, addresses, emails and similar mock records, and the Credit Cards Generator produces Luhn-valid test card numbers the same way this one produces MOD-97-valid IBANs.