We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Validate a SWIFT/BIC code and retrieve its bank, branch, country, city, and address.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
SWIFT/BIC Code Lookup provides a structured check of the bank, country, location, and optional branch segments of a SWIFT Business Identifier Code. Instead of reducing the answer to a vague pass or fail, it keeps the main signals available for review, export, and downstream data-quality work.
Single mode is intended for a focused check immediately before a signup, payment, contact, or data-entry decision.
The response can include validity, bank name, branch, country, city, address, and the parsed code segments. Read related fields together: the validity flag is useful for sorting, attribution fields support cross-checking, and a missing optional field means that the provider had no data rather than proving a risk.
CSV exports preserve the submitted value, processing state, and selected result columns. For payment, messaging, or customer-contact workflows, do not trigger an irreversible action from one Boolean field without an appropriate business rule and review path.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Provide an 8-character institution BIC or 11-character branch BIC; letters are normalized to uppercase. Remove names, notes, transaction amounts, internal identifiers, and any other fields that the check does not need. Sending only the minimum value reduces formatting mistakes and unnecessary exposure.
The browser performs a basic format check before submission, but passing it only means that the request can be made. If a value is rejected, check the country prefix, length, separators, capitalization, and invisible whitespace introduced by copying from a spreadsheet.
Use cases
See how the tool fits into real work and everyday tasks.
Common workflows include international payment review, supplier bank-data onboarding, finance migrations, and bulk beneficiary-bank cleanup. Checking records before they enter a system reduces rejects, entry mistakes, and later manual corrections. Periodic checks can also identify stale records that accumulated over time.
For an auditable process, retain the lookup time, original input, returned fields, and any later human decision. Treat the result as one decision signal, not a replacement for confirmation by a bank, carrier, mail operator, or site owner.
Q&A
Find concise answers to common questions and confusing cases.
eight characters identify an institution, while eleven can identify a branch; both lengths can be valid. A valid state covers the format and data signals available at lookup time; it does not replace a real payment, delivery, subscriber, or ownership confirmation.
No. Those states usually identify a network, quota, or upstream service failure. Keep the original input and retry later instead of classifying the record as invalid.
An empty optional field normally means that the service has no data for it. It is not evidence of either validity or risk on its own.
Notes
Review scope, result limitations, and important precautions before use.
a valid code does not guarantee that a particular currency or correspondent route is available; XXX often identifies the head office. Provider databases, live network conditions, and synchronization schedules can change an answer over time. Incomplete, borderline, or commercially important records should be routed to manual review.
Timeouts, HTTP 429 quota responses, and temporary upstream faults are service errors rather than proof that an input is invalid. In a batch export, use the error message to distinguish data that needs correction from a request that can be retried later.
BICs are generally public institution identifiers, but unrelated customer and transaction data should not be included. Protect downloaded batch files with appropriate access controls and retention periods, and delete them when the operational need ends. Do not publish results or use them for harassment, unsolicited outreach, or identity inference.
Related
Discover related tools, collections, and available API capabilities.