IBAN-BIC.com (Theano GmbH) » Web Service » Documentation » Documentation: supported_countries
Example:
supported_countries("IBAN AND some_BICs AND (account_validated OR bankcode_validated)", "DE", "benutzername", "passwort") returns, in German ("DE"), a list of countries which are supported by the SOAP interface such that IBANs can be calculated, BICs (possible more than one BIC candidate) are returned for those bank codes for which a BIC is defined, and the domestic account number or the bank code are validated (or both).
Purpose: Informs which countries are currently supported by the SOAP interface, and what their names are in a given language. You may specify what conditions must be met for a country to be considered "supported".
Input Parameters:
If you leave the parameter "supported_condition" empty, the default condition "IBAN AND some_BICs AND (account_validated OR bankcode_validated)" is used.
Output Fields:
tns:CountryResStruct with the following fields:
Our CMS composes the following table by using several calls of the function "supported_countries". Therefore, we don't have to manually adjust the table; it always keeps up to date automatically whenever the SOAP interface starts supporting another country.
Country | domestic account number validation? | bank code validation? | BICs available? |
---|---|---|---|
no | yes | yes¹ | |
Albania | no | yes | yes¹ |
Andorra | no | yes | yes¹ |
Austria | yes | yes | yes¹ |
Belarus | no | yes | yes¹ |
Belgium | yes | yes | yes¹ |
Bosnia and Herzegovina | yes | yes | yes¹ |
Bulgaria | no | yes | yes¹ |
Croatia | yes | yes | yes¹ |
Cyprus | no | yes | yes¹ |
Czech Republic | yes | yes | yes¹ |
Denmark | no | yes | yes¹ |
Egypt | no | yes | yes¹ |
Estonia | yes | yes | yes¹ |
Finland | yes | yes | yes¹ |
France | yes | yes | yes¹ |
Georgia | no | yes | yes¹ |
Germany | yes | yes | yes¹ |
Hungary | yes | yes | yes¹ |
Iceland | no | yes | yes¹ |
Ireland | yes | yes | yes³ |
Israel | no | yes | yes¹ |
Italy | yes | yes | yes³ |
Jordan | no | yes | yes¹ |
Kazakhstan | no | yes | yes¹ |
Kosovo | yes | yes | yes¹ |
Latvia | no | yes | yes¹ |
Lebanon | no | yes | yes¹ |
Liechtenstein | yes | yes | yes¹ |
Lithuania | no | yes | yes¹ |
Luxembourg | no | yes | yes¹ |
Malta | no | yes | yes¹ |
Moldova | no | yes | yes¹ |
Monaco | yes | yes | yes¹ |
Netherlands | yes | no | yes |
Norway | yes | yes | yes¹ |
Poland | no | yes | yes² |
Portugal | yes | yes | yes³ |
Romania | no | yes | yes¹ |
San Marino | yes | yes | yes³ |
Serbia | yes | yes | yes¹ |
Slovakia | yes | yes | yes¹ |
Slovenia | yes | yes | yes¹ |
Spain | yes | yes | yes¹ |
Sweden | yes | yes | yes¹ |
Switzerland | yes | yes | yes¹ |
Turkey | no | yes | yes¹ |
United Arab Emirates | no | yes | yes¹ |
United Kingdom | yes | yes | yes¹ |
¹ These BICs are regularly copied from an official directory (usually from the national bank). If a BIC is defined for some bank code, we will return this one unique BIC.
² These BICs are also regularly copied from an official directory. However, there are bank codes for which more than one BIC is defined. In such a case, we return all possible BIC candidates, so you might have to figure out which one is the correct one.
³ These BICs are regularly updated by combining two official directories, one with BICs and bank names, and another one with bank names and bank codes. We join these directories based on the bank names. Some occasional errors might occur as a result due to naming inconsistencies. Also, the BICs are not always unique, and you might need to determine which one out of several candidates is correct.
Whenever we return several BIC candidates, we always first return short ones (with 8 instead of 11 significant digits). Usually these shorter BICs are good candidates.