Numbers
Random IBAN Test Number Generator
A random IBAN test number generator creates structurally valid International Bank Account Numbers for GB, DE, FR, NL, and ES — letting developers and QA engineers test payment flows without touching real account data. Each IBAN follows the correct country prefix, check digits, and fixed character length for its format, so validation logic and payment APIs respond exactly as they would with genuine input. Choose a country and set how many IBANs you need — up to a full batch in one click. The output is ready to paste into test suites, seed scripts, or Postman collections. Because the structure is correct but the values are random, you can also probe edge cases: wrong length, bad check digits, or unsupported country codes.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Select the target country from the dropdown to match the IBAN format your application needs to handle.
- Set the count field to the number of test IBANs you want — increase it for bulk fixture files or database seeding.
- Click Generate to produce the list of randomly structured IBANs for that country.
- Copy individual IBANs or the full list and paste them into your test forms, Postman collections, or fixture files.
Use Cases
- •Seeding a Postgres staging database with multi-country IBAN records for GB, DE, and FR accounts
- •Populating Postman environment variables to smoke-test a GoCardless or Stripe payment API
- •Generating Jest fixture data for unit tests on a bank transfer validation module
- •Verifying front-end IBAN auto-spacing and masking logic in a React checkout form
- •Demoing a fintech onboarding flow in Figma or a staging environment without exposing real account numbers
Tips
- →Generate IBANs for all five supported countries in separate runs to test that your validator handles multi-country formats, not just one.
- →After copying, manually change one digit in an IBAN and feed both versions to your validator — confirming it accepts valid and rejects corrupted input.
- →For database seeding, generate the maximum count, copy to a spreadsheet, and pair each IBAN with a mock BIC code column for more realistic records.
- →NL IBANs are shortest at 18 characters; FR are longest at 27 — test both extremes to catch any hard-coded length assumptions in your input fields.
- →If your front-end adds spaces for readability (e.g. GB29 NWBK 6016 1331 9268 19), test that your back-end strips spaces before validating, using these IBANs as raw input.
FAQ
Do these generated IBANs pass the MOD-97 checksum?
Yes — the check digits are computed with the standard ISO 13616 MOD-97 algorithm from the account body, so every generated IBAN passes a strict MOD-97 validation and is accepted by format validators and sandbox payment APIs. The account numbers themselves are random, so they are fake but structurally and checksum-valid.
Can I use fake IBANs in a sandbox payment API?
Yes — that is exactly what they are for. They pass format and checksum validation so a sandbox accepts them, while never matching a real account, so live processors reject them gracefully. Never use real customer IBANs in development or staging; generate fresh test ones here instead.
What is the difference between an IBAN and a SWIFT BIC code?
An IBAN identifies a specific bank account; a BIC (SWIFT code) identifies the bank or branch itself. International transfers often need both — the IBAN to route to the right account and the BIC to identify the institution. This generator produces IBANs only, so supply a BIC separately if your API needs one.
Which countries can I generate IBANs for?
It supports several common formats — GB (United Kingdom), DE (Germany), FR (France), NL (Netherlands), and ES (Spain) — each built to that country's correct length and structure before the MOD-97 check digits are applied. Pick the country your integration expects so the IBAN length and layout match.
Are the account numbers real?
No — the bank and account portions are randomly generated, so the IBANs are entirely fictional. Only their structure and checksum are valid, which is precisely what test data should be: it passes validation everywhere without ever pointing at a real account.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.