SWIFT Code

A SWIFT code is the common banking name for a Business Identifier Code (BIC), an 8-character identifier for an organization in financial-services data with an optional 3-character identifier for a branch, department, service, or other organizational unit. A BIC identifies a business party; it does not identify the beneficiary’s individual bank account.

The International Organization for Standardization defines the BIC structure in ISO 9362, and SWIFT acts as the registration authority. The terms SWIFT code and BIC are commonly used interchangeably, but having a valid BIC does not necessarily mean the organization can connect directly to the SWIFT network.

Key Takeaways

• BIC is the formal standardized name; SWIFT code is the familiar banking term.
• A BIC contains 8 characters, with an optional 3-character branch identifier for an 11-character form.
• The code identifies a financial or non-financial organization and, optionally, one of its organizational units.
• A BIC is not an account number, IBAN, domestic routing number, payment reference, or proof of account ownership.
• Connected BICs can be used by organizations with access to SWIFT messaging; non-connected BICs can be used as reference identifiers without direct network access.
• A syntactically correct BIC does not prove that the code is current, connected, appropriate for the payment route, or supplied by the genuine beneficiary.
• Payment instructions should be obtained from a trusted source and independently verified when they are new, changed, urgent, or unusual.

SWIFT Code Format

Under the current ISO 9362 terminology, the BIC structure is:

BBBBCCSS[XXX]

The characters are contiguous. Spaces or hyphens may appear in explanatory formatting, but they are not part of the BIC itself.

Older explanations often call the first four characters the bank code and the following two-character suffix the location code. Current ISO terminology uses business party prefix and business party suffix because BICs can identify financial and non-financial organizations, not only banks.

BIC8 vs. BIC11

An 8-character BIC identifies the business party. Adding the optional 3-character branch identifier creates an 11-character BIC for an organizational unit.

XXX is commonly used in an 11-character representation associated with the primary-office or default form of a BIC8. It should not be added, removed, or replaced merely to make a payment form accept the code. Use the exact identifier requested by the beneficiary institution and payment provider.

A branch identifier need not map to a public retail branch. It can identify a department, service, system, or other organizational unit belonging to the business party.

Worked Example: Reading a BIC

Consider the fictional BIC AAAAUS2LXXX:

Parsing the code does not reveal:

• the beneficiary’s name or account number;
• whether the beneficiary holds an account at the organization;
• the payment currency;
• the correspondent-bank route;
• the purpose or amount of the transfer;
• whether the BIC is connected to SWIFT; or
• whether the instructions are authentic.

The example is deliberately fictional and must not be used as a payment instruction.

Connected and Non-Connected BICs

SWIFT distinguishes two important statuses:

The BIC itself is an identifier; connectivity is an attribute in the associated reference data. Do not infer current connectivity from an old convention about a particular character position. Verify status through current institutional instructions or authoritative directory data.

SWIFT Code vs. Other Payment Identifiers

A payment form can require several of these fields. A correct BIC with an incorrect IBAN can still reject or misdirect a transfer. A valid IBAN checksum and valid BIC format also do not prove that the beneficiary name matches the destination account.

SWIFT Code vs. SWIFT Network

SWIFT provides secure standardized financial messaging. A BIC helps identify parties in messages and reference data.

SWIFT does not ordinarily hold a retail customer’s deposit or itself settle the underlying bank-to-bank payment. Banks, correspondent accounts, central-bank money, and payment or settlement systems perform the account and value-transfer functions applicable to the route.

This distinction matters when reviewing a status. A SWIFT message can be created, transmitted, acknowledged, rejected, investigated, or matched while the underlying payment has a separate debit, credit, settlement, hold, return, or compliance status.

How a BIC Can Appear in a Cross-Border Payment

Assume a company sends a fictional USD supplier payment from Bank A to a beneficiary at Bank D. Bank A and Bank D do not maintain the required direct correspondent relationship, so the route uses Bank B and Bank C.

The beneficiary bank’s BIC does not list every intermediary that the sending bank may use. Intermediary routing can depend on currency, correspondent relationships, account locations, service availability, sanctions screening, cutoffs, and bank procedures.

Fees can also be deducted or charged at different points under the instruction and account agreements. The BIC does not encode the fee arrangement or guarantee the amount ultimately credited.

How to Verify a SWIFT Code Safely

1. Obtain the BIC and account details from the beneficiary’s bank-issued instructions or another trusted source.
2. Compare the legal institution name, country, address, and branch or unit information with the expected payment relationship.
3. Confirm whether the payment provider needs BIC8, BIC11, an IBAN, a domestic routing code, or intermediary-bank information.
4. Validate the BIC against current bank records or authoritative BIC reference data; do not rely on format alone.
5. Independently verify new or changed instructions through a known contact channel, not a phone number or link supplied only in the change message.
6. Use dual approval and changed-instruction controls when the amount or risk warrants them.
7. Review the payment confirmation, message or trace reference, bank debit, intermediary status, and beneficiary credit separately.
8. Contact the sending institution immediately if fraud or misdirection is suspected; recovery may become harder as funds move onward.

An online “SWIFT code checker” may validate length or display copied directory data without proving that the source is current or trustworthy. Avoid disclosing customer account information to an unknown lookup site merely to check a public institution identifier.

Worked Example: A Valid BIC in Fraudulent Instructions

Assume a company normally pays Supplier S at Bank X. An email that appears to come from Supplier S says its bank has changed and provides:

• a correctly formatted BIC for a real Bank Y;
• a new beneficiary account;
• an urgent request to pay a large invoice today; and
• a new phone number for confirmation.

The BIC may pass format validation and genuinely identify Bank Y. That establishes nothing about whether Supplier S owns the new account or sent the email.

A safer process uses the supplier contact and telephone number already held in independently maintained records, confirms the requested change with an authorized person, documents the verification, and requires the normal payment approval. If verification fails, the payment should not be released solely because the BIC is valid.

The FBI’s Internet Crime Complaint Center identifies changed payment instructions as a common business-email-compromise pattern and recommends verification through a secondary channel or known contact information.

Common Errors and Risks

Wrong Identifier Type

Entering a BIC in an IBAN or account-number field can cause rejection or misrouting. Field labels should be read literally.

Wrong Organizational Unit

A BIC8 may be valid while a payment provider requires a specific BIC11, or the supplied BIC11 may identify an inappropriate department or service. Do not invent a suffix.

Stale Reference Data

Institutions merge, rename, reorganize, change connectivity, or stop using an identifier for a route. Old invoices and unofficial directories can remain online after instructions change.

Connectivity Assumption

A registered non-connected BIC can identify an organization without allowing direct SWIFT message exchange. Routing may require another connected party.

Authentication Failure

Syntax and directory matching do not authenticate the email, invoice, beneficiary account, or person requesting payment.

Payment-Status Confusion

A message acknowledgement is not the same as settlement or beneficiary-account credit. Review each status independently.

Data Exposure

Real bank-account and customer data should not be pasted into untrusted validation sites, chat tools, or public searches.

Review Checklist for a Payment Record

• Confirm the BIC exactly as sent, without spaces added to the stored value.
• Record whether it is BIC8 or BIC11 and what the branch identifier represents.
• Match the BIC to the legal institution, country, status, and expected role.
• Identify connected and non-connected parties in the route where relevant.
• Confirm beneficiary name, account number or IBAN, currency, amount, and reference separately.
• Verify intermediary-bank instructions when requested by the sending institution.
• Compare new instructions with prior approved details and investigate every change.
• Retain approval, verification, message, debit, fee, trace, and beneficiary-credit evidence.
• Do not infer final payment from a valid BIC or a sent-message status.

Authoritative Sources

• SWIFT: Business Identifier Code for BIC structure, uses, registration authority, and connectivity status
• ISO/TC 68: What Is BIC? for the ISO 9362 organization and branch structure
• ISO 9362:2022 for the current Business Identifier Code standard
• FBI IC3: Business Email Compromise for changed-account verification and payment-fraud precautions

Related Terms

• SWIFT: Financial messaging network and standards provider, distinct from the BIC itself.
• IBAN: Standardized account identifier used in participating countries and payment contexts.
• Routing Number: U.S. domestic identifier used in specified payment and banking processes.
• Wire Transfer: Bank-to-bank payment instruction that can require BIC and correspondent details for a cross-border route.
• Correspondent Banking: Account and service relationships that help banks route cross-border and multi-currency payments.
• Bank Account Number: Customer-account identifier that serves a different purpose from a BIC.

Check Your Understanding

FAQs

This article provides general payment and banking education. It does not authenticate payment instructions, determine legal payment status, or replace confirmation from the relevant financial institutions.