BIC Validation
Purpose
BIC Validation endpoint allows the consumers to validate that the BIC value available with them is a valid BIC or not.
Configuration
BIC validation can be performed using dynamic configurations populated using both legacy SWIFTRef portfolio and with evolved SWIFTRef portfolio. Client implementations who wish to switch from legacy portfolio to the evolved portfolio can do so using the configuration ipf.csm-reachability.swift-ref-version. Refer the configuration on application.conf
| Configuration Value | Portfolio | Dynamic Configuration Used | Industry Files USed |
|---|---|---|---|
legacyPortfolio |
SWIFTRef legacy portfolio |
Bic Dir 2018 |
BIC Directory 2018 |
evolvedPortfolio |
SWIFTRef evolved portfolio |
Party Entity Directory |
SWIFTRef Identifiers All |
Dynamic Configurations Used
BIC validation uses the industry data dynamic configurations to carry out BIC validation. The dynamic configurations are required to be populated through ingestion of relevant industry files provided
| Industry Data | Used with SWIFTRef portfolio | Purpose | Additional References |
|---|---|---|---|
BicDir2018 |
SWIFTRef legacy portfolio |
The dynamic configuration is used for BIC validation functionality provided by IPF. |
|
Party Entity Directory |
SWIFTRef evolved portfolio |
The dynamic configuration holds the party entity data along with the BICs that are used for BIC validation. |
SWIFTRef Identifiers All |
Usage
-
Client implementations can call the endpoint /bicvalidation to validate if the BIC they have is a valid and active BIC.
-
The BIC validation is done against industry reference date (BicDir2018 or Identifiers All, depending on the configuration value.)
Request and Response
BIC Validation follows below request and response structure. This section provides information on the request and response properties, for detailed API specs, please refer CSM Reachability Service API
Notes
-
The endpoint can accept 8 or 11 character BICs. When a 8 character BIC has been provided, the BIC must match with first 8 characters of a head office BIC on party entity directory to be deemed a valid BIC. If the party entity directory does not contain a head office record, the BIC8 on input won’t be deemed valid even if the first 8 characters match with a branch BIC.