IBAN Toolkit logoIBAN Toolkit

Bulk Test IBAN Generator

Bulk test IBANs for developers: up to 500 at once, with CSV, JSON and TXT export. Valid check digits, zero signup.

Maintained by Mister AhmadUpdated 8 October 2026Editorial policy

Generate synthetic IBAN test data in bulk

Built for test fixtures, database seeding and load tests.

Same country + seed + row order gives the same test values. Leave blank for random samples. Seed algorithm: v1. Do not enter personal data.

How this tool works

This tool is designed for testing, education and workflow prototyping. It validates or generates structurally correct values based on published format rules and clearly states where no live-bank lookup is performed.

Synthetic IBANs for serious testing

When a single IBAN is not enough: you are seeding a test database, running a load test against a validation API, or generating fixtures for a CI pipeline: you need bulk fake IBANs. This tool generates up to 500 at a time and exports them as CSV, JSON, or plain text, ready to pipe into your scripts.

What makes useful IBAN test data?

  • Structurally valid: correct length and BBAN layout per the official registry, so your validators exercise the real code path.
  • Checksum-correct: genuine mod-97 check digits, so format validation passes and you can test downstream logic.
  • Synthetic by design: random bank and account segments intended for controlled test environments. Because the generator does not query live directories, do not treat a generated value as guaranteed unassigned.

Common workflows

  • Database seeding: download CSV and import directly into staging tables.
  • API load testing: feed JSON arrays into k6, Locust, or Postman collections.
  • Unit test fixtures: generate a fixed set once, then hard-code the known-valid values into your test suite.
  • Demo environments: realistic-looking customer records without any real PII.

A note on responsibility

Fake IBANs are a standard QA tool: and also why this page carries a clear boundary: they must never be used to mislead anyone, open accounts, or move money. Every export from this tool is synthetic test data intended only for controlled development and QA. If you need a single IBAN with a validator, use the main IBAN generator.

Related tools

IBAN Generator

Create country-specific identifiers for format testing.

IBAN Validator

Check country format, length and MOD-97 digits.

IBAN Calculator

Calculate an IBAN from your account components.

SWIFT/BIC Generator

Generate test BICs and check their syntax.

Bank Account Number Generator

Create synthetic account numbers for QA fixtures.

Routing Number Generator

Generate checksum-valid US routing test values.

Frequently asked questions

Up to 500 per click, in CSV, JSON or TXT format. Generate repeatedly for larger sets.
Yes: if your app implements standard ISO 13616 validation (length + structure + mod-97 checksum), these will pass, because they are built to the official registry specs.
No. They are synthetic test values and are not checked against live account directories. Do not use them for real transactions or to represent a real account.
This page is optimized for bulk: bigger batches, one-click file export, and fixture-friendly formats. The main generator is better for interactive single IBANs with a built-in validator.
Testing and educational use. Generated identifiers are synthetic and are not checked against live bank directories. A randomly generated value can coincidentally resemble or match a real identifier. Never use generated data for real payments, account applications, identity verification, or to represent a real person or institution.

DEVELOPER FIXTURES · VERSION 1.0.0

Download a reproducible IBAN test pack

623 cases across all 89 supported formats: passing values, lowercase and spaced input, wrong checksum, short/long input, and a national-pattern or invalid-character case. Each record includes the expected format result and failed rule.

Built locally. No signup or upload. Version 1.0.0 uses seed fixture-pack-1.0.0 and seed algorithm v1.

What was tested

4,450 generated values and 21,452 assertions passed across 89 formats. Independent BigInt MOD-97 and a separately constructed character-pattern matcher were used in the test suite. Seed and row reproducibility, normalization and negative cases are included.

Scope of the expected results

“Pass” means international format, country length, BBAN character pattern and MOD-97. It does not mean every domestic checksum passes, a bank code is current, an account exists or a recipient owns it. Synthetic values can coincide with assigned identifiers. Never use these files for payments.

Use in a regression suite

  1. Download the JSON or CSV and keep the version in source control.
  2. Read expected_format_valid as a local structural-validation expectation.
  3. Keep directory, domestic-checksum and provider-sandbox cases in separate suites.
  4. When updating your rules, investigate changed outcomes rather than silently rewriting the expected result.