A SWIFT code is an identifier used to name a bank or other organisation in financial messaging. The standards term is Business Identifier Code, shortened to BIC. In ordinary banking instructions, “SWIFT code” and “BIC” normally point to the same eight- or eleven-character value. The code helps a sending institution identify the intended organisation and, when supplied, a particular branch or business unit. It is not an account number and it does not identify the beneficiary by itself.
The distinction matters during an international transfer. A bank may need a BIC to address a message to another institution, while the beneficiary’s IBAN or domestic account number identifies the account. Treating the two as interchangeable can cause a form to reject the payment or, worse, encourage someone to place the correct-looking value in the wrong field. The safest approach is to read each label literally and use details supplied through a trusted channel.
The four parts of a BIC
A BIC contains eight mandatory characters and may add three branch characters. Read DEUTDEFF500 from left to right. DEUT is the four-letter bank or business code. DE is the two-letter ISO 3166-1 country code for Germany. FF is the two-character location code. 500 is the optional branch identifier. The first six positions are letters; the location and branch positions may also use digits.
The country segment describes where the BIC is registered, not the currency of the payment and not necessarily the physical location of every office serving the customer. The location segment is an identifier rather than a plain-language city abbreviation. It can also carry operational signals: a zero in its second position marks a test or non-production BIC, and a one marks a passive participant. Those flags are useful warnings, but they do not replace a current directory or direct confirmation.
Eight characters versus eleven
An eight-character BIC identifies the primary office. When an eleven-character form ends in XXX, it explicitly states the same primary-office convention. A different three-character ending names a branch or business unit. That means an eight-character value is not automatically incomplete. Some payment forms accept either form, while a bank’s instructions may require a specific branch suffix. Follow the instructions for the transaction instead of adding XXX merely to fill space.
Equally, do not delete a supplied branch code on the assumption that the shorter value is always preferable. The branch can matter to routing, reconciliation or the receiving institution’s internal process. If two trusted documents show different suffixes, ask the recipient or bank which value belongs to this payment rather than choosing based on appearance.
What a format checker can establish
A structural checker can confirm the length, character classes, assigned country code and visible flags. It can split the code so a human can inspect it. A curated directory may also associate a familiar BIC8 with an institution and city. Use the local SWIFT code checker for that job: the input is processed synchronously in your browser and is not submitted to this site.
However, a valid format does not prove that the organisation is currently reachable on a particular network, that the branch accepts the intended payment type, or that the code belongs to the beneficiary details you were given. It cannot confirm an account holder, detect a compromised invoice or guarantee settlement. Those questions require current information from the bank, payment provider or recipient. The SWIFT directory on this site is an editorial reference, not a live operational directory.
Where to find the correct code
Prefer the receiving bank’s official account instructions, a bank statement issued to the beneficiary, the authenticated online-banking details for the account, or direct confirmation from the bank. A supplier invoice can be convenient, but payment-detail changes sent by email are a common fraud pattern. When details change, verify them through a separate trusted channel—such as a known telephone number or authenticated banking message—rather than replying to the same message.
Search-engine snippets and generic code lists are useful for orientation, not final payment authority. Bank names merge, legal entities change and multiple institutions can share similar brands across countries. A real BIC can still be the wrong BIC for the account. Match the institution name, country, beneficiary account information and any branch instruction as a set.
A careful pre-transfer routine
- Copy the code from a trusted bank or beneficiary source; avoid retyping where possible.
- Remove only presentation spaces and compare every remaining character.
- Use the checker to confirm the eight- or eleven-character structure and country segment.
- Compare the institution and location with the rest of the payment instruction.
- Confirm any unexpected branch suffix, test flag or passive-participant flag with the bank.
- For a new or changed payee, verify the payment details through a second trusted channel.
That routine separates two different questions: “Is this shaped like a BIC?” and “Is this the right live routing detail for this payment?” The first can be answered locally and instantly. The second deserves independent confirmation before money moves. For the broader distinction between institution, account and domestic routing identifiers, continue with SWIFT vs IBAN vs IFSC.