Skip to main content
POST
NUBAN Advanced
The NUBAN Advanced endpoint provides a more comprehensive view of a bank account compared to the standard NUBAN check. In addition to resolving the account name, it compares the account against a customer_name you provide and returns a name-match confidence score — useful for confirming that a bank account genuinely belongs to the person or business claiming it.

Endpoint

Request

Headers

Body Parameters

Example

Response

200 OK

The name match ignores letter case and extra spaces, so Stephen Badmus matches STEPHEN BADMUS. Decide on comparism_data.status; keep confidence for your own records.

Reading the name match

Base your decision on status, not on your own confidence cut-off: the provider sets the verdict. For example, a check returned false at 65% and true at 97%. In the dashboard this shows as Name match: Match (100%) or Name match: Not a match (37%). When the name doesn’t match, the call still succeeds and returns the account details, with status: false:
Use the exact bank code. A code for a different bank returns “Record not found”. For example, Sterling Bank is 232 and Sterling Mobile is 23201.

400 Bad Request

401 Unauthorized

Authorizations

x-access-token
string
header
required

Your Adhere API secret key

Body

application/json
account_number
string
required
Example:

"0123456789"

bank_code
string
required
Example:

"044"

customer_name
string
required

The name to check against the registered account holder's name

Example:

"STEPHEN BADMUS"

Response

Account resolved, with the name-match result