Test IBAN generator

Why test IBANs matter

Any form or API that accepts IBANs should be tested with values that pass every validation layer - length, format, mod-97 check digits and national checksums. Random strings fail immediately and real customer IBANs have no place in a test suite. A generated test IBAN gives you the best of both: it exercises the full happy path of your validation logic while pointing at no real account. Where a country documents a test or example bank code, the generator uses it by default, and every result carries an explicit TEST label, including when you copy it.

This tool intentionally has no bulk mode, no CSV export and no API. If you need hundreds of values in CI, generate them programmatically with an open-source library (ibantools for JavaScript, schwifty for Python) - see why we made this trade-off and how the check digit algorithm works.

Per-country test IBAN pages

Frequently asked questions

Are these generated IBANs real bank accounts?

No. They are structurally valid numbers for software testing: correct length, correct mod-97 check digits and, where applicable, correct national check digits. They are labelled TEST and must never be used for real payments.

Why do generated IBANs use documented test bank codes?

Where a country publishes a test or registry-example bank code, the generator uses it by default. This makes accidental collision with a live account as unlikely as possible while keeping the IBAN fully valid for validators.

Can I generate thousands of IBANs as a CSV?

Deliberately not. Bulk export invites abuse, so this tool generates one IBAN at a time. For CI-scale data, generate them inside your test code with an open-source library instead - our guide explains how.

Last verified: 2026-07-05.

Also from ZENOM

Would your buyer find all the answers about your business?

See what ZENOM is doing about it.

About ZENOM

Or bring a specific problem of your own.

Contact ZENOM