Guide · 4 min read

IBAN vs BIC: the difference, and when you need each one

Last updated 17 July 2026

IBAN and BIC answer two different questions. The IBAN answers “which account?”; the BIC answers “which bank?”. Payments need the account, routing needs the bank — which is why forms keep asking for both.

Side by side

IBANBIC / SWIFT
IdentifiesA specific bank accountA financial institution (or branch)
StandardISO 13616ISO 9362
Length15–34 chars (fixed per country)8 or 11 characters
ContainsCountry, check digits, bank code, accountBank, country, location, optional branch
Validated bymod-97 checksum (offline)Registry lookup (SWIFT directory)
ExampleIT60 X054 2811 1010 0000 0123 456UNCRITMMXXX

When is the BIC still required?

SEPA regulation introduced the “IBAN-only” rule for consumer payments inside the area, so a typical bank transfer form now needs just the IBAN. But the BIC never disappeared from the plumbing: banks derive it internally to route, and plenty of B2B flows still require it explicitly.

  • ISO 20022 / pain.001 batch files with mandatory agent (BIC) fields.
  • Cross-border wires outside SEPA, where correspondent routing needs the institution.
  • PSPs and marketplaces validating payout destinations before onboarding a seller.
  • Treasury systems reconciling which institution actually holds a counterparty account.

You have the IBAN — getting the BIC

The BIC is not a substring of the IBAN, but the IBAN’s embedded bank code maps to it. Resolving that mapping requires per-country registry data (Bundesbank BLZ files in Germany, ABI tables in Italy, and so on). A single API call to iban2bic returns the BIC, bank name, address and SEPA scheme reachability for any SEPA IBAN — at €0.009 per successful lookup.

Frequently asked

Related guides

Resolve IBANs to BICs programmatically

One endpoint returns the BIC, bank details and SEPA reachability for any SEPA IBAN — €0.009 per successful call, failures always free.