An IBAN (International Bank Account Number) is a globally standardized format for identifying bank accounts across borders. Developed by the International Organization for Standardization (ISO 13616) and the European Committee for Banking Standards, the IBAN was created to simplify and speed up international money transfers while reducing errors. Today it is used in over 80 countries and territories, and it serves as the backbone of the Single Euro Payments Area (SEPA) payment network. Whether you are a freelancer invoicing a client in another country, a business paying overseas suppliers, or an individual sending money to family abroad, understanding the IBAN is essential to making sure your money arrives quickly, safely, and without unnecessary fees.
Before IBANs, each country had its own account numbering system. A transfer from Germany to France required the sender to know the recipient's bank code, branch code, and account number — all in different formats. Errors were common, and misrouted payments caused delays and extra fees. The IBAN was introduced in the late 1990s to solve this by wrapping all account identifiers into a single, validated string.
The concept of a universal bank account identifier was first proposed by the European Committee for Banking Standards in 1997. The initial standard, ECBS EBS 204, was later formalized as ISO 13616 in 2003. The European Union made IBANs mandatory for cross-border euro payments in 2006 through Regulation (EC) No 924/2009, and later required them for all domestic euro payments by February 2014 under the SEPA end-date regulation. These regulatory mandates drove rapid adoption, and today the SWIFT IBAN Registry lists over 80 participating countries.
The history of the IBAN is marked by a series of key milestones that gradually transformed international payments. In 1997, the European Committee for Banking Standards published the first IBAN specification. In 2003, the ISO formally adopted the standard as ISO 13616-1 and ISO 13616-2, establishing the rules for IBAN structure and the registry of country-specific formats. By 2006, European Union regulation required that all cross-border euro credit transfers use IBANs, and in 2008 the Single Euro Payments Area officially launched with the IBAN as its primary account identifier. February 2014 marked the final deadline for all eurozone countries to migrate their domestic payment systems to IBAN-based formats. Outside Europe, countries in the Middle East, North Africa, and the Caribbean adopted the IBAN throughout the 2010s, with nations such as Saudi Arabia (2009), the UAE (2011), and Brazil (2013) rolling out their own IBAN formats. The standard continues to expand, with new countries joining the registry each year.
Every IBAN contains four key parts, always in the same order:
The length varies by country — from 15 characters (Norway) to 34 characters (Malta). The check digits allow software to detect transcription errors with over 99% accuracy before the transfer is even sent. You can explore the exact format for each country in our IBAN format by country reference guide.
The MOD-97 validation algorithm works by rearranging the IBAN so that the country code and check digits move to the end, converting all letters to numbers (A = 10, B = 11, and so on), and then computing the remainder when dividing by 97. A valid IBAN always produces a remainder of 1. This simple yet effective mechanism catches single-digit errors, transposition errors (swapping two adjacent digits), and most other common transcription mistakes.
One of the most common misunderstandings about IBANs is that they replace your domestic bank account number. In reality, an IBAN is a wrapper around your existing domestic account details. Your bank code, branch identifier, and account number are all embedded within the IBAN — the system simply adds a standardized country code and check digits to the front.
For example, a German customer with bank code 37040044 and account number 0532013000 receives the IBAN DE89 3704 0044 0532 0130 00. The domestic numbers are preserved in their entirety. Similarly, a UK customer with sort code 601613 and account number 31926819 gets the IBAN GB29 NWBK 6016 1331 9268 19, which includes the bank identifier (NWBK for NatWest), the sort code, and the account number. This wrapping approach means that countries did not need to redesign their entire banking infrastructure — they simply layered the IBAN standard on top of existing systems.
Over 80 countries and territories use the IBAN system today. It is mandatory across all European Union and European Economic Area member states. Many countries in the Middle East (such as Saudi Arabia, the UAE, and Qatar) and parts of Africa and the Caribbean have also adopted it. The United States, Canada, Australia, and most of Asia have not adopted IBANs — they continue to use domestic formats like routing numbers. For a comprehensive list, see our which countries use IBAN guide.
The SWIFT IBAN Registry is the official reference document maintained by SWIFT on behalf of ISO. It lists every country that has formally registered an IBAN format, along with the exact structure, length, and example IBANs. Banks and payment processors worldwide rely on this registry to validate incoming IBANs and route payments correctly.
People frequently confuse IBANs with SWIFT codes (also called BIC codes). While both are used in international transfers, they serve different purposes. An IBAN identifies a specific bank account — it tells the banking network exactly where the money should be deposited. A SWIFT/BIC code identifies the bank itself and is used to route the message through the SWIFT network. For cross-border transfers outside SEPA, you typically need both: the IBAN to identify the account and the SWIFT/BIC code to identify the institution. Within the SEPA zone, however, the IBAN alone is usually sufficient because European clearing systems can derive the bank from the IBAN structure.
A SWIFT/BIC code is either 8 or 11 characters long and follows the format NWBKGB2L (bank code, country code, location code, and optional branch code). The IBAN, by contrast, can be anywhere from 15 to 34 characters and always begins with a country code followed by check digits. If someone asks you for your "IBAN or SWIFT," they may need both pieces of information — do not assume one substitutes for the other.
The IBAN is the backbone of the Single Euro Payments Area (SEPA), which allows fast, low-cost euro transfers across 36 European countries. For SEPA credit transfers and direct debits, only the IBAN is required — no separate SWIFT/BIC code is needed. This makes cross-border euro payments as simple as domestic ones.
The European Payments Council governs the SEPA scheme rules and publishes the SEPA rulebooks that define how IBANs must be used in credit transfers, direct debits, and instant payments. Under SEPA, a payment from a bank in Portugal to a bank in Finland is processed in the same way and at the same cost as a domestic transfer. This level of harmonization would not be possible without the IBAN as a universal account identifier.
Despite its design for error reduction, several common mistakes continue to cause failed or misrouted payments:
DE89 3704 0044 0532 0130 00), but the electronic format contains no spaces. Some input fields accept spaces and some do not — always check.An IBAN is not a secret — it is the equivalent of your postal address for banking. You need to share it so that people and organizations can send money to you. Businesses routinely print their IBANs on invoices, and employees share their IBANs with payroll departments. Knowing someone's IBAN does not grant access to their account or allow withdrawals without proper authorization.
That said, you should still exercise reasonable caution. While an IBAN alone cannot be used to steal money from your account, it can be combined with other personal information in social engineering attacks. Fraudsters may use a known IBAN to impersonate your bank or trick you into authorizing payments. Best practices include: sharing your IBAN only with trusted parties, verifying unexpected payment requests through a separate communication channel, and monitoring your account for unauthorized direct debit mandates. In the SEPA zone, you have the right to request a refund for unauthorized direct debits within 13 months of the transaction date.
Whenever you receive an IBAN, it is good practice to validate it before initiating a transfer. Our free IBAN validator checks the country code, length, structure, and MOD-97 checksum in real time, and shows a full breakdown of the bank and account details embedded in the number. All validation runs entirely in your browser — no data is sent to any server.
Back to all guides.