IBAN validator and parser
Validate IBANs against ISO 13616 (country code, length, MOD 97 checksum), break them into country, bank, branch and account segments, and show the 4-digit grouping; ships a table of 80+ countries and regions.
Runs in your browserEvery computation happens in your browser — your data never leaves this device.
Validation order: characters → format → country code → length → MOD 97. Segments are still shown when the checksum fails so you can compare them piece by piece.
Validation
What this tool does
- Validate an account number a customer sent you before it goes into the system, so a missing or mistyped character cannot bounce the transfer.
- Reconcile a payment slip against your system: the 4-digit grouping plus the MOD 97 check exposes manual typing errors immediately.
- Break an IBAN into its structured segments (bank code, branch, sort code, account number, RIB key) and map them onto your own data model.
- Confirm a country’s IBAN length and layout before writing payment code — Germany is 22 characters, the UK is also 22 but splits differently.
Example
Input
GB82 WEST 1234 5698 7654 32
Output
GB82 WEST 1234 5698 7654 32 Valid: United Kingdom · country GB · check digits 82 · length 22 · MOD 97 = 1 Bank code WEST · sort code 123456 · account number 98765432
This is the official UK example from the IBAN Registry and its MOD 97 remainder is 1. Change the final 2 to a 1 and the remainder becomes 71, so the tool reports a checksum mismatch — while still showing the segments so you can compare them piece by piece.
Frequently asked questions
Does a passing validation mean the account really exists?
No. Country code, length and the MOD 97 checksum only prove the string is well formed, i.e. free of typing errors. Whether the bank code is live, whether the account belongs to that person and whether it has been closed must be confirmed by the bank or your payment provider — this tool never goes online.
Do case and spaces matter?
No. Before validating, spaces, hyphens and en/em dashes are removed and the string is upper-cased, so "gb82 west 1234…" and "GB82WEST1234…" behave identically. Any other punctuation, such as a dot, triggers an illegal-character error.
Can I use it for Chinese account numbers?
China is not an official IBAN member country, so the table marks it unofficial: you get a warning and a best-effort parse. Cross-border transfers to China normally use SWIFT/BIC plus a local account number instead of an IBAN. Kosovo (XK) is in the same situation.
How does the MOD 97 check work?
It follows ISO 7064 MOD 97-10: move the first four characters to the end, replace each letter with two digits (A=10 … Z=35), then take the remainder of that digit string modulo 97. A valid IBAN leaves a remainder of 1. Computing it in chunks keeps huge numbers from overflowing.
What happens with empty input or the wrong length?
Empty input asks you to enter an IBAN; a length that disagrees with the country table states the expected length (22 for DE, for example); an unknown country code is reported as not being in the table. The order is characters → format → country code → length → MOD 97.
Keywords：ibaniban 校验iban validatoriban parserswiftbicmod 97iso 13616国际银行账号银行账号校验