Guide
BIC Format and Bank Directory Limits
Learn how 8 and 11 character BIC/SWIFT formats work, and why BankCodeKit does not confirm licensed directory status or Swift network connectivity.
Who needs to choose between format and directory checks
Users reviewing BIC/SWIFT fields on invoices, vendor records, payment forms, and developer test cases.
Choose the right type of BIC check
| Question | Format checker | Where to confirm |
|---|---|---|
| Is it 8 or 11 characters? | Yes | Visible text is sufficient |
| Are country and branch positions well formed? | Yes | Visible text is sufficient |
| Is the BIC active or assigned? | No | Licensed directory, bank or provider |
| Can it receive this transfer? | No | Sending bank or payment provider |
| Is the recipient safe? | No | Trusted recipient verification and fraud controls |
The visible BIC structure
A BIC is usually 8 or 11 characters. BankCodeKit can parse the visible structure into business party prefix, country code, location/business party suffix, and optional branch identifier.
- Business party prefix: 4 alphanumeric characters.
- Country code: 2 alphabetic characters.
- Location/business party suffix: 2 alphanumeric characters.
- Optional branch identifier: 3 alphanumeric characters.
What a format check can do
A format check can confirm length and allowed character placement. It can help spot obvious mistakes before a value is copied into another system.
Directory and connectivity limits
BankCodeKit does not use a licensed BIC directory and does not confirm whether a bank exists, whether a BIC has directory status or Swift network connectivity, or whether a payment can be routed through a specific network.
Format data and directory data answer different questions
A format checker answers whether the visible string has an accepted 8- or 11-character arrangement. A licensed or authoritative directory can answer different questions about a registered business party, code status, name, address, or connectivity attributes at a particular time. Those data sets are not interchangeable. BankCodeKit intentionally performs only the first task, so its result should never be presented as a directory match. This distinction matters when a code looks plausible but came from an unverified invoice or message.
- Format result: length and character positions are structurally consistent.
- Directory result: a separate source may associate the code with current reference data.
- Payment result: the bank or provider decides whether a route can be used.
Reviewing BIC8 and BIC11 without inventing a branch
Both BIC8 and BIC11 can satisfy the visible format rule. The final three characters of BIC11 are the optional branch identifier, and they must be preserved when they are supplied. Do not append XXX, delete a branch suffix, or substitute another location code merely to make a form accept the value. A provider may request a specific representation for its own workflow. If the instruction and form disagree, treat that as a reason to verify the source rather than as permission to construct a new code.
- Compare all characters with the original bank or recipient instruction.
- Keep the business party, country, location, and branch segments in order.
- Ask the provider which representation it accepts for the intended route.
A safer workflow before using a BIC
Run the format check as an early data-quality step, then return to the business context. Compare the beneficiary name and account details with the invoice or contract, check whether the BIC changed from a trusted prior record, and confirm unusual updates through an established channel. Use a bank or payment provider for current routing and directory questions. This workflow keeps a useful local format result in its proper place: it can reduce typing errors, but it cannot authorize a payment or replace current institutional reference data.
- Keep IBAN, BIC, beneficiary, amount, and reference in separate fields.
- Escalate unexpected changes instead of relying on visual plausibility.
- Do not interpret a green format result as a safe-transfer decision.
Avoid turning a format result into a directory claim
A plausible BIC can be invented by combining allowed characters in the right positions. That value may pass every local syntax rule without corresponding to an active institution or reachable branch. Keep screenshots, exports and user-facing labels explicit: the result is a visible structure check, while operational status belongs to a current directory or payment-provider workflow.
Practical BIC examples
The examples below show format patterns only. They are not proof of a live bank relationship or payment route.
- BIC8 pattern: DEUTDEFF
- BIC11 pattern: NWBKGB2LXXX
- Business party prefix example: first four alphanumeric characters.
- Branch identifier example: optional last three alphanumeric characters.
Where a BIC format check stops
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.
- It does not confirm licensed BIC directory status.
- It does not confirm Swift network connectivity.
- It does not confirm bank existence, reachability, or routing availability.
- It does not confirm sanctions status, fraud risk, payment readiness, or payment success.
FAQ
Can BankCodeKit tell if a BIC is in a licensed directory?
No. BankCodeKit checks format only and does not use licensed BIC directory data.
What does connected vs non-connected BIC mean here?
That context relates to directory and messaging status. BankCodeKit does not verify that status.
Can an 8 character BIC be valid format?
Yes. BIC format can be 8 characters, with an optional branch identifier making it 11 characters.
Should I verify a BIC before payment?
Yes. Verify real payment details with your bank, payment provider, invoice issuer, or recipient.
Sources for BIC Format and Bank Directory Limits
Public references for BIC Format and Bank Directory Limits are linked below; detailed standard scope, review methods, and licensing boundaries are documented on the Sources and Updates page.
Matching the cited format and reference data for BIC Format and Bank Directory Limits does not confirm account existence, ownership, bank reachability, or payment success. Read the detailed disclaimer.
Reference data reviewed: 2026-07-17 Next scheduled data review: 2026-10-17 Sources: Swift BIC / ISO 9362 information Reference data is reviewed periodically. BankCodeKit does not perform live bank, account, sanctions, or payment-network confirmation.