DEV Community

wangxiaolou
wangxiaolou

Posted on Originally published at xiaohongshudownloader.hashnode.dev

How to Check an IBAN Before You Send an International Transfer

You have a recipient's account number and a transfer form open. The amount is ready. The only thing standing between you and a returned or misrouted payment is whether that string of letters and digits is actually an IBAN — and whether it was copied without a typo.

A domestic account number pasted into an IBAN field, a country code off by one letter, or a truncated copy-paste is easy to miss on the form itself. What you need before you click send is narrower than a full bank inquiry: a format check, a breakdown of the country and bank segments, and, when the form also asks for it, the receiving bank's SWIFT/BIC code.

That is the job of a browser IBAN toolkit. One example is IBANtool, which checks an IBAN's format, length, and ISO 13616 check digits in the browser, and can look up or decode a SWIFT/BIC from a bundled bank directory. This article walks through how to use that kind of workflow well: what a "valid" result actually means, how to read the breakdown, when you also need a SWIFT code, and what you still have to confirm with the recipient.

A green check is not proof the account exists

An IBAN (International Bank Account Number) is a standardized way to identify a bank account across borders, defined by ISO 13616. It starts with a two-letter country code, two check digits, and a country-specific Basic Bank Account Number (BBAN). Total length is fixed per country. On IBANtool's documented range, that runs from 15 characters in Norway to 34 characters in the longest national formats.

A format checker typically does three things:

  • Confirms the character set: letters A–Z and digits 0–9 only, after spaces are stripped.
  • Checks that the length and BBAN pattern match the rules for that country — for example 22 characters for Germany (DE), 27 for France (FR), 22 for the United Kingdom (GB), or 18 for the Netherlands (NL).
  • Computes the MOD 97-10 checksum. After rearranging the IBAN and converting letters to numbers, a well-formed value yields a remainder of 1.

Passing those checks only shows that the string matches the implemented format and checksum rules. It does not prove the account exists, is open, belongs to a particular person, or can receive funds. It also does not run national domestic check-digit algorithms, or query a live bank directory to verify the account. Always confirm the IBAN with the recipient or their bank before you send money.

Paste the IBAN and read the breakdown

Open the IBAN validator in a normal browser. You do not create an account.

Paste or type the IBAN into the field. Spaces are fine; they are stripped automatically. Then look at the result panel:

  • A green check means the format, country length, BBAN pattern, and MOD 97 checks all passed.
  • If a check fails, the tool shows which layer failed — so you can tell a typo in the country code from a missing digit or a bad checksum.
  • Read the breakdown of country code, check digits, and BBAN. The country should match where you think you are sending money. A DE prefix on a payment you expected to go to Denmark (DK) is a different country, a different required length, and a different checksum.

The page also has a load-example menu with known-good public fixtures for supported countries, useful if you want to see a passing result before you paste a real number. Treat those examples as demonstrations, not as accounts you can pay.

Common reasons a check fails are almost always about the input:

  • A typo in the country code ("DE" vs "DK")
  • Missing or extra characters (a German IBAN must be exactly 22 characters once spaces are removed)
  • Wrong check digits after a single mistyped character
  • A domestic account number pasted as if it were an IBAN

If the value fails, stop and get a fresh copy from the recipient — a bank statement, official payment instructions, or their online banking — rather than editing digits yourself.

The validator runs in your browser. IBANtool states that the IBAN you enter is not uploaded as a tool input; ordinary page requests may still be processed by hosting and analytics services.

You often need a SWIFT code as well

An IBAN identifies a specific account. A SWIFT code, also called a BIC (Business Identifier Code, ISO 9362), identifies a bank or branch. For many international transfers, especially to Europe, you need both: the BIC to route the payment to the institution, and the IBAN to credit the right account. In corridors that do not use IBANs, the bank will ask for a local account number plus routing details instead.

A SWIFT/BIC is 8 or 11 characters:

  • Characters 1–4: bank code
  • 5–6: country
  • 7–8: location (a city or processing centre)
  • 9–11: optional branch code. An 8-character code points to the head office. If a form requires 11 characters and you only have eight, the usual convention is to append XXX for the primary office rather than leave the field short.

The same bank brand can have different BICs in different countries, and a familiar-looking code can still point to the wrong legal entity. The receiving bank's current instructions should take priority over an old directory listing or an old statement.

IBANtool's SWIFT/BIC lookup lets you search by bank name or country, or paste an 8- or 11-character code to decode the bank, country, location, and branch blocks. It runs in the browser and uses a bundled directory of major head-office codes — a practical aid, not a complete registry of every branch worldwide. Narrow by country when two banks share a similar name, and prefer the legal bank name (for example "MUFG Bank") over a short brand. If no match appears, or you need a branch-specific code, use the recipient's official instructions.

The site also offers an IBAN-to-SWIFT helper: it extracts the country and the bank segment from the IBAN and checks that segment against its directory. An IBAN does not contain the BIC itself, so a miss is possible. Do not invent a BIC from the bank code. If there is no exact match, go back to the recipient's bank.

Confirm, then send

A pre-flight check is useful because it is cheap and reversible. A format failure is a reason to stop. A format pass is a reason to proceed to confirmation, not a reason to skip it.

Before you submit the transfer:

  • The IBAN's country code matches the destination you were given
  • The SWIFT/BIC, if required, matches the named bank and country on the invoice or payment instructions
  • The beneficiary name and any reference the bank requires are copied from the same official source, not from a chat typo
  • You have confirmed the details with the recipient or their bank

Do not use a synthetic IBAN from a generator as a real payment destination. Those values are test fixtures designed to pass checksums; they are not verified accounts.

The toolkit will not tell you that an account is open, that a name matches, or that a bank still accepts a particular BIC. It is not a Verification of Payee service, a live SWIFT registry terminal, or a substitute for bank confirmation. IBANtool is not affiliated with SWIFT, ISO, or any bank.

Used that way, the workflow is short: paste the IBAN, read the breakdown, look up the BIC if the form asks for one, and only then send the payment you have already confirmed.

Top comments (0)