Skip to main content
GET
BIC validation

Getting started

Base URL

Validation endpoint

The bic endpoint requires your API key and a BIC parameter to perform comprehensive validation of Business Identifier Codes.
This successful request validates a German BIC and returns detailed information:

Request parameters

String
required
Your unique API key. Note that each user has unique API keys for each of Cleariflow APIs, so your Bank Validation API key will not work for your Exchange Rates API, for example.
String
required
The Business Identifier Code to validate. Spaces are allowed and will be automatically removed during processing. The BIC should follow the ISO 9362 standard format.

Response parameters

The API response is returned in a universal and lightweight JSON format.
String
The normalized BIC without spaces, returned in uppercase format.
Boolean
Overall validation result indicating whether the BIC is valid according to all validation rules.
String
The two-letter ISO country code (e.g., DE for Germany, US for United States).
String
The full name of the country associated with the BIC.
String
The 4-character bank identifier code (e.g., DEUT for Deutsche Bank).
String
The name of the bank (currently shows “Bank information not available”).
String
The 2-character location code indicating the city or region (e.g., FF for Frankfurt).
String
The 3-character branch code (optional, may be empty for 8-character BICs).
Object
Additional detailed information about the BIC type and status.
String
The type of identifier (typically “BIC”).
Boolean
Whether the BIC is currently active and in use.
String
The type of financial institution (e.g., “Bank”, “Credit Union”).

Examples

Valid German BIC (8 characters)

Request:
Response:

Valid German BIC (11 characters with branch)

Request:
Response:

Valid US BIC

Request:
Response:

Valid UK BIC

Request:
Response:

Invalid BIC

Request:
Response:

Error handling

Missing BIC parameter

Request:
Response:

Missing API key

Request:
Response:

BIC Structure

The BIC consists of several components:
  1. Bank Code (4 characters): Unique identifier for the financial institution
  2. Country Code (2 characters): ISO 3166-1 alpha-2 country code
  3. Location Code (2 characters): City or region identifier
  4. Branch Code (3 characters): Optional branch identifier (XXX for main office)

Format examples

  • 8-character BIC: DEUTDEFF (Deutsche Bank, Germany, Frankfurt)
  • 11-character BIC: DEUTDEFF500 (Deutsche Bank, Germany, Frankfurt, Branch 500)

Common location codes

  • FF: Frankfurt, Germany
  • 33: New York, United States
  • 2L: London, United Kingdom
  • PP: Paris, France
  • MM: Milan, Italy

Validation Rules

The API performs comprehensive validation including:
  1. Length Validation: Checks if the BIC is 8 or 11 characters long
  2. Format Validation: Verifies the BIC follows the ISO 9362 standard
  3. Character Validation: Ensures only alphanumeric characters are used
  4. Country Code Validation: Validates the country code format
  5. Bank Code Validation: Checks the bank identifier format

BIC format requirements

  • Bank Code: 4 alphanumeric characters
  • Country Code: 2 alphabetic characters (ISO 3166-1)
  • Location Code: 2 alphanumeric characters
  • Branch Code: 3 alphanumeric characters (optional)

BIC vs SWIFT

BIC (Business Identifier Code) and SWIFT are often used interchangeably:
  • BIC: The official ISO 9362 standard name
  • SWIFT: The messaging network that popularized the code
  • SWIFT Code: Alternative name for BIC
All BICs can be used for SWIFT messaging, but not all SWIFT codes are valid BICs.

Supported Countries

The API supports BIC validation for 50+ countries including:
  • Europe: Germany, France, Italy, Spain, Netherlands, Belgium, Austria, Switzerland, UK, Poland
  • Americas: United States, Canada, Brazil, Mexico
  • Asia: Japan, Singapore, Hong Kong, Australia
  • Africa: South Africa, Egypt, Nigeria
For a complete list of supported countries, see the Supported Countries page.

Use Cases

BIC validation is essential for:
  1. International Wire Transfers: Ensuring accurate routing information
  2. SEPA Payments: European payment system requirements
  3. Banking Applications: Customer account validation
  4. Financial Compliance: Regulatory reporting requirements
  5. Payment Processing: E-commerce and fintech applications