Skip to main content
POST
/
account-holder-verifications
Verify IBAN Holder
curl --request POST \
  --url https://api.ibantrack.com/api-v1/account-holder-verifications \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "account": {
    "iban": "FR7630004000031234567890143"
  },
  "account_holder": {
    "name": "Jean Dupont"
  }
}
'
{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "completed",
  "match_result": "match"
}

Documentation Index

Fetch the complete documentation index at: https://docs.ibantrack.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

This endpoint is the core of Ibantrack. It allows you to verify whether the provided name matches the holder of the specified IBAN, in real-time and across the SEPA zone. The verification is performed synchronously by querying the responding bank. Use the interactive API playground to test requests directly from this page: Authenticate using your API token, modify request parameters, and inspect real API responses

​
Request payload

​
Required fields

FieldTypeDescription
account.ibanstringIBAN of the account to be verified.
account_holder.namestringName of the account holder to be verified.
- For individuals: full legal name.
- For businesses: legal business name (company name).

​
Example requests

​
Individual — France

{
  "account": {
    "iban": "FR7630004000031234567890143"
  },
  "account_holder": {
    "name": "Jean Dupont"
  }
}

​
Business — Germany

{
  "account": {
    "iban": "DE80500105172521224695"
  },
  "account_holder": {
    "name": "Blue Horizon Travel GmbH"
  }
}
Timeout Notice: Responses typically take 1-3 seconds, but can take up to 10 seconds for some European banks. Set your client timeout accordingly.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
account
object
required
​
account_holder
object
required

Response

Verification completed

​
id
string<uuid>
read-only
Example:

"abc123ab-3171-4e97-92ec-a11e9fabc123"

​
status
enum<string>
read-only

The current lifecycle state of the verification request.

A completed status indicates that the financial institution has been successfully reached and processed the request.

A failedstatus indicates that the verification could not be completed due to technical or institutional constraints.

Additional details may be provided in the status_reason field.

Available options:
pending,
completed,
failed
​
match_result
enum<string>
read-only

The outcome of the account holder name verification against the financial institution’s records. Provided only when statusis completed.

Available options:
match,
close_match,
no_match,
account_not_verifiable
​
matched_name
string
read-only

Indicates the full name or company name as registered by the financial institution. Provided only if 'match_result' is 'close_match' and in accordance with data privacy regulations.

Example:

"JEAN DUPONT"

​
status_reason
string
read-only

Additional context on the request status. Primarily populated when status is 'failed' or when match_result is 'account_not_verifiable'

Example:

"institution_timeout"

​
enrichment
object
read-only