Bankers Almanac® Validate API Portal
© 2023 LexisNexis Risk Solutions Group

Validating the beneficiary bank details

Home Private: Validate API – Introduction Section 1 – Validation and Search Validating the beneficiary bank details
by

This call will validate the clients bank and account number, the one call will validate many formats including

  1. Bank codes (domestic clearing codes and BICs),
  2. Bank codes and account number,
  3. BBANs (such as CLABE) and
  4. IBANs

We always recommend back what you should be using including recommending any corrections or the format required change required for the payment.

The call is very flexible so you can take the data that your client has, we understand that using our AI and give you back what you need.

The service also give you prompts for additional data is available and in some cases required for the payment.

The service will also return the details for the Branch and Head Office of the bank (these may be the same branch) and also the branch that you require (see input options).  If you make no change from the default request then it will return the IBAN branch.

These include for each branch

  1. Name
  2. Address
  3. Domestic and International Codes
  4. SEPA Status
  5. Indicators of additional information that is available

METHOD

GET command, in “application/json” format

End Point

validate.bankersalmanac.com/validate-api/rest/convert/1.0.1

REQUEST

The request fields that are optional will affect the output values but not the output field, other than by using the parameter page.  If you enter the optional request field page and enter a number then your response will be paginated.  The default number of branches for a paginated response is 10 but this can be varied by entering the request field pageSize and giving it a value other than 10.

Calls that deliver additional details on the bank can be made using the branchToken (this defines the branch) and the freeToken (this means you will not be charged for these additional detail calls).  The additional detail that you can access are:

  1. Correspondent details- These will be required if you are making a non-domestic payment
  2. Additional requirements – This lists the payment purpose codes for the country
  3. Payment network membership – These are the details of the banks connection to payment networks for example CHAPS in the UK or FedWire in the US.
  4. Holidays – This gives you a list of working and non-working days.
  5. Contact details – If you wish to contact the bank or branch

RESPONSE

The request parameters can be downloaded here Response components table if you use the request field page then this will modify the output and the output fields can be found here.

If the user requests pagination which has been introduced in call 1.0.1 and call 1.0.2. The additional fields that are returned with the paginated response are:

  • page – indicates the current page number – default value is 1
  • pageSize – indicates how many branches are there per page – default value is 10
  • pageTotal – indicates the total number of pages the user can traverse per inquiry

TEST

Try testing using POSTMAN which is available as a Google Chrome App and can be found here POSTMAN REST Client you can create project which you can create using the WADL to create the project.  Just enter a valid authentication token into the request below and you’re working.

https://validate.bankersalmanac.com/validate-api/rest/convert/1.0.1?countryCode=GB&nationalId=309408&accountNumber=01638696&token=ENTERTOKEN&noBranch=N&errorComment=E

The test data entered into this sample is

Country Code: GB
National Code: 309408
Account Number: 01638696