IBAN

IBAN is the account number standard that underpins European bank-to-bank payments and is a prerequisite for SEPA transactions. For payment operators routing funds across European banking infrastructure, correctly formatting and validating IBANs is a basic operational requirement.

IBAN Structure

An IBAN consists of up to 34 alphanumeric characters:

1. Country code (2 letters): ISO 3166-1 alpha-2 country code (e.g., DE for Germany, GB for the United Kingdom, NL for Netherlands)
2. Check digits (2 digits): Used to validate the IBAN using the MOD-97 algorithm
3. Basic Bank Account Number (BBAN): Country-specific account number format, which may include bank code, branch code, and account number

Example: DE89 3704 0044 0532 0130 00 is a German IBAN. The BBAN (370400440532013000) encodes the bank sort code and account number in German format.

IBAN lengths are fixed per country and defined in the SWIFT IBAN registry. Validating an IBAN requires both format validation (correct length for the country, only valid characters) and check digit verification.

SEPA and IBAN

SEPA (Single Euro Payments Area) mandated IBAN as the sole account identifier for euro-denominated credit transfers and direct debits within the zone, which covers 36 countries including all EU member states, Iceland, Liechtenstein, Norway, and several non-EU countries.

Before SEPA, domestic bank account formats varied: Germany used Bankleitzahl + Kontonummer, France used RIB codes, the UK used sort code + account number. SEPA migration standardized these onto IBAN, though the underlying domestic account structures are encoded within the IBAN BBAN.

IBAN vs. SWIFT/BIC

IBAN identifies the account. BIC (Bank Identifier Code, also known as SWIFT code) identifies the institution. For cross-border payments, both were historically required, but SEPA transactions within the zone now require only the IBAN — the bank routing can be derived from the IBAN. For non-SEPA international wires, both IBAN and BIC/SWIFT remain required by most correspondent banking networks.

IBAN Adoption Outside Europe

IBAN adoption beyond Europe is uneven:

• Middle East and North Africa: Several countries (UAE, Saudi Arabia, Lebanon) have adopted IBAN
• Americas: Not adopted — the US, Canada, and most of Latin America use domestic routing number systems (ABA routing numbers in the US, CLABE in Mexico)
• Southeast Asia: Not adopted. APAC bank accounts use domestic formats specific to each country: BSB + account number in Australia, SWIFT + account number for international, and various domestic real-time payment identifiers (PayNow proxy in Singapore, PromptPay in Thailand, GoPay/bank account in Indonesia)

Operational Relevance for PSPs

PSPs settling funds to European merchants, processing SEPA Direct Debits for subscription billing, or handling payouts to European bank accounts must manage IBAN validation and formatting. Common operational issues include:

• Receiving IBAN in print-formatted (space-separated) vs. electronic (no spaces) format and normalizing correctly
• Validating IBANs before submission to avoid failed payments and the associated fees
• Storing IBANs securely as they constitute sensitive financial account information

For global payment platforms, IBAN sits alongside account number + routing number (US/Canada), sort code + account number (UK), and regional equivalents as one of several account identifier formats that must be supported in payout infrastructure.