Create AccountHolderVerification request

post

https://www.bankingcircleconnect.com/api/v2/risk-check/accountholderverifications

You can request an Account Holder Verification (AHV) with this endpoint. This service allows you to verify whether the provided account holder name matches the associated account number and bank details. It helps prevent misdirected payments and reduces fraud.

📘
Read about migrating from the v1 to the v2 endpoint in the Account Holder Verification (v1) page.

Body Params

companyNumber

string

required

length between 1 and 9

The unique identifier for the client's company. This corresponds to the "ownedByCompanyNumber" field from the GET /accounts endpoint. Clients can use any company number they have access to from this response.

verificationName

string

required

length between 1 and 140

Contains the full name of the individual or business.

verificationType

string | null

enum

Contains the type of the entity to verify ("Personal" or "Business"). Required only for CoP UK lookups; ignored for CoP AU and VoP EU.

Allowed:

verificationAccount

object

required

The verification service (CoP UK / VoP EU / CoP AU) is automatically inferred from the request payload (account format + country + financialInstitution).

IBAN inputs are always processed as VoP, including GB IBANs.

See the Guide section: "How the verification type is determined from the payload".

userReference

string | null

Optional reference for tracking the request.

Responses

Language

Credentials

Bearer

Loading…

Response

Choose an example:

application/json

201Created

400Bad Request

401Unauthorized. The server understood the request, but access is not allowed, i.e. calling user does not have access.

404Not found. There is no resource behind the URL, i.e. requesting an entity that does not exist.

429Too Many Requests. The client has sent too many requests in a given amount of time. Only applicable for CoP AU requests.

500Internal Server Error. Something unexpected happened on BC Connect side.