Addressing via Account Details
Where proxies are not available, a payment can be addressed using either (a) International Bank Account Numbers (IBAN) or (b) local account numbers alongside a financial institution ID.
Addressing via IBAN
Nexus supports addressing by International Bank Account Numbers (IBAN) whenever the Destination Country accepts IBAN. IBAN is accepted in around 78 countries, but is not accepted in many major markets (such as Canada, Hong Kong, India, Singapore, and the USA).
IBANs are not accepted in India, Indonesia, Malaysia, the Philippines, Singapore and Thailand.
Addressing via Account Identification and Financial Institution Identification
Nexus also allows payments to be addressed using an Account Identification
(commonly called “account numbers”) and a Financial Institution Identification
(such as a Business Identifier Code, BIC or a non-BIC Clearing System Member Id
). Nexus is aware of the format of the Account Identification and Financial Institution Identification.
Identifying the Account
Account Identifications can vary significantly in format and length from country to country. In some countries, all Account Identifications have a fixed length, but in other countries the Account Identification can vary in length depending on the financial institution.
Identifying the Financial Institution
The ISO 20022 standard permits three types of Financial Institution Identification:
Business Identifier Code (BIC) (most commonly used)
Legal Entity Identifier (LEI)
A domestic Clearing System Member Identification.
In some countries, financial institutions may have both a BIC and a Clearing System Member Identification, although only one or the other needs to be used in a specific payment instruction.
LEI can be used in addition to BIC or Clearing System Member Identification to provide further information about the financial institution. This can be useful to support compliance checks and sanctions screening.
Warning: Locally-generated, non-registered BICs
Some IPSs issue non-bank PSPs with an identifier that follows the formatting of BIC but is not registered with Swift (the registration authority). This means that the locally-generated “pseudoBICs” are not included in the Swift database that some PSPs use to validate BICs before sending payments. Consequently, some PSPs may not be able to make payments to PSPs with non-registered pseudoBICs.
It is better to register these locally generated codes with Swift, so that they always validate correctly.
Last updated