IBAN Validator
Check IBAN structure, checksum and duplicate line positions
Processed locally in the browser; input is not autosaved. Maximum input: 1 MiB.
Structure reference: the 2024-04-30 schwifty historical snapshot covering 87 IBAN prefixes, not the latest official registry. Unknown prefixes are marked not covered.
Maximum 1,000 lines. ASCII lowercase becomes uppercase; ASCII spaces and tabs can be removed. Duplicates retain original line positions. Passing means format, structure and MOD-97 checks only; it does not verify a bank, account, recipient or payment.
Process again after changing input or options to generate a current result.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Check an IBAN list before investigating a rejected banking import. Each physical line receives a separate format, country-length, BBAN character-structure and MOD-97 result, with duplicate references back to the original line. ASCII lowercase is normalized; spaces and tabs can be removed. Country structures use a clearly dated schwifty snapshot from 2024-04-30 covering 87 IBAN prefixes, not a claim to the latest SWIFT registry. A prefix absent from this snapshot is reported as not covered. Passing these local checks does not verify bank allocation, domestic account checksums, account existence, beneficiary identity or payment availability. Input is not uploaded or autosaved.
Scenario Recipes
Review duplicate entries without losing line positions
Goal: Locate two copies of a grouped IBAN and one blank row.
- Paste GB82 WEST 1234 5698 7654 32, leave the second line blank, then paste GB82WEST12345698765432 on line 3.
- Keep ASCII space cleanup enabled and process. Confirm line 2 remains blank and line 3 points back to line 1.
- Download the report. Resolve duplicates in the source list deliberately, and verify beneficiary details through your banking workflow.
Result: The report preserves the original three row positions and the normalized duplicate relationship.
Failure Clinic (Common Pitfalls)
A newly issued IBAN says not covered
Cause: The bundled historical reference may predate that prefix.
Fix: Check the current SWIFT registry; do not treat missing coverage as proof the account is fake.
Copied account text fails format
Cause: Non-breaking spaces, full-width letters or other Unicode characters are not ASCII IBAN characters.
Fix: Obtain an ASCII account identifier from the source. Optional cleanup removes only ordinary spaces and tabs.
A passing account still cannot receive payment
Cause: This tool checks structural rules and MOD-97, not bank systems or domestic checks.
Fix: Verify bank availability, beneficiary identity and account status with the appropriate provider.
Production Snippets
A checksum is only one check
text
GB82WEST12345698765432 → structure and MOD-97 pass
DE67AAAAAAAAAAAAAAAAAA → BBAN structure fails, despite MOD-97
XX97123456789012345678 → prefix not covered by the snapshot
Passing does not establish account ownership.Frequently Asked Questions
What does a passing IBAN result mean?
The ASCII format, length and BBAN structure in the bundled snapshot, check-digit range 02–98 and MOD-97 all passed. This does not verify a real account, bank allocation or recipient.
Which registry version is used?
The bundled reference is the 2024-04-30 schwifty snapshot with 87 actual IBAN prefixes. It is historical, not a statement that this is the latest SWIFT registry; the source link is shown in the tool.
Does an unsupported country mean the IBAN is invalid?
No. It means the prefix is absent from this historical snapshot. Consult the current SWIFT registry and the bank for newly adopted or changed formats.
Why can a correct checksum still fail?
A value can satisfy MOD-97 yet contain letters where a country requires digits, or have the wrong length. Country structure and checksum are checked separately.
Are blank and duplicate lines removed?
No. All physical lines retain their positions. Duplicates refer to their first normalized occurrence. A final LF or CRLF terminates the previous line without creating an extra line.
What input and privacy limits apply?
Process up to 1 MiB and 1,000 lines locally. Only ASCII lowercase becomes uppercase; optional cleanup removes ASCII spaces and tabs. Input is not uploaded or autosaved, and the old automatic draft is removed.
Keep browsing