The account object used in fundsBeneficiary, fundsOriginator and other places provides several fields that are used to uniquely identify an account. Which fields are used, depends on the use case.
| Usecase | Field | Description | example |
|---|---|---|---|
| bank account | accountNumber |
Account numbers as used in most national or international schemes like IBAN, national routing number, or credit card. In case the provided value is detected to be a valid IBAN and no separate bankCountry is provided, the first 2 digits of the account number will be used as bankCountry. |
|
| bank country | bankCountry |
Alpha-2 country code of the account. |
|
| credit card | combination of
|
while applying many of the best practices, the gateway is not regulated due to PCI-DSS. Thus you must not transfers PANs. |
|
| Online wallets | accountEmailId |
Many schemes e.g. like PayPal use the user's email address as primary identifier for the account | harles.hollinten@mail.com |
| custom ids, token | accountId |
Any identifier that is used in your use case to uniquely identify an account can be provided in this field. Hashes or tokenized card numbers are a typical example as well | tqYV+tmG9aMh+l/K6cjJOwlka32LkaicU |
The above table provides typical usecases. However you can use the mentioned fields differently and in combination.
Technically, by default the combination of the fields bankCountry+accountNumber+accountEmailId+accountId+bankIdentifier+last4Digits+expiry is used to uniquely identify an account (unique within your tenant). If the accountNumber qualifies as an IBAN (which is defined to be unique) actually only the accountNumber is used as identificator.
The other fields from the account-Object (bankName, holder, productCode etc.) are not considered for a unique account identification.