Are these real bank accounts?

No. They have valid format and checksum but don't map to real accounts. They'll pass a format validator but fail any lookup at an actual bank.

Can I use these to test my payment form?

Yes, for format-validation testing. They will satisfy an 'is this a well-formed IBAN?' check. For end-to-end payment testing, use sandbox accounts from your payment processor (Stripe, Adyen) — they provide real-format test IBANs that trigger mock transactions.

Is it legal to generate fake IBANs?

Yes, generating them is legal. Using them to commit fraud, impersonate a real account, or bypass identity verification is illegal in every jurisdiction that recognises IBAN. Use for internal testing only.

Why do the generators produce valid checksums?

An invalid checksum would be useless for testing — every form validator rejects it immediately. The whole point is to generate strings that pass format validation so you can test the rest of your payment flow.

What countries are supported?

The 16 most common European IBAN-using countries: GB, DE, FR, ES, IT, NL, BE, AT, CH, IE, PT, PL, SE, NO, DK, FI. Each has the correct length and BBAN structure for that country.

Could I accidentally generate a real account number?

The odds are astronomically small — the BBAN space for any country has trillions of combinations, and banks only use a tiny fraction. But it's theoretically possible, which is why you should never attempt a real transaction with these numbers.

Fake IBAN Generator

Generate valid-format IBANs for testing. Not for fraud.

Generation is browser-side; no server logs. These IBANs are for testing only — do not use for real transactions.

For testing and development only. These IBANs pass format validation (correct country structure and checksum) but do not correspond to real bank accounts. Never use them to impersonate a customer, commit fraud, or bypass KYC — that is illegal in every jurisdiction that recognises IBAN.

United Kingdom · 5 IBANs

GB11 ODXI 6804 2183 7946 89
GB98 QAAC 4498 2370 2122 93
GB09 LKPK 6671 2506 6148 03
GB11 ECLW 7311 8801 3508 39
GB18 OFIW 7815 9238 1029 17

Similar tools

QR Code Generator

Generate custom QR codes for URLs, WiFi, contacts, and more.

Strong Random Password Generator

Create cryptographically strong passwords with a strength meter.

List Randomizer

Fair Fisher-Yates shuffle for giveaways and team picks.

What is a Fake IBAN Generator?

A Fake IBAN Generator produces strings of digits and letters that pass every IBAN-format validator but do not correspond to real bank accounts. It exists for testing and development only — QA teams need realistic bank account numbers to build payment flows, form validators, and fraud-detection heuristics, and they absolutely should not use real customer accounts (or their own personal accounts) to populate test fixtures.

Critical ethical disclaimer. Every single generated IBAN has a valid format and a correct mod-97 checksum. A format validator on a payment form will accept them. Submitting them to an actual bank or payment processor for a real transaction will either (a) fail at the account-lookup step because no such account exists, or (b) in rare cases, hit a real account that coincidentally matches the format — which is worse. Never use these IBANs to impersonate a real person or bypass KYC. Doing so is fraud and is illegal in every jurisdiction that recognises IBAN.

How IBAN format works. The International Bank Account Number (ISO 13616) starts with a two-letter country code, followed by two checksum digits, followed by the country-specific Basic Bank Account Number (BBAN) that identifies the bank and account. UK IBANs are 22 characters total; Germany is 22; France is 27; Portugal is 25 — each country has a fixed length. Our generator uses the correct length and structure for every country it offers.

Checksum. The two digits after the country code are a mod-97 checksum. Algorithm: move the country code and "00" placeholder to the end of the string, convert every letter to a two-digit number (A=10, B=11, ... Z=35), compute mod-97 of the result, and the checksum is 98 - remainder. Our tool computes this correctly, which is why every generated IBAN validates. (A random 20-digit string without checksum fails validators.)

Legitimate uses. QA test fixtures. Populating staging environments with realistic-looking data. Manual testing of form validation. Building demo videos that need to show bank details without using a real account. Writing documentation that includes sample IBANs. Running static analysis against code that handles IBANs.

Illegitimate uses. Submitting to a real bank or payment system. Creating fraudulent receipts, invoices, or customer records. Bypassing identity verification. Anything that would be considered fraud or financial misrepresentation under your jurisdiction's laws. Don't do those things.

How to generate fake IBANs for testing

Pick a country. 16 European countries supported.
Set how many to generate (up to 25 at once).
Click Regenerate for a fresh batch.
Copy one or all — paste into your test fixture or staging database.
Never use these for real financial transactions.

Features

16 European countries with correct length and BBAN structure.
Valid ISO 13616 mod-97 checksum on every IBAN.
Formatted display with 4-character groups (standard IBAN print format).
Single or bulk (up to 25) generation.
Copy individual or all at once.
Prominent "for testing only" disclaimer.

Frequently asked questions

Are these real bank accounts?: No. They have valid format and checksum but don't map to real accounts. They'll pass a format validator but fail any lookup at an actual bank.
Can I use these to test my payment form?: Yes, for format-validation testing. They will satisfy an 'is this a well-formed IBAN?' check. For end-to-end payment testing, use sandbox accounts from your payment processor (Stripe, Adyen) — they provide real-format test IBANs that trigger mock transactions.
Is it legal to generate fake IBANs?: Yes, generating them is legal. Using them to commit fraud, impersonate a real account, or bypass identity verification is illegal in every jurisdiction that recognises IBAN. Use for internal testing only.
Why do the generators produce valid checksums?: An invalid checksum would be useless for testing — every form validator rejects it immediately. The whole point is to generate strings that pass format validation so you can test the rest of your payment flow.
What countries are supported?: The 16 most common European IBAN-using countries: GB, DE, FR, ES, IT, NL, BE, AT, CH, IE, PT, PL, SE, NO, DK, FI. Each has the correct length and BBAN structure for that country.
Could I accidentally generate a real account number?: The odds are astronomically small — the BBAN space for any country has trillions of combinations, and banks only use a tiny fraction. But it's theoretically possible, which is why you should never attempt a real transaction with these numbers.