IBAN
Also known as: IBAN number, International Bank Account Number, bank account number (international), SEPA account identifier
An IBAN (International Bank Account Number) is a standardized format for identifying bank accounts used in international payments.
It consists of a 2-letter country code, 2 check digits, and a country-specific account identifier (up to 30 characters). IBANs are used in 80+ countries, covering the entire EU/EEA, the UK, the Middle East, and many other regions. The standard (ISO 13616) enables automated processing of international payments by uniquely identifying the exact account without ambiguity. The US, Canada, and Australia do not use IBANs domestically but can receive IBAN-based payments from international senders.
IBAN, explained at three levels
At home
An IBAN is your bank account's international address. If you have a bank account in the UK, your IBAN looks like GB29NWBK60161331926819. If someone outside your country needs to send you money, you give them your IBAN instead of just your account number: it contains all the information needed to identify your country, bank, and account. You can find your IBAN on your bank statement or in your bank's mobile app.
At work
If your business receives payments from European or Middle Eastern clients, they will ask for your IBAN to set up payments to you. If your bank account is in the EU, your IBAN starts with your country code (DE for Germany, FR for France, NL for Netherlands, etc.) and encodes your account details in standardized format. Providing the correct IBAN to clients prevents payment delays caused by incorrect account details: IBAN validation checks catch most format errors before the payment is submitted.
At home
IBAN structure: the first 2 characters are the country code (GB, DE, FR, etc.); the next 2 are check digits calculated from the remaining characters (allowing software to verify the IBAN has not been mistyped); the remaining characters are the BBAN (Basic Bank Account Number) in country-specific format. The UK BBAN encodes sort code + account number; German IBANs encode bank code + account number. Online IBAN validators can verify whether a given IBAN is structurally valid, though not whether the account actually exists and is active.
At work
SEPA (Single Euro Payments Area) transfers use IBANs and are processed like domestic payments across about 40 European countries: same-day or next-day processing within the SEPA zone, with no correspondent bank fees. For a UK business paying a German supplier in euros via SEPA credit transfer, the payment is straightforward, fast, and low-cost compared to a SWIFT wire. For the same payment in a non-euro currency, SWIFT would be used. Understanding the SEPA zone vs. non-SEPA international payment distinction is important for payment cost and speed planning.
At home
The absence of IBANs in the US creates friction for international payments. When a US company pays a European supplier, the European company provides an IBAN; the US company's bank processes it via SWIFT. When a European company pays a US company, they ask for routing number + account number, which does not have the same validation properties as IBAN, leading to more payment errors and manual review. Fintechs such as Wise give customers in the US and Canada their own euro account details with an IBAN, making SEPA payments easier to receive.
At work
IBAN validation in payment systems is a critical input validation requirement: accepting IBAN-based payments without validation allows entry of clearly invalid IBANs (wrong country code, wrong length, failed check digit), leading to payment failures and manual intervention. Most payment APIs (Stripe, GoCardless for SEPA) validate IBANs at the point of entry. For custom-built payment intake forms, an IBAN validation library should be integrated: IBAN format is fully algorithmic (the check digit algorithm is public), making real-time validation possible without external API calls.
Real-world examples
At home
Nadia was a freelancer in the Netherlands receiving payment from a UK client. She provided her Dutch IBAN (starting NL) and the client's bank processed it via SEPA credit transfer. The payment arrived the next business day with no fees deducted, the same speed and cost as a domestic transfer. She compared this favourably to a non-EU client who sent a SWIFT wire that took three days and arrived with correspondent bank fees.
At work
Thomas managed accounts receivable for a UK company that invoiced European clients. He added the company IBAN to all invoices for European clients and included a note distinguishing SEPA payments (same-day/next-day, no fees) from SWIFT wires (2-3 days, fees possible). European clients defaulted to SEPA once they knew it was available, improving the company's days-sales-outstanding (DSO) metric as payments arrived faster.
Common confusions
- Many non-European businesses assume IBAN validation guarantees the account exists and belongs to the named person — IBAN validation (checking the structure and check digits) confirms the IBAN is formatted correctly: it does not confirm the account is active, belongs to the named recipient, or that the payment will be accepted. A structurally valid IBAN for a closed account will pass format validation but fail when the payment is submitted. For high-value payments or new payment relationships, account verification (in the UK, the Confirmation of Payee service; similar services exist elsewhere) is a separate step from IBAN validation.
- Some UK businesses assume that after Brexit they no longer use IBANs or SEPA — The UK still uses IBANs, and it also stayed in the SEPA payment schemes after Brexit: the European Payments Council approved continued UK participation in 2019. UK banks can still send and receive SEPA euro transfers, but because the UK is now outside the EU, payments between the UK and EU must carry extra information, such as the payer's address. What changed is the regulatory status, not the IBAN format or access to SEPA.
For analysts
When reviewing a client's invoicing templates or payment intake processes for international customers, verify that IBANs are displayed correctly on invoices to European clients (IBAN + BIC/SWIFT code), that payment intake forms validate IBAN format before accepting customer entries, and that the client understands the distinction between SEPA and SWIFT payments for European transactions. These practical payment operations details are often overlooked in financial systems implementations.
History & origin
IBANs were developed in the 1990s by the International Organization for Standardization (ISO) and the European Committee for Banking Standards (ECBS) to standardize cross-border payment processing within Europe. The EU mandated IBAN adoption for all bank accounts in EU member states as part of the Single Euro Payments Area (SEPA) initiative, with full migration required by 2014. SEPA made EU cross-border euro payments as straightforward as domestic payments, using IBANs as the single account identifier format. IBAN adoption has since spread beyond Europe through SWIFT's support for IBAN in payment messages. The UK retained IBAN post-Brexit. The US and Canada developed alternative standards (routing number + account number for ACH/wire) and have not adopted IBAN for domestic use.