Skip to main content
Back to Numbers generators

Numbers

Random IBAN Test Number Generator

Used by developers, writers, and creators worldwide.

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.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Select the target country from the dropdown to match the IBAN format your application needs to handle.
  2. Set the count field to the number of test IBANs you want — increase it for bulk fixture files or database seeding.
  3. Click Generate to produce the list of randomly structured IBANs for that country.
  4. 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

The IBANs are structurally formatted for each country — correct prefix, length, and check-digit positions — but are randomly generated and may not all pass a strict MOD-97 verification. If your integration requires checksum-passing IBANs, run each one through a MOD-97 library like iban.js before adding it to your test suite.

can I use fake IBANs in a sandbox payment API without breaking anything

Yes — structurally valid but randomly generated IBANs are exactly what sandbox environments expect. They will be accepted by format validators and rejected gracefully by live payment processors, which is the safe, compliant way to test. Never use real customer IBANs in development or staging environments.

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 typically need both — the IBAN to route funds to the right account and the BIC to identify the receiving institution. This generator produces IBANs only, so if your API also requires a BIC, you will need to supply that separately.