BankCodeKit

Guide

IBAN vs BIC vs SWIFT Codes

Compare IBAN, BIC, and SWIFT codes in payment details. Learn which value identifies account format, which identifies bank format, and what neither value proves.

Who this guide is useful for

Freelancers, accountants, developers, and payment operations teams explaining why forms may ask for both values.

IBAN, BIC/SWIFT and SEPA at a glance

Payment-code roles and BankCodeKit checks
Item Role What BankCodeKit can check What it cannot confirm
IBAN Account identifier format Country support, expected length, allowed characters, and MOD97 checksum. Real account existence, account owner, bank reachability, or payment success.
BIC/SWIFT Financial institution or business identifier format 8- or 11-character structure, country-code position, location segment, and branch-code format. Licensed directory status, live Swift connectivity, or whether a bank can receive a payment.
SEPA Euro payment area and scheme-country context Country-level SEPA status from local reference data. Specific bank participation, account eligibility, SEPA Instant support, or payment readiness.
Invoice reference Payment matching text used by the recipient Formatting support when you build a copyable payment-details block. Invoice authenticity, payee identity, or whether the reference is commercially correct.

The practical difference

IBAN, BIC, and SWIFT codes are often shown together on invoices and payment forms, but they do not prove the same thing. An IBAN describes an account-number format, while a BIC/SWIFT code describes a bank or business identifier format.

  • IBAN: account-number format, country-specific length, and checksum structure.
  • BIC/SWIFT: 8 or 11 character business or bank identifier format.
  • IBAN checks can review country, length, characters, and checksum.
  • BIC checks can review segment placement, country-code position, and optional branch format.

When an IBAN may be used

IBANs are commonly used for payments involving countries that support the IBAN standard. The IBAN helps software and users catch format or checksum mistakes before using the value.

  • Some payment forms ask for IBAN only when the provider can derive the required routing context.
  • A local IBAN check still does not confirm account existence, ownership, reachability, or payment success.
  • A country-specific IBAN length can be valid while the recipient details still need bank or invoice confirmation.

When a BIC/SWIFT code may be used

A payment form may ask for a BIC/SWIFT code when the receiving bank identifier is required. Requirements vary by bank, country, currency, and payment provider.

  • BIC8 can identify the visible party and country-level structure.
  • BIC11 adds a three-character branch identifier when a branch-level value is provided.
  • A BIC format match does not confirm licensed directory status or Swift network connectivity.

What neither value proves

IBAN and BIC/SWIFT values can be structurally well-formed without proving that they belong together or that a real payment should be sent.

  • They do not prove payee identity or invoice authenticity.
  • They do not screen sanctions, fraud risk, fees, delivery time, or provider restrictions.
  • They do not replace confirmation with a bank, payment provider, invoice issuer, or recipient.

Practical payment detail example

An invoice for an international transfer may list both values so the payer can enter the account identifier and the bank identifier.

  • IBAN field: DE89 3704 0044 0532 0130 00
  • BIC/SWIFT field: DEUTDEFF
  • Reference field: Invoice 2026-1042
  • These fields still need confirmation from the invoice issuer or bank before payment.

Important limitations

Format checks only. This guide does not confirm account existence, ownership, bank reachability, or payment success. Read the detailed disclaimer for the full limitation list.

  • Matching-looking IBAN and BIC values do not prove they belong together.
  • Neither field confirms account ownership.
  • Neither field confirms payment readiness or payment success.
  • Payment requirements can vary by provider and transfer type.

FAQ

Do I always need both an IBAN and a BIC?

Not always. Requirements depend on the payment route, bank, country, currency, and provider.

Which one identifies the account?

The IBAN is the account identifier format. The BIC/SWIFT code is a bank or business identifier format.

Can one be valid while the other is wrong?

Yes. IBAN and BIC checks are separate format checks and do not confirm the values belong together.

Can I convert an IBAN to a SWIFT/BIC code?

No. BankCodeKit does not convert IBAN to SWIFT/BIC. Use the IBAN Checker for account-number format, the BIC/SWIFT Checker for bank identifier format, and verify real payment requirements with your bank or provider.

What should I verify before sending money?

Verify the payee, amount, currency, reference, IBAN, BIC if required, and payment instructions through a trusted source.

Sources and update note

BankCodeKit keeps payment-code checks browser-local and uses local reference data for format and country information. Local IBAN data was reviewed 2026-06-28 against Swift IBAN Registry Release 102 - Jun 2026. Official public source pages are used for reference, but BankCodeKit does not perform live bank, account, sanctions, or payment-network confirmation.

Format checks only. This page does not confirm account existence, ownership, bank reachability, or payment success. Read the detailed disclaimer.

Last reviewed: 2026-06-28 Sources: Swift IBAN Registry, Swift BIC / ISO 9362 information, European Payments Council SEPA scheme countries list Reference data is reviewed periodically. BankCodeKit does not perform live bank, account, sanctions, or payment-network confirmation.