Part of the BIC Validation service. One request checks a BIC / SWIFT code against the official BIC directory licensed from S.W.I.F.T. SCRL and returns the institution behind it: name, branch, address, whether it is a financial institution, whether it is connected to the SWIFT network, and the network services and market infrastructures it takes part in. A second endpoint searches the same directory by institution name and country, for finding the BIC when you only have the bank’s name. Worldwide coverage.
Validate and look up a BIC:
https://api.iban.com/clients/api/swiftv2/bic/https://api.iban.com/clients/api/swiftv2/bic/?api_key=YOUR_API_KEY&format=json&bic=BARCGB22XXXSearch the directory by institution name:
https://api.iban.com/clients/api/swiftv2/bank/https://api.iban.com/clients/api/swiftv2/bank/?api_key=YOUR_API_KEY&format=json&country=US&bank_name=natwestapplication/x-www-form-urlencoded; GET takes the same parameters in the query string. Both methods return the same response. JSON bodies are not read.format is wrong. 429 when the rate limit is exceeded (HTML page), 500 with an empty body for a malformed parameter.Content-Type is application/json or application/xml. Directory text is upper case as registered with SWIFT.YOUR_API_KEY:curl "https://api.iban.com/clients/api/swiftv2/bic/" -d api_key=YOUR_API_KEY -d format=json -d bic=BARCGB22XXXThe full response to this request is in the Response section; the same request in six more languages is under Example request.
Both endpoints take the key and the format; each has its own input. Parameters the endpoint does not know are ignored.
| Parameter | Required | Value | Description |
|---|---|---|---|
api_key | yes | string | Your personal key, shown under API Access. Missing: HTTP 400 with a text body; wrong or empty: HTTP 403 with result code 301. |
format | yes | json or xml | Response format, lower case. Missing, empty or any other value (including JSON or XML in upper case) is refused with HTTP 400 and a text body (see Handling errors). |
| Parameter | Required | Value | Description |
|---|---|---|---|
bic | yes | string, 8 or 11 characters | The BIC to validate. Letters and digits only, in any case (lower case is converted and echoed in upper case). Spaces, hyphens and other characters are not removed: they give result code 801. Any length other than 8 or 11 gives 802. An 8-character BIC is looked up as its head-office record (branch code XXX) and directory_results.bic is returned in the 11-character form. Missing or empty: HTTP 400. When the parameter is sent twice, the last value is used. |
| Parameter | Required | Value | Description |
|---|---|---|---|
bank_name | yes | string, at least 3 characters | Part of the institution name, matched case-insensitively as a substring of the name in the directory (barclays finds BARCLAYS BANK PLC and its branches). Letters, digits and spaces are accepted; full stops, hyphens and apostrophes pass the check and are then matched literally (j.p. morgan finds J.P. Morgan records, wells-fargo finds nothing); accented and other non-ASCII letters give 806. The value is used exactly as sent: leading or trailing spaces and double spaces find nothing (808), so trim it. Fewer than 3 characters: 806. Missing: HTTP 400. |
country | yes | string, 2 letters | ISO 3166-1 alpha-2 code of the country of the institution, in any case. Anything other than two letters gives 807; two letters that are not a country (UK, XX) find nothing (808). Missing: HTTP 400. |
city | no | string | Narrows the search to records whose city contains the value (case-insensitive substring: lond matches LONDON). Echoed in query when sent. A city that matches nothing gives 808. Cannot be used without bank_name. |
limit | no | integer, 1 to 100 | Maximum number of records to return. Default 10, maximum 100 (larger values are capped). A value that is not a positive integer (0, -1, abc) is ignored and the default applies; 5.5 is read as 5. There is no paging: records beyond the first 100 cannot be retrieved, so narrow the search with city or a longer name when records_found is above 100. |
Every example validates the same BIC, BARCGB22XXX (Barclays Bank PLC, head office); its response is shown in the next section. Replace YOUR_API_KEY with the key from API Access.
curl "https://api.iban.com/clients/api/swiftv2/bic/" \
-d api_key=YOUR_API_KEY \
-d format=json \
-d bic=BARCGB22XXXThe bank endpoint takes the same form; the search in the Bank name search section:
curl "https://api.iban.com/clients/api/swiftv2/bank/" \
-d api_key=YOUR_API_KEY \
-d format=json \
-d country=US \
-d bank_name=natwestA BIC endpoint response has five members after query: bic_valid, bic_active, directory_results, services and error, in that order in both formats. The response to the example request:
{
"query": {
"bic": "BARCGB22XXX",
"success": true
},
"bic_valid": true,
"bic_active": true,
"directory_results": {
"bic": "BARCGB22XXX",
"bic8": "BARCGB22",
"bic_branch": "XXX",
"institution": "FINANCIAL",
"name": "BARCLAYS BANK PLC",
"branch_name": "ALL U.K. OFFICES",
"office": "HEAD OFFICE",
"address": "1 CHURCHILL PLACE",
"city": "LONDON",
"zip": "E14 5HP",
"country_name": "UNITED KINGDOM",
"iso_country_code": "GB"
},
"services": [
{
"code": "FIN",
"description": "MANY-TO-MANY FIN PAYMENT SERVICE"
},
{
"code": "SCO",
"description": "SCORE FIN"
}
],
"error": {}
}| Field | Type | Description |
|---|---|---|
query.bic | string | The BIC as received, converted to upper case. Empty in the response to an account error (301–305). |
query.success | boolean | true when the request was processed, including when the BIC failed validation (801–803); false only for account errors. |
bic_valid | boolean | true when the BIC has the right form and exists in the directory; false for 801, 802 and 803. |
bic_active | boolean | true when the directory marks the BIC as connected to the SWIFT network. false for a BIC that exists but is not connected: passive participants (8th character 1, such as UNCRITM1) and institutions that have been disconnected from the network. An active BIC can still have an empty services list. Also false whenever bic_valid is false. |
directory_results | object | The directory record, twelve fields (below). An empty object in JSON and an empty element in XML when the BIC was not found. |
services | array | The SWIFT network services and market infrastructures the BIC takes part in, each with code (3 characters) and description. Empty when the BIC has none or was not found. Codes are listed under Service codes. |
error | object | Empty ({} in JSON, empty code and message elements in XML) when the BIC was found. Otherwise code (a three-digit string, "803") and message. See Result codes. |
| Field | Description |
|---|---|
bic | The BIC of the record, always 11 characters (BARCGB22XXX for an 8-character request). |
bic8 | The first eight characters: institution, country and location codes. |
bic_branch | The branch code, three characters; XXX for the head office record. |
institution | FINANCIAL or NONFINANCIAL (a corporate with its own BIC, such as VODAGB2L). |
name | Name of the institution as registered with SWIFT, upper case. |
branch_name | Name of the branch or department; often empty, and HEAD OFFICE for some head-office branch codes. |
office | HEAD OFFICE or BRANCH, the office type of the record. A passive or disconnected BIC can be registered as BRANCH even with branch code XXX. |
address | Street address; empty when the directory has none. |
city | City; may be empty. |
zip | Postal code; may be empty. |
country_name | Country name, upper case. |
iso_country_code | ISO 3166-1 alpha-2 code, the same as characters 5–6 of the BIC. |
UniCredit’s passive BIC UNCRITM1 (8th character 1): it is in the directory, so bic_valid is true, but it is not connected to the network and has no services:
{
"query": {
"bic": "UNCRITM1",
"success": true
},
"bic_valid": true,
"bic_active": false,
"directory_results": {
"bic": "UNCRITM1XXX",
"bic8": "UNCRITM1",
"bic_branch": "XXX",
"institution": "FINANCIAL",
"name": "UNICREDIT S.P.A.",
"branch_name": "",
"office": "BRANCH",
"address": "",
"city": "",
"zip": "",
"country_name": "ITALY",
"iso_country_code": "IT"
},
"services": [],
"error": {}
}A corporate BIC, VODAGB2L:
{
"query": {
"bic": "VODAGB2L",
"success": true
},
"bic_valid": true,
"bic_active": true,
"directory_results": {
"bic": "VODAGB2LXXX",
"bic8": "VODAGB2L",
"bic_branch": "XXX",
"institution": "NONFINANCIAL",
"name": "VODAFONE GROUP SERVICES LTD",
"branch_name": "",
"office": "HEAD OFFICE",
"address": "VODAFONE HOUSE, THE CONNECTION",
"city": "NEWBURY",
"zip": "RG14 2FN",
"country_name": "UNITED KINGDOM",
"iso_country_code": "GB"
},
"services": [
{
"code": "FIN",
"description": "MANY-TO-MANY FIN PAYMENT SERVICE"
},
{
"code": "SCO",
"description": "SCORE FIN"
}
],
"error": {}
}An 11-character BIC with a branch code, CRESCHZZ80A. Institution names follow the directory: the former Credit Suisse BIC is now registered to UBS Switzerland AG, and BEARUS33 to J.P. Morgan Securities LLC, so do not assume a BIC’s owner from its letters:
{
"query": {
"bic": "CRESCHZZ80A",
"success": true
},
"bic_valid": true,
"bic_active": true,
"directory_results": {
"bic": "CRESCHZZ80A",
"bic8": "CRESCHZZ",
"bic_branch": "80A",
"institution": "FINANCIAL",
"name": "UBS SWITZERLAND AG (FORMERLY CREDIT SUISSE)",
"branch_name": "HEAD OFFICE",
"office": "BRANCH",
"address": "PARADEPLATZ",
"city": "ZUERICH",
"zip": "8001",
"country_name": "SWITZERLAND",
"iso_country_code": "CH"
},
"services": [
{
"code": "EB+",
"description": "EBA CLEARING - EURO1/STEP1 REACHABLE INSTITUTIONS"
},
{
"code": "FIN",
"description": "MANY-TO-MANY FIN PAYMENT SERVICE"
},
{
"code": "TG+",
"description": "TARGET2 INDIRECT PARTICIPANTS AND ADDRESSABLE BICS"
}
],
"error": {}
}Result code 803; directory_results and services are empty. 801 and 802 have the same shape with their own code and message:
{
"query": {
"bic": "ZZZZZZ99XXX",
"success": true
},
"bic_valid": false,
"bic_active": false,
"directory_results": {},
"services": [],
"error": {
"code": "803",
"message": "BIC Code not found in directory."
}
}HTTP 403, result code 301 shown; 302 to 305 have the same shape with the messages from the code table. query.bic is empty and query.success is false:
{
"query": {
"bic": "",
"success": false
},
"bic_valid": false,
"bic_active": false,
"directory_results": {},
"services": [],
"error": {
"code": "301",
"message": "API Key is invalid"
}
}The bank endpoint finds every record whose institution name contains bank_name in the given country, optionally narrowed by city, and returns up to limit of them (default 10, maximum 100). Each record carries the twelve directory fields, its own bic_active flag and its own services. The search for natwest in the United States, four records:
{
"query": {
"country": "US",
"bank_name": "natwest",
"success": true
},
"records_found": 4,
"records_displayed": 10,
"directory_results": [
{
"bic": "RBOSUS3GXXX",
"bic8": "RBOSUS3G",
"bic_branch": "XXX",
"institution": "FINANCIAL",
"name": "NATWEST MARKETS SECURITIES INC.",
"branch_name": "",
"bic_active": true,
"office": "BRANCH",
"address": "600 WASHINGTON BLVD",
"city": "STAMFORD,CT",
"zip": "06901",
"country_name": "UNITED STATES OF AMERICA",
"iso_country_code": "US",
"services": [
{
"code": "FIN",
"description": "MANY-TO-MANY FIN PAYMENT SERVICE"
}
]
},
{
"bic": "GRNWUS33FUT",
"bic8": "GRNWUS33",
"bic_branch": "FUT",
"institution": "FINANCIAL",
"name": "NATWEST MARKETS SECURITIES INC.",
"branch_name": "FUTURES",
"bic_active": true,
"office": "BRANCH",
"address": "600 WASHINGTON BLVD",
"city": "STAMFORD,CT",
"zip": "06901",
"country_name": "UNITED STATES OF AMERICA",
"iso_country_code": "US",
"services": [
{
"code": "FIN",
"description": "MANY-TO-MANY FIN PAYMENT SERVICE"
}
]
},
{
"bic": "GRNWUS3EXXX",
"bic8": "GRNWUS3E",
"bic_branch": "XXX",
"institution": "FINANCIAL",
"name": "NATWEST MARKETS SECURITIES INC.",
"branch_name": "",
"bic_active": true,
"office": "BRANCH",
"address": "600 WASHINGTON BLVD",
"city": "STAMFORD,CT",
"zip": "06901",
"country_name": "UNITED STATES OF AMERICA",
"iso_country_code": "US",
"services": [
{
"code": "FIN",
"description": "MANY-TO-MANY FIN PAYMENT SERVICE"
}
]
},
{
"bic": "GRNWUS33XXX",
"bic8": "GRNWUS33",
"bic_branch": "XXX",
"institution": "FINANCIAL",
"name": "NATWEST MARKETS SECURITIES INC.",
"branch_name": "",
"bic_active": true,
"office": "HEAD OFFICE",
"address": "600 WASHINGTON BLVD",
"city": "STAMFORD,CT",
"zip": "06901",
"country_name": "UNITED STATES OF AMERICA",
"iso_country_code": "US",
"services": [
{
"code": "FIN",
"description": "MANY-TO-MANY FIN PAYMENT SERVICE"
}
]
}
],
"error": {}
}| Field | Type | Description |
|---|---|---|
query | object | country and bank_name as received (case is kept; a country value longer than two characters is cut to two; an apostrophe is echoed with a backslash before it), success, and city when it was sent. success is false for 806, 807, 808 and the account errors. |
records_found | integer | Number of records that match the search, before limit is applied; with city it counts the filtered records. 0 with result code 808. |
records_displayed | integer | The limit in effect (the limit sent, capped at 100, or 10), not the number of records returned: a search with four matches and the default limit reports 10. Count directory_results instead. 0 on an error. |
directory_results | array | The matching records, each with the twelve directory fields above plus bic_active and its own services array. Empty on an error. In XML each record is a record element; there bic_active is the numeric flag 1 for connected, the services element of a record is empty even when JSON lists services, and the response carries top-level bic_valid, bic_active and services elements that have no meaning for a search. Use JSON when you need the services of a record. |
error | object | As on the BIC endpoint: empty on success, code and message otherwise. |
Result code 808, query.success false. 806 and 807 have the same shape:
{
"query": {
"country": "US",
"bank_name": "zzzzqqqqxx",
"success": false
},
"records_found": 0,
"records_displayed": 0,
"directory_results": [],
"error": {
"code": "808",
"message": "No records found in directory."
}
}Records are returned in the directory’s own order, which is not alphabetical; sort them yourself. A search without country or without bank_name is refused with HTTP 400, and bic is not accepted on this endpoint: validate a BIC you found with the BIC endpoint.
A result code is a three-digit string in error.code. 8xx codes come with HTTP 200 and describe the input; 3xx codes come with HTTP 403 and describe the account.
| Code | Message | Meaning |
|---|---|---|
| 801 | Invalid characters in BIC. | A character other than a letter or digit, including a space or hyphen. |
| 802 | Incorrect BIC Length. Accepted BIC length 8 or 11 characters | The value has a length other than 8 or 11. |
| 803 | BIC Code not found in directory. | Well-formed, but not in the current directory: never issued, deleted, or a test BIC (8th character 0). |
| Code | Message | Meaning |
|---|---|---|
| 806 | Bank Name Invalid! Bank search should be minimum of 3 characters. Allowed characters a-z, A-Z, 0-9, space! | bank_name is shorter than three characters or contains characters outside the allowed set (accented letters, for instance). |
| 807 | Country code incorrect! Allowed is 2 letter country code. Example: UK, DE, FR | country is not exactly two letters. |
| 808 | No records found in directory. | Nothing matches the name, country and city sent. |
HTTP 403, both endpoints. No lookup is performed.
| Code | Message | What to do |
|---|---|---|
| 301 | API Key is invalid | Copy the key exactly as shown under API Access; an empty key gives the same answer. |
| 302 | Subscription expired | Renew the BIC Validation service under My Services. |
| 303 | No queries available | BIC Validation plans have no query limit, so this code is not expected; contact support if you see it. |
| 304 | You have no access to this API | The BIC Validation service is not active on this account. |
| 305 | IP Address not allowed | The key is restricted to certain IP addresses; add the calling server's address under Settings. |
HTTP 400 with a plain-text body (text/html), both endpoints. There is no result code; match on the status.
| Body | Cause |
|---|---|
Bad Request: Missing 'api_key' or 'format' parameter values | api_key or format is missing. Also the answer to a JSON body, which is not read. |
Bad Request: Invalid 'format' parameter value | format is empty or not exactly json or xml. |
Bad Request | bic missing or empty (BIC endpoint); bank_name or country missing (bank endpoint). |
What each outcome means for your code. Lookups are deterministic for a given input; the directory itself changes with each SWIFTRef release, so if you cache responses, give the cache a limited lifetime.
| Situation | Meaning | What to do |
|---|---|---|
| HTTP 400, text body | A required parameter is missing or format is wrong. The body is plain text, not JSON or XML. | Fix the request. Do not retry it unchanged. |
| HTTP 403, result code 301 or 304 | The key is wrong, or the BIC Validation service is not on the account. The body has the normal structure with the error object filled and query emptied. | Stop sending; every request will fail the same way. Check the key under API Access, or contact support for 304. |
| HTTP 403, result code 302 or 303 | The BIC Validation service has expired (302); 303 is not expected on an unlimited plan. | Stop sending and alert whoever handles the subscription; renew under My Services, or contact support for 303. |
| HTTP 403, result code 305 | The calling address is not on the key’s IP allow-list. | Add the address under Settings, then resend. |
| HTTP 429, HTML body | More than 20 requests per second. The request was rejected by the web server before reaching the API and was not processed. | Wait a moment and resend; lower the sending rate. Safe to retry. There is no Retry-After header. |
| HTTP 500, empty body | A parameter was sent in a form the API cannot read, such as bic[]. | Send plain string parameters. |
| HTTP 5xx, timeout, connection error | Temporary problem on the way to the API or on the API itself. | Retry with increasing delays (1 s, 2 s, 4 s, then give up and queue). A request that got no response may still have been processed. |
| HTTP 200, result code 801–803 or 806–808 | The request was fine; the BIC or the search terms are not. | Do not retry: the same input gives the same result. Show the user the message, log the code. |
bic_valid and bic_active are both true. bic_valid alone means the code exists in the directory; a valid but inactive BIC (passive participant, disconnected institution) cannot receive SWIFT messages.error.code, not on HTTP status or on the presence of directory_results.institution when the payee should be a bank: NONFINANCIAL records are corporates with their own BIC.TGT, TG+, EBA, EB+ or ERP tells you how the institution is reached in TARGET2 or EURO1/STEP1; STG is CHAPS in the UK. The lists are per BIC and can be empty for an active institution.hsbc finds 27 records in HK) rather than the full brand, and trim the input.directory_results; do not rely on records_displayed.Every entry in a services array carries its description, so you do not need this table to display a result. It lists the codes the directory can return: SWIFT network services and the EU-wide infrastructures first, then national market infrastructures by country.
| Code | Service | Country |
|---|---|---|
ABE | EBA CLEARING - EURO1/STEP1 (EBA) | network / EU |
EB+ | EBA CLEARING - EURO1/STEP1 REACHABLE INSTITUTIONS | network / EU |
EBA | EBA CLEARING - EURO1 | network / EU |
ERP | EBA CLEARING - STEP1 | network / EU |
FIN | MANY-TO-MANY FIN PAYMENT SERVICE | network / EU |
MAC | Financial institution restricted to a Member-Administered Closed User Group (MA-CUG) | network / EU |
SCO | SCORE FIN | network / EU |
TG+ | TARGET2 INDIRECT PARTICIPANTS and addressable BICs | network / EU |
TGT | TARGET2 DIRECT PARTICIPANTS | network / EU |
RPD | RAPID-FINCOPY RPD (LIVE) | AE United Arab Emirates |
AIP | ALBANIAN INTERBANK PAYMENT SYSTEM | AL Albania |
PTR | SISTEMA DE LIQUIDACO POR BRUTO | AO Angola |
CCE | CCP.CEE | AT Austria |
CSA | BULK PAYMENTS BYCLEARING SERVICE AUSTRIA | AT Austria |
OEK | OEK CSD | AT Austria |
ACL | AUSTRACLEAR CLOSED USER GROUP | AU Australia |
PDS | PAYMENT DELIVERY SYSTEM/RITS-RTGS | AU Australia |
AZM | AZIPS - AZERBAIJAN INTERBANK PAYMENT SYSTEM | AZ Azerbaijan |
BAP | BOSNIA I HERCEGOVINA RTGS | BA Bosnia And Herzegovina |
BDS | CBRTGS - CENTRAL REAL TIME GROSS SETTLEMENT SYSTEM | BB Barbados |
BHR | BAHRAIN RTGS | BH Bahrain |
CBS | BAHRAIN SSS (SECURITIES SETTLEMENT SYSTEM) | BH Bahrain |
BPS | BURUNDI RTGS SYSTEM FOR EAPS | BI Burundi |
BHS | BAHAMAS RTGS | BS Bahamas |
BIS | BOTSWANA INTERBANK SETTLEMENT SYSTEM | BW Botswana |
CAD | LVTS - LARGE VALUE TRANSFER SYSTEM | CA Canada |
CDS | MT566 - CORPORATE ACTION CONFIRMATION DELIVERY SERVICE | CA Canada |
BCG | CSD SERVICE OF DRC | CD Congo, The Democratic Republic Of The |
CBC | RTGS OF CENTRAL BANK OF CONGO | CD Congo, The Democratic Republic Of The |
PCH | SWISS INTERBANK CLEARING (SIC) | CH Switzerland |
UTP | UBS THIRD PARTY FIN MT971 | CH Switzerland |
SCP | SISTEMA CHILENO DE PAGOS INTERBANCARIOS | CL Chile |
SYG | SYGMA | CM Cameroon |
CCC | COMPENSACION DE DIVISAS DE COLOMBIA | CO Colombia |
UNI | CSD PRAGUE FIN-CUG | CZ Czechia |
EP+ | EPM-ECB | DE Germany |
DD+ | KRONOS - DANISH KRONE RTGS | DK Denmark |
DDK | KRONOS - DANISH KRONE RTGS | DK Denmark |
DKD | DANMARKS NATIONAL BANK | DK Denmark |
VPD | VP SECURITIES A/S CUG | DK Denmark |
SDD | SIPARD LBTR | DO Dominican Republic |
ALG | BANK OF ALGERIA - GROSS PAYMENT SYSTEM | DZ Algeria |
MCS | MCDR_FIN_CUG | EG Egypt |
PEG | PAYMENT SYSTEM IN EGYPT | EG Egypt |
CAM | SPI | ES Spain |
RTC | REGIS-TR CORPORATE STATUS | ES Spain |
FBN | RTGS FIJI | FJ Fiji |
AIM | BLOOMBERG ASSET AND INVESTMENT MANAGER | GB United Kingdom |
BFI | BLACKROCK | GB United Kingdom |
BMF | BLOOMBERG MONEY MARKET FUNDS | GB United Kingdom |
CCS | BROADRIDGE MATCHING | GB United Kingdom |
FXG | BLOOMBERG FX SETTLEMENT SERVICE | GB United Kingdom |
GSS | SWIFTNET BULK PAYMENTS BY VOCALINK | GB United Kingdom |
GST | GSTP GLOBAL STRAIGHT THROUGH PROCESSING | GB United Kingdom |
SSE | BLOOMBERG SELL SIDE EXECUTION AND ORDER MANAGEMENT SOLUTIONS | GB United Kingdom |
STG | CHAPS STERLING (RTGS) | GB United Kingdom |
STP | BLOOMBERG STRAIGHT THROUGH PROCESSING | GB United Kingdom |
TLF | LCH - TRADE LEG FEED | GB United Kingdom |
TOM | BLOOMBERG SELL SIDE TRADE ORDER MANAGEMENT SOLUTIONS | GB United Kingdom |
TRM | BLOOMBERG CORPORATE TREASURY MANAGEMENT | GB United Kingdom |
GIS | GHANA INTERBANK SETTLEMENT SYSTEM (GISS) | GH Ghana |
CBG | GAMBIA RTGS | GM Gambia |
GNR | REPUBLIQUE DE GUINEE RTGS SERVICE | GN Guinea |
HKL | HONG KONG RTGS SERVICE | HK Hong Kong |
SPH | LBTR HONDURAS - FIN COPY (LIVE) | HN Honduras |
HRK | HSVP - HRVATSKI SUSTAV VELIKIH PLACANJA | HR Croatia |
HUF | VIBER - VALOS IDEJU BRUTTO ELSZAMOLASI RENDSZER | HU Hungary |
KLR | CLOSED USER GROUP FOR HUNGARIAN SECURITIES MARKET | HU Hungary |
CBI | IRIS | IE Ireland |
BIR | ISRAELI RTGS | IL Israel |
TAC | ISRAEL: TAC - TACH CUG (LIVE) | IL Israel |
XBC | XBOMINBB_CUG | IN India |
ISG | ICELAND RTGS SERVICE | IS Iceland |
JOD | RTGS-JO | JO Jordan |
JOE | JORDAN CROSS BORDER REPORTING | JO Jordan |
JOF | JORDAN CROSS BORDER REPORTING | JO Jordan |
KPS | KENYA ELECTRONIC PAYMENT SETTLEMENT SYSTEM (KEPSS) | KE Kenya |
CBE | EASTERN CARIBBEAN PAYMENTS SYSTEM | KN Saint Kitts And Nevis |
LKB | LANKASETTLE | LK Sri Lanka |
LRR | LIBERIA RTGS SERVICE | LR Liberia |
LSW | LESOTHO WIRE | LS Lesotho |
LA+ | LATVIA'S ACCESS TO TARGET | LV Latvia |
LVL | STARPBANKU AUTOMATIZETA MAKSAJUMU SISTEMA | LV Latvia |
MUP | MACSS - MAURITIUS AUTOMATED CLEARING AND SETTLEMENT SYSTEM | MU Mauritius |
RBM | MALAWI: RTGS SERVICE - MITASS | MW Malawi |
RTS | MALAYSIA: BANK NEGARA MALAYSIA - RENTAS | MY Malaysia |
NAM | NAMIBIAN INTERBANK SETTLEMENT SYSTEM (NISS) | NA Namibia |
INC | INTERPAY CUG | NL The Netherlands |
MCF | MCF - EMCF CUG | NL The Netherlands |
NBO | NORGES BANK RTGS SERVICE | NO Norway |
NOC | NICS - NORWEGIAN INTERBANK CLEARING SYSTEM | NO Norway |
OSC | OSC EQUITY CLEARING | NO Norway |
AVP | AVP - ASSURED VALUE PAYMENTS | NZ New Zealand |
AVT | RESERVE BANK OF NEW ZEALAND - AVT | NZ New Zealand |
NSI | NZClear Interface | NZ New Zealand |
BSP | PPS - PHILIPPINES PAYMENT SYSTEM | PH Philippines |
KDP | POLAND: KDPW_FIN_CSD | PL Poland |
PLN | POLAND: SORBNET2 - POLAND RTGS | PL Poland |
PMA | PMA RTGS | PS Palestine, State Of |
PPY | SISTEMA DE PAGOS DEL PARAGUAY | PY Paraguay |
DEC | CSDA_FIN_CUG | RO Romania |
ROB | ROMANIAN GSRS (NEW) | RO Romania |
ROL | REPORT - ROMANIAN ELECTRONIC PAYMENT OPERATIONS IN REAL-TIME | RO Romania |
RON | NEW REGIS SERVICE - RON | RO Romania |
ROS | ROMANIAN GSRS | RO Romania |
RWS | RWANDAN RTGS SYSTEM FOR EAPS | RW Rwanda |
SAR | SARIE - SAUDI ARABIAN RIYAL INTERBANK EXPRESS | SA Saudi Arabia |
BCC | BGC CLEARING CUG | SE Sweden |
SE+ | RIX | SE Sweden |
SEC | RX | SE Sweden |
SSK | RIX - REAL-TIME GROSS SETTLEMENT IN SEK | SE Sweden |
MEP | MEPS+ : SINGAPORE RTGS SYSTEM | SG Singapore |
MEQ | TEST SINGAPORE RTGS SYSTEM | SG Singapore |
MEU | TEST SERVICE FOR MEPS (INTERNAL TESTING) | SG Singapore |
SLF | SIERRA LEONE RTGS SERVICE | SL Sierra Leone |
SLR | SIERRA LEONE RTGS SERVICE SLISS | SL Sierra Leone |
BCA | STAR - UEMO A MI-CUG | SN Senegal |
IPS | SWAZILAND INTERBANK PAYMENTS AND SETTLEMENTS SYSTEM | SZ Swaziland |
ERS | ECOBANK RAPID TRADE (USD) | TG Togo |
ERU | ECOBANK RAPID TRADE (EUR) | TG Togo |
THB | BAHTBNET/2 - THAILAND PAYMENT SYSTEM | TH Thailand |
DVP | TAKASBANK DVP SETTLEMENT SYSTEM | TR Turkey |
TTD | SAFE-TT | TT Trinidad And Tobago |
TWI | TAIWAN FOREIGN CURRENCY DIRECT DEBIT SERVICE | TW Taiwan |
TWP | FOREIGN CURRENCY RTGS SERVICE | TW Taiwan |
TIS | TANZANIA INTERBANK SETTLEMENT SYSTEM (TISS) | TZ Tanzania, United Republic Of |
UIS | UGANDA NATIONAL INTER-BANK SETTLEMENT (UNIS) SYSTEM | UG Uganda |
BTC | FUNDPLICITY SERVICE | US United States Of America |
CLN | CLN - CLSNET FINCOPY SIT/PERF | US United States Of America |
COT | LOAN/SERV CLEAR FIN | US United States Of America |
FAC | FedACH | US United States Of America |
FWR | FedWIRE | US United States Of America |
OMG | Omgeo (INTELLIGENT TRADE MANAGEMENT SOLUTIONS) | US United States Of America |
PEF | PERES OPERATIONS (LIVE) | US United States Of America |
CUY | FIN COPY FOR THE CENTRAL BANK OF URUGUAY | UY Uruguay |
PVE | PVE - PAYMENTS SYSTEM VENEZUELA | VE Venezuela (Bolivarian Republic Of) |
YVE | LBTR VENEZUELA | VE Venezuela (Bolivarian Republic Of) |
MOS | SAMOS - SOUTH AFRICAN MULTIPLE OPTION SETTLEMENT | ZA South Africa |
RCH | BANKSERVAFRICA RCH | ZA South Africa |
SRS | SIRESS FIN COPY SERVICE | ZA South Africa |
ZAS | STRATE - SHARE TRANSACTIONS TOTALLY ELECTRONIC | ZA South Africa |
ZCL | SOUTH AFRICA FX FIN COPY | ZA South Africa |
ZDS | SOUTH AFRICA DS FIN COPY | ZA South Africa |
ZVA | SOUTH AFRICAN VALUE ADDED PAYMENTS SYSTEM | ZA South Africa |
ZIS | ZAMBIA INTERBANK PAYMENT & SETTLEMENT SYSTEM (ZIPSS) | ZM Zambia |
CCH | COMESA REPSS PAYMENT SYSTEM | ZW Zimbabwe |
ZET | ZETSS - ZIMBABWE ELECTRONIC TRANSFER AND SETTLEMENT SYSTEM | ZW Zimbabwe |
| Term | Meaning |
|---|---|
| BIC | Business Identifier Code (ISO 9362), also called SWIFT code: 4-letter institution code, 2-letter country code, 2-character location code, and an optional 3-character branch code. 8 characters identify the institution, 11 a specific branch. |
| Head office / XXX | The 8-character BIC is the institution itself; in the directory it is stored as the 11-character form with branch code XXX. The API returns that record for an 8-character request. |
| Location code | Characters 7–8. An 8th character of 0 marks a test BIC (not in the directory, result 803); 1 marks a passive participant, an institution that is in the directory but not connected to the network (bic_active false). |
| Connected | The directory flag behind bic_active: the institution can send and receive messages on the SWIFT network. A BIC can be valid and registered without being connected. |
| Non-financial institution | A corporate or other organisation with its own BIC for treasury traffic; institution is NONFINANCIAL. |
| Service code | Three-character code of a SWIFT network service (FIN) or a market infrastructure the BIC participates in (TGT for TARGET2, STG for CHAPS), from the directory. |
| SWIFTRef | The reference-data products of S.W.I.F.T. SCRL. The BIC directory behind this API is licensed from SWIFTRef and refreshed regularly; BIC data is used with the permission of S.W.I.F.T. SCRL, database rights reserved. |