GB82 WEST 1234 5698 7654 32GB82WEST12345698765432About IBAN Validator
An IBAN (International Bank Account Number) joins a country code, two check digits, and a domestic account number into up to 34 characters, guarded by the ISO 7064 MOD-97 algorithm so a single mistyped digit does not misroute a transfer. This tool validates IBANs locally in your browser: it checks the country-specific length, converts letters to digits, takes the MOD-97 remainder, confirms it equals 1, and breaks out the bank, branch, and account parts. What the checksum confirms is that the characters were not mistyped, not that the account exists. The check digits come from a defined operation on the preceding characters, so any single-character slip is caught, which makes it a reliable barrier at data entry. But a fully valid, checksum-passing number may belong to no account or a closed one. Its role is catching input errors, not validating accounts, and conflating the two misleads the business. Country code and length must be checked together, since either alone misses problems. Each country code implies a fixed character count, so more or fewer is invalid, and the string joins bank identifier, branch identifier and account according to national rules whose boundaries and checksum presence vary. Implement the check by looking up the country code and then applying that country segmentation, not a single universal length. Not every country uses this numbering system, so cross-border work needs several checks. Some regions use a local routing number with an account, others a card scheme or an international standard number, each with its own algorithm and length constraints. For multi-country collections, select the rule by country first rather than applying one format, which would reject legitimate foreign accounts. When you normalise affects the result. Users type spaces in groups and mix case, which does not affect validity but does interfere with length checks, so strip spaces and uppercase before validating. Do not write the normalised string back as the display value, since the original spacing often reflects a habitual grouping that helps human checking. Finally, this is a sensitive account identifier with boundaries. Bulk validation concentrates scattered accounts into a list that should be managed as internal material with a retention limit, and error messages should say only that the format or check digit is wrong, keeping the full string out of logs and front-end responses to reduce exposure.
How It Works Internally
Validation has two steps: check the structure by length (country code, two check digits, domestic account) and convert letters to digits, take modulo ninety-seven and require one. The algorithm catches the overwhelming majority of single-character errors and adjacent transpositions, but it validates structure only — never whether the account exists, is still open, or belongs to the stated holder.
DE89370400440532013000Passes (structurally valid) — whether the account exists still needs confirmation through the bankMeasured on This Page
| Mod-97 accuracy | Valid IBANs built for GB/DE/FR/NL/ES/IT/NO/SE are all accepted |
|---|---|
| Wrong checksum | An IBAN with two check digits altered is rejected, reporting a mod-97 failure |
| Fixed here | EG/MA/DZ/SN/CM/BF/ML/IR used to be rejected outright as unknown countries; they are now validated by checksum |
| Table coverage | 75 countries are built in while the IBAN registry lists over 80; for the difference the checksum still decides but the length cannot be checked |
| Stated limit | When a country is outside the table the page says the total length was not checked rather than implying full validation |
An IBAN checksum only proves the number is not mistyped: mod-97 equal to 1 does not mean the account exists or that a bank will accept it, which needs a real verification service. Also note the checksum is country-independent, so a number from a country missing from the length table can still be judged genuine — the length is an extra constraint, not a prerequisite.
How to Use
- Open "IBAN Validator"
- Enter or paste the full IBAN
- The status bar shows pass or the exact failure reason
- On success, read the country, check digits and BBAN
- Copy the group-formatted number with its copy icon
Use Cases
- Checkout validation — Verify a customer IBAN in real time before a cross-border payment form submits, cutting failed transfers.
- Finance reconciliation — Bulk-check IBANs in vendor master data to catch accounts with dropped or transposed digits.
- Country detection — Derive the account country from the first two letters and confirm it matches the stated bank.
- Field extraction — Split a long IBAN into bank code, branch code, and account for a legacy system's separate fields.
- Pretty formatting — Group a pasted continuous IBAN into blocks of four for easier human review and printing.
- Payment integration — Validate IBAN format before submitting a payment API call to reduce rejections.
- Account parsing — Extract the bank identifier and branch code from a valid IBAN for internal routing.
- Bulk upload prep — Run a batch of IBANs through the validator before a payroll or vendor upload to catch errors early.
FAQ
How does the MOD-97 check actually work?
Move the first four characters (country code plus check digits) to the end, replace every letter with a number (A=10, B=11 … Z=35), read the result as one huge integer, and take it modulo 97. A remainder of 1 means the IBAN is valid.
Does a valid IBAN mean the account exists?
No. MOD-97 only confirms the string is mathematically consistent and free of obvious typos; it cannot confirm the account is open, can receive money, or who owns it.
Why do IBAN lengths differ by country?
Each country has its own domestic account structure, so total IBAN length varies — Norway 15, Germany 22, Malta 31. The tool checks length by country code before computing the check digits.
Do spaces and lowercase matter?
No. Validation strips spaces and uppercases everything; grouping spaces are only for readability, and electronic transfers usually need the continuous form with no spaces.
Is an IBAN the same as a SWIFT/BIC?
No. An IBAN identifies a specific account, while a BIC (SWIFT code) identifies a bank. Cross-border payments often need both, and a BIC cannot be checked with this tool's MOD-97.
Validation passes but the transfer says the account does not exist. Why?
Validation checks structure and check digits, which filters typing errors, but cannot confirm the account exists, is still open, or belongs to the stated holder. A structurally valid but inactive account is common, especially after branch mergers or account migrations. Passing validation does not replace confirming with the bank and matching the holder name, which is worth doing before any cross-border transfer.
The copied IBAN contains spaces. Does that break validation?
No, the standard allows spacing in groups of four for readability, so strip all spaces before computing. The real risk is visually similar characters: letter O against digit zero and letter I against digit one are nearly indistinguishable in some fonts, which makes transcription from a screenshot or printout error-prone. Check digits catch most of those, so examine those positions first when validation fails.
Does a valid IBAN mean the account really exists?
Validation only checks the format and the mod-97 algorithm (it catches typos), not whether the account exists at a bank. Confirming existence and the beneficiary name requires a bank confirmation flow such as SEPA name checking.