IBAN Name Check API Use Cases
The use cases section of the IBAN-Name Check API for Organisations provides practical examples of how the API can be used to perform different types of requests and retrieve corresponding responses. The examples are categorised based on schemes. Schemes support checks in certain regions and or countries in the world.
IBAN-Name Check for Natural persons
IBAN-Name Check is a process used to verify that the account holder name and IBAN (International Bank Account Number) provided by a customer or supplier match the information registered with the bank. The IBAN is a unique identifier for bank accounts that is used internationally to facilitate transactions.
IBAN-Name Check for Organisations
IBAN-Name Check is a process used to verify that the account holder name and IBAN (International Bank Account Number) provided by a customer or supplier match the information registered with the bank. The IBAN is a unique identifier for bank accounts that is used internationally to facilitate transactions.
The IBAN-Name Check for Organisations and Natural persons are comparable, they differ on the following points:
- An organisation can only have one account holder.
- For organisations we always give a name suggestion, also in case of a know no match;
- For organisations we give the city name back;
- Note that they can also be matched on trading names see section Company (KvK) ID check.
Other NL scenarios
In the examples you can find other scenarios which might occur in the Netherlands. For instance, when an account is inactive, not found or matched on data which is not from the CRM system of a bank.
Request
{
"accountId": {
"value": "NL72SRPY0000000001",
"type": "IBAN"
},
"name": "David Alex Miller"
}
Response
{
"nameMatchResult": "MATCH",
"dataUsedForMatching": "VERIFIED",
"account": {
"accountNumberValidation": "VALID",
"paymentPreValidation": "PASS",
"status": "ACTIVE",
"accountType": "NP",
"jointAccount": false,
"numberOfAccountHolders": 1,
"countryCode": "NL"
},
"scheme": "SurePay"
}
Company (KvK) ID check
For checks on organisation accounts in addition to the IBAN-Name Check functionality, Dutch banks also provide SurePay with a KvK-number and KvK-branch number.
- This enables API users to validate whether the submitted/provided KvK number is matching the account holder's KvK number as registered by the bank.
- Furthermore, a connection with the KVK API improves our algorithm capabilities by allowing matches on the trading names retrieved from an account holding organisation.
- This means that in addition to checking the account holder name and IBAN, the SurePay Account Check service can also check for matches based on the company's trading name. This can further reduce data entry mistakes and fraud in payments.
In the 'KVK only check'
and 'KVK & Branch check'
example, you'll see that the field 'name'
does not need to be inputted in the request to proceed with the check.
VAT check
The VAT check
functionality is another feature of the IBAN-Name Check API for Organisations v2 API. The functionality allows organisations to perform a VAT (Value Added Tax)
check on their customers and suppliers.
How does it help in real use cases?
The VAT check
verifies the validity of the VAT number
provided by the customer or supplier. Ensuring that:
- The number is registered with the appropriate tax authority.
- The name registered (linked) to the
VAT number
matches any of the legal and commercial name at the bank.
The VAT check
functionality can be integrated into any system that supports APIs.
Request
{
"accountId": {
"value": "NL34SRPY0000000006",
"type": "IBAN"
},
"companyIds": [
{
"companyIdType": "NL_KVK",
"companyIdValue": "54892382"
}
]
}
Response
{
"nameMatchResult": "COULD_NOT_MATCH",
"dataUsedForMatching": "VERIFIED",
"companyIds": [
{
"type": "NL_KVK",
"matchResult": "MATCH"
}
],
"account": {
"accountNumberValidation": "VALID",
"paymentPreValidation": "PASS",
"optedOut": false,
"status": "ACTIVE",
"accountType": "ORG"
},
"scheme": "SurePay"
}
Account Type check (NP/ORG)
The ‘Account Type' feature allows users to input the account type of the payee in the request (in the field ‘accountType’).
This can be either 'Natural Person' (NP)
or 'Organization' (ORG)
. By providing this information in the request, the SurePay IBAN-Name Check API for Organisations service can perform an additional check on the account type stored by the bank and return a result based on the match between the user's input and the account type stored in the bank/ organisation. When the user inputs the account type in the request, the SurePay Account Check service will return a field in the response called 'accountTypeMatchResult'
.
How does it help in real use cases?
By receiving the ‘accountTypeMatchResult’
in the response, users can further verify the identity of the payee and reduce the risk of fraud and mistakes in payments. This feature is particularly useful for organisations that need to verify the identity of their suppliers and ensure that they are working with legitimate businesses.
Request
{
"accountId": {
"value": "NL72SRPY0000000001",
"type": "IBAN"
},
"name": "David Alex Miller",
"accountType": "ORG"
}
Response
{
"nameMatchResult": "MATCH",
"dataUsedForMatching": "VERIFIED",
"account": {
"accountNumberValidation": "VALID",
"paymentPreValidation": "PASS",
"status": "ACTIVE",
"accountTypeMatchResult": "NO_MATCH",
"jointAccount": false,
"numberOfAccountHolders": 1,
"countryCode": "NL"
},
"scheme": "SurePay"
}