What Is a BIC (Bank Identifier Code)
A BIC, Bank Identifier Code, is the unique identifier assigned to a financial institution for the purpose of international transfers. When you send money across borders through the traditional banking system, the BIC tells the network exactly which bank should receive it, in which country, and at which branch. Without it, a cross-border payment has nowhere to go. It is sometimes called a SWIFT code because SWIFT is the organisation that issues and maintains the registry; the two terms refer to the same thing.
What the Code Actually Contains
A BIC isn't arbitrary. Each section of the code carries specific routing information, and understanding the structure helps explain why international transfers work the way they do.
A standard BIC is either eight or eleven characters:
- First four characters: the institution code, identifying the bank itself (e.g., HSBC, Barclays, JPMorgan)
- Next two characters: the country code, in ISO format (GB for the UK, US for the United States, DE for Germany)
- Next two characters: the location code, identifying the city or region of the bank's head office
- Final three characters: optional branch code; when omitted, the code defaults to the bank's primary office
So a BIC like HBUKGB4BXXX breaks down as: HBUK (HSBC Bank), GB (United Kingdom), 4B (London), XXX (primary office). That eight-character string is enough to route a payment to the right institution. The branch code adds precision when a specific office needs to receive funds directly.
What Is a BIC and What Does It Do in a Real International Transfer
The meaning of a BIC becomes clear when looking at how a cross-border payment is routed between banks.
A BIC (Bank Identifier Code) is used to identify the receiving financial institution and guide the payment through the SWIFT network. It does not move funds itself, but it determines the path the payment will take.
In practice, when a US company sends €85,000 to a German supplier, the payment instruction includes both the supplier’s IBAN and BIC. The sending bank uses the BIC to identify the destination bank and determine how the payment should be routed.
If a direct relationship exists, the transfer may complete in a single step. More commonly, the payment passes through one or more intermediary correspondent banks. Each institution in that chain is identified using its own BIC as the payment message moves through the network.
This routing structure introduces several effects:
- Additional processing time as each bank handles the payment in sequence
- Fees deducted by intermediary institutions
- Potential delays if compliance checks or cut-off times are triggered
The meaning of the BIC is functional rather than causal. It enables routing across the correspondent banking network, but the friction comes from the structure of that network itself, not from the identifier.
Where This Gets Complicated for Treasury Teams
The operational challenge with BIC-based routing isn't the code itself; it's everything that comes with it:
- Correspondent bank fees are unpredictable and deducted mid-transfer, meaning the recipient often receives less than the amount sent
- Settlement timelines vary depending on which intermediaries are in the chain, their cut-off times, and whether any compliance review is triggered along the way
- Traceability is limited; once a payment enters the SWIFT network, tracking exactly where it is requires manual follow-up with the sending bank
- Currency conversion often happens at an intermediary stage, at a rate the originator has no visibility into until after the fact
For a finance team running high volumes of international vendor payments, these variables compound. Each unresolved payment requires investigation, each fee discrepancy needs reconciliation, and each delayed settlement affects working capital forecasting.
How Virtual IBANs Change the Routing Problem
Merge's virtual IBANs give counterparties a local bank account number to pay into, in their own currency, in their own region, without the sending party needing to navigate correspondent banking chains or supply a BIC at all. The payment arrives locally, and Merge handles the conversion and settlement on the other side. The BIC routing layer still exists underneath, but it is abstracted away from the treasury team's workflow entirely.
For the German supplier in the example above, this means receiving payment into what looks like a local euro account. For the US company's finance team, it means initiating a transfer without managing routing codes, intermediary bank relationships, or unpredictable fee deductions.
Merge Transfer handles the cross-border leg, and Merge Reconcile maps each inbound or outbound transaction to the corresponding invoice, so the operational overhead of international payments doesn't land on the finance team to sort out manually.
FAQ
What is a BIC code used for?
A BIC (Bank Identifier Code) identifies a specific financial institution in an international transfer. It tells the SWIFT network which bank should receive the payment, in which country, and at which office. Every bank that participates in international wire transfers has one, and it is required alongside an IBAN to route a cross-border payment correctly.
Is a BIC the same as a SWIFT code?
Yes. BIC and SWIFT codes refer to the same identifier. SWIFT, the Society for Worldwide Interbank Financial Telecommunication, is the organisation that assigns and maintains these codes globally. The terms are used interchangeably in banking, though "SWIFT code" is more common in everyday use and "BIC" is the formal ISO standard designation.
Do stablecoin transfers require a BIC?
No. Stablecoin payments route via wallet addresses on a blockchain, not through the correspondent banking network that BICs are designed to navigate. This removes the multi-hop routing, intermediary fees, and settlement delays that come with BIC-based international transfers, which is a significant part of why enterprise treasury teams are moving cross-border B2B payments onto stablecoin rails.