IBAN Checker

Runs in browser New Web Utilities

Paste an IBAN from any of the 89 countries and territories in the SWIFT IBAN Registry and the checker reads it entirely in your browser: it removes spaces and fixes letter case, finds the country from the first two letters, compares the length and the national account format (BBAN) with the registry, checks the two check digits with the ISO 13616 MOD-97 rule and shows the bank and branch identifiers at the positions the registry gives for that country. A valid result means the IBAN is well formed; it does not prove that the account exists, and the tool never names the bank or the account holder, because an IBAN alone cannot tell you who owns the account.

Privacy: This tool runs entirely in your browser. Your input never leaves your device.

What does an IBAN check actually prove?

An IBAN (ISO 13616) is a country code, two check digits and the national account number (BBAN), whose length and layout each country registers in the SWIFT IBAN Registry. A check can prove only that the IBAN is well formed: the right length and structure for its country and check digits that pass the MOD-97 rule, which catches almost every single typing mistake and swapped pair. It cannot prove that the account exists, is open or belongs to a particular person — only the bank holding the account can confirm that.

Security note: Payment fraud often arrives as an e-mail announcing a "new IBAN" for a known supplier, and that IBAN passes every check. Confirm any change of bank details by calling a number you already have, never through the message that announced it.

Read the guide: What Is an IBAN?

Every IBAN is a country code, two check digits and the BBAN, the national account number. Each country sets its own BBAN layout, so the bank, branch and account fields sit in different places: compare the UK and Saudi examples.

United Kingdom: the registry example (22 characters)

Part 1:GBPart 2:29Part 3:NWBKPart 4:601613Part 5:31926819

Saudi Arabia: the registry example (24 characters, no branch field)

Part 1:SAPart 2:03Part 3:80Part 5:000000608010167519

  • 3–5BBAN: its fields and their positions differ by country
  1. 1Country codeISO 3166 letters. They decide the length and the BBAN layout to check against.
  2. 2Check digitsComputed from all the other characters with MOD-97; always 02–98.Checksum
  3. 3Bank identifierUK: 4 letters. Saudi Arabia: 2 digits. A code, not a bank name.
  4. 4Branch identifierUK: the 6-digit sort code. Many countries, Saudi Arabia among them, have none.
  5. 5Account numberThe rest of the BBAN: 8 digits in the UK, 18 characters in Saudi Arabia.

A correct layout and checksum show that the IBAN is well formed. They do not show that the account exists or whose it is.

How to use IBAN Checker

  1. Paste or type the IBAN. Spaces, dashes between groups, lower-case letters and the word "IBAN" in front are fine.
  2. Press Check IBAN. The Format and checksum tile says whether the IBAN is valid, invalid, or from a country whose format cannot be verified.
  3. If it is invalid, read the Checks table: the first failed row says what is wrong, for example a wrong length or a checksum that does not match.
  4. Use the IBAN breakdown for the country, check digits, BBAN and bank identifier, and copy the electronic or print format you need.
  5. Before you send money, confirm the beneficiary's name and bank with the payee or your bank: a valid IBAN does not prove whose account it is.

IBAN Checker features

  • Validates IBANs from all 89 countries and territories with their own code in the SWIFT IBAN Registry, from Saudi Arabia, the UAE and Egypt to Germany, the UK and Brazil
  • Normalizes the input first: removes spaces, invisible marks and the dashes a printed IBAN can have between its groups, accepts lower case and a leading "IBAN" label, and turns Arabic-Indic or Devanagari digits into 0–9
  • Checks each rule separately — characters, country code, national length, BBAN structure, check-digit range and the ISO 13616 MOD-97 checksum — and says which one failed and where
  • Identifies the country from the first two letters and shows the bank and branch identifiers at the positions the registry gives for that country, leading zeros included
  • Shows the checksum calculation with your IBAN's own numbers, so you can see why it passes or fails
  • Lists the IBAN format of every registry country — length, BBAN structure, bank-code position and the registry example — as a table you can download
  • Copies the IBAN in electronic format (no spaces) or print format (groups of four) with one click

Inputs and outputs

Inputs

  • IBAN — one IBAN in electronic or print format, up to 64 characters with spaces or dashes; native Arabic-Indic and Devanagari digits are accepted.
  • Nothing else: no bank, country or account setting is needed, and nothing is fetched.

Outputs

  • Format and checksum — the verdict (valid, invalid, or not verifiable for a country outside the registry), the country, the checksum result, the bank identifier and a reminder that the account holder is not verified.
  • IBAN in electronic and print format, each with its own Copy button.
  • IBAN breakdown and Checks — the country, check digits, BBAN, bank and branch identifiers with their positions, and every rule with its result and the reason.
  • How the checksum was computed, the Country format from the SWIFT IBAN Registry, and What this result does not tell you.
  • IBAN formats by country — with Show all country formats, every registry country's length, BBAN structure, bank-code position and example, downloadable as CSV.

IBAN Checker example

The SWIFT IBAN Registry example for Saudi Arabia

Input:

sa03 8000 0000 6080 1016 7519 (the tool's Load example, typed in lower case with spaces)

Output:

Format and checksum: Valid · Country: SA (Saudi Arabia) · MOD-97 checksum: Passed · Bank identifier: 80 · Account holder: Not verified
IBAN, electronic format: SA0380000000608010167519
IBAN breakdown: Check digits 03 · BBAN 80000000608010167519 · Bank identifier 80 (characters 5–6) · Length 24 of 24 characters · Normalized: spaces removed · letters made upper case
Checks: Characters, Country code, Length, BBAN structure (2 digits · 18 letters or digits), Check digits (03, inside the 02–98 range), MOD-97 checksum (remainder 1) — Passed; Bank name and BIC, Account and beneficiary — Not available

How to read the IBAN Checker results

"Format and checksum: Valid" means the country is in the SWIFT IBAN Registry, the length and BBAN structure match its format and the MOD-97 checksum leaves 1. It is the right result to expect before a transfer, but it is not a confirmation that the account exists or belongs to the person you are paying.

"Invalid" means at least one rule failed; the first failed row in Checks is usually the one to fix. A failed checksum with every other row passing almost always means one mistyped character or two swapped neighbours — ask the payee to send the IBAN again rather than correcting it yourself.

"Not verifiable" means the code is a real country code, but the country is not in the SWIFT IBAN Registry, so its national length and structure cannot be checked. The checksum result is still shown for information, yet the IBAN is not called valid.

Bank identifier is the code the registry places at that position — a number in Saudi Arabia or Germany, four letters in the UK or Jordan. The tool shows the code only; it does not turn it into a bank name.

When to use IBAN Checker

  • Checking an IBAN a customer, supplier or landlord sent you for typing mistakes before you enter it in your banking app.
  • Seeing which country and bank code an IBAN carries, for example to tell a Saudi IBAN (SA, 24 characters) from a UAE one (AE, 23).
  • Testing a payment form or an onboarding flow: the registry examples are well-formed documentation IBANs that every validator should accept.
  • Looking up the IBAN length and BBAN layout of a country before you build or review an input field.

Troubleshooting

  • "Remove these characters": the IBAN contains a dot, a character from another alphabet, or a dash that does not separate two groups — at the start or the end, or two in a row. Type it again with letters and digits only; spaces and single dashes between groups are fine.
  • "IBANs are 24 characters long; this one has 23": a character is missing or one too many. Count against the print format the payee sent, four characters at a time.
  • The checksum fails although every other check passes: a digit is mistyped or two are swapped. Request the IBAN again from its owner instead of trying digits until it passes — a guessed IBAN can pass and still be someone else's account.
  • "Not verifiable": the country does not use IBANs in the SWIFT IBAN Registry (the United States, Canada, India and Australia do not). A transfer there usually needs an account number with a bank or routing code instead.

Frequently asked questions about IBAN Checker

Does a valid IBAN mean the account exists?

No. Valid means the IBAN has the right country code, length and national format, and its check digits match the rest of the number under the MOD-97 rule. A mistyped but well-formed account number can still pass, and a closed or never-opened account looks exactly like an open one. Only the bank that holds the account can confirm it exists.

Can I find the account holder's name from an IBAN?

No. An IBAN contains a country code, check digits and the national account number — no name. This tool connects to no bank or account-verification service, so it shows no beneficiary name and never guesses one. Confirm the name with the payee, or use your bank's own payee check when you add the beneficiary.

Why does the tool show a bank code but not the bank's name or BIC?

The SWIFT IBAN Registry says where the bank identifier sits in each country's IBAN, so the tool can show those characters exactly, leading zeros included. Turning a code into a bank name or a BIC needs a maintained bank directory, and none is bundled, so the tool shows the code and does not guess a name. Ask the payee or your bank for the BIC if a transfer needs one.

How is the IBAN checksum calculated?

Move the first four characters to the end, replace every letter with two digits (A = 10 … Z = 35), and divide the resulting number by 97. A correct IBAN leaves a remainder of 1. The check digits themselves are chosen as 98 minus the remainder computed with 00 in their place, so they always fall between 02 and 98.

Is my IBAN sent or stored anywhere?

No. The check runs in your browser on the formats bundled with the page. The IBAN is not sent to Mutqan, to a bank or to any other service, and it is not stored or recorded in analytics.

How long is a Saudi IBAN?

A Saudi Arabian IBAN has 24 characters: SA, two check digits, a 2-digit bank code and an 18-character account number. The bank code is characters 5 and 6, so in the registry example SA03 8000 0000 6080 1016 7519 it is 80.

Technical notes

An IBAN (ISO 13616) is a two-letter ISO 3166 country code, two check digits and the Basic Bank Account Number (BBAN), the account number in the country's own layout. The SWIFT IBAN Registry, maintained by SWIFT as the ISO 13616 registration authority, fixes each country's total length (15 for Norway, 24 for Saudi Arabia, up to 33 for Russia) and the BBAN structure in its own notation: 2!n18!c means exactly 2 digits then exactly 18 letters or digits.

The checksum is ISO 7064 MOD 97-10. Move the country code and check digits to the end, replace every letter with two digits (A = 10 … Z = 35) and take the remainder of the whole number divided by 97: a correct IBAN leaves 1. The check digits are issued as 98 minus the remainder computed with 00 in their place, so they always fall between 02 and 98; the tool works the remainder out in seven-digit pieces, so numbers of 30 digits and more lose no precision.

The registry also gives the position of the bank identifier and, for some countries, the branch identifier inside the BBAN — for example characters 5–6 in Saudi Arabia, 5–12 (the BLZ) in Germany, 5–8 (the bank's letters) and 9–14 (the sort code) in the United Kingdom. The tool extracts exactly those characters as text, so a leading zero stays part of the code.

Many countries add their own check digits inside the BBAN (the French RIB key, the Italian CIN, the Belgian and Norwegian account-number checks). Those national rules are not part of ISO 13616 and are not verified here.

Validating the Saudi registry example: move the first four characters to the end, turn letters into numbers, divide by 97. A remainder of 1 means the check digits fit; any other remainder means a typing mistake.
  1. 1Move the country code and check digits to the endThe BBAN comes first, then SA03.80000000608010167519SA03
  2. 2Replace letters with numbersA=10 … Z=35, so S=28, A=10.80000000608010167519281003
  3. 3Divide by 97 and keep the remainderThe 26-digit number, in pieces of seven digits so nothing is rounded.mod 97 = 1
  4. 4Remainder 1: the checksum is correctTogether with the right length and structure, the IBAN is valid in form. Its owner is not checked.Pass

Limitations and methodology

Formats come from the SWIFT IBAN Registry as bundled with the page; a country added to the registry later is reported as not verifiable until the page is updated.

No bank directory is bundled and no bank or account-verification service is connected: the tool cannot show a bank name, a BIC, whether the account is open, or the account holder's name.

National check digits inside the BBAN are not verified, and a wrong account number whose check digits happen to match passes the checksum.

Territories that use another country's IBAN format (for example French overseas departments with FR) are checked as that country.

Security and privacy

The IBAN is checked in your browser and never sent to Mutqan, a bank or any other service; it is not stored, logged or included in analytics.

Treat an IBAN as personal financial data: share it only with people who need it, and confirm payment details through a channel you already trust, because fraudsters often send a "new IBAN" that passes every check.

References