IBAN doesn’t move money—it stops you from typing it wrong.
IBAN is a validation layer—not a payment rail, not a registry, not a protocol. It catches human input errors in account identifiers before they trigger costly rejections downstream. Its mechanism is simple: a fixed-position country code, two check digits, and a national account identifier, all validated via MOD-97-10. It works where people type numbers. It fails where logic, intent, or authority is required.
IBAN uniquely identifies a customer’s account across borders to cut transcription errors in cross-border transactions.
2:33
How does it work?
It uses a fixed-format string with MOD-97-10 check digits to validate routing and account number at entry.
3:46
What actually works?
The check digits catch typos, transpositions, omissions, and duplications—guaranteed.
5:10
Who owns it—and when?
ISO published it as 13616 in 1997; SWIFT now maintains the 2020 version.
6:27
Where does it sit in the standards ecosystem?
It is one of over 25,000 ISO standards, developed through a formal six-stage technical committee process.
7:44
What does it *not* do?
It reduces risk—but only for transcription. Not fraud, not compliance, not availability.
Worth your time?
Yes. Study the whole thing.
4/ 5
What works
detects transcription errors with mathematical certainty
enables pre-routing validation
standardises account identification across jurisdictions
What does not
prevent fraud
authorise payments
replace local clearing rules
guarantee account validity
Study it if
cross-border payment operators
banking software developers
compliance teams handling SEPA or SWIFT
Skip it if
domestic-only institutions
end consumers sending occasional transfers
blockchain wallet users
The written brief1 min read
What it is and the problem it solves
IBAN is an internationally agreed system for identifying bank accounts across borders. It solves the problem of transcription errors in cross-border transactions.
How it works
IBAN imposes a flexible but regular format with embedded check digits calculated using MOD-97-10 as defined in ISO/IEC 7064:2003.
What works
The check digits reliably detect single-character omissions, duplications, mistypings, and transpositions of two adjacent characters. They enable a real-time sanity check of routing destination and account number at data entry.
What does not
IBAN does not prevent fraud, authorise payments, or replace local clearing rules. It does not guarantee transaction success if the underlying account is closed, frozen, or misconfigured.
What it changes
It shifts error detection from the receiving bank’s back-end to the sender’s data entry point—reducing failed transfers caused by typos, transpositions, omissions, or duplications.
Is it worth your time
Yes—if you process cross-border payments and need to catch transcription errors before routing fails. No—if you operate only domestically or rely on intermediary systems that already validate IBANs.