Generate valid fictitious IBANs for 89 countries, with the right BBAN structure, national check digits and mod 97 check digits.
An IBAN is the country code, 2 check digits and the BBAN, the domestic part of the account, whose structure each country registers under ISO 13616. A generator that just draws digits until mod 97 closes produces numbers that strict libraries reject: a letter where only digits fit, the wrong bank length, or a national key that does not match. This generator uses the SWIFT registry structure for all 89 countries (bank, branch and account fields, as digits, letters or alphanumerics) and computes the national key in 27 of them, among them Spain, France, Italy, Belgium, Portugal, Poland and Norway. It then closes the IBAN with the ISO 13616 check digits. You can fix the bank and branch code, generate 1 to 500 at a time, copy in electronic or printed format, download CSV and JSON, and produce controlled defects for negative tests. The output is fictitious: passing validation does not prove an account exists.
Mod 97 only guarantees the check digits match the rest of the number. It accepts, for example, a letter in the middle of a German account number, which in the registry is fully numeric (8 bank digits and 10 account digits). Systems that validate the BBAN, such as bank onboarding forms and ERPs, reject that IBAN, and the test you built with it proves nothing.
So the generator honors three layers: the country's total length (from 15 characters in Norway to 33 in Russia), the class of each BBAN field (n for digits, a for uppercase letters, c for alphanumeric) and, where it exists, the national check digit.
Some countries embed in the BBAN a digit that the issuing bank computes from the rest: Spain (two DC digits), France and Monaco (the RIB key), Italy and San Marino (the CIN letter), Belgium, Portugal, Norway, Poland, Finland, Hungary, Croatia, Estonia, Czechia, Slovakia and others. Each algorithm was checked against the example IBAN the registry publishes.
Germany, the United Kingdom, Ireland and most other countries have no such digit inside the BBAN, or the method depends on each bank. For those countries the generator draws the account number with no extra rule. The Netherlands has the elfproef, treated as indicative only because newer banks do not follow it.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/iban-generator"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="IBAN Generator for Testing"
></iframe>These references help contextualize formulas, standards, APIs and limitations used on this page. They do not replace professional validation when a result has legal, financial, medical or operational impact.
No. The IBANs are drawn with the country's correct structure and correct check digits, but no bank issued them. Because the number space is finite, one of them can coincide with an existing account by chance, which is why they must not go into payments, debits or real sign-ups. To test payment flows, use the sandbox IBANs your provider publishes.
Fictitious test data. These IBANs are drawn at random and have a valid format, but they belong to nobody and may coincide with a real account by chance. Do not use them for payments, real sign-ups or to deceive anyone.
DE81 6742 2730 4375 6711 45
DEGermanySEPA areaSWIFT BBAN format: 8!n10!n
| Part | Value | Registry rule |
|---|---|---|
| Country | DE | ISO 3166-1 country code |
| Check digits | 81 | Mod 97 (ISO 13616) |
| Bank | 67422730 | 8 digits |
| Account | 4375671145 | 10 digits |
Registry example: DE89 3704 0044 0532 0130 00
674227304375671145DE816742273043756711451314811Responsible use: test IBANs are for forms, validation, data import and payment sandboxes. Passing validation does not prove an account exists. Everything is generated in your browser and nothing is sent to servers.