Skip to main content

​
Bank Account Holder Verification API

Ibantrack provides a simple REST API to verify that an IBAN belongs to the expected account holder accross the SEPA zone, for both individual and business accounts. The Ibantrack API is organized around REST, has predictable resource-oriented URLs, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. All requests are performed synchronously.

​
Usage scenarios

Ibantrack API is designed to fit seamlessly in various workflows and usage scenarios to help prevent payment errors and frauds. How teams use Ibantrack in production:

Supplier IBAN verification

Verify supplier bank accounts before initiating payments and reduce the risk of fraud, misdirected transfers, or invoice manipulation.

Employee IBAN verification

Validate employee IBANs during onboarding or payroll setup to prevent salary payment errors at scale.

Credit & lending workflows

Confirm borrower IBAN ownership as part of KYC checks, loan origination, or repayment account validation.

Insurance claim verification

Verify beneficiary IBANs before indemnification to ensure funds are paid to the rightful account holder.

KYC & identity platforms

Integrate IBAN holder verification as an additional signal within broader identity or document verification workflows.

Financial software & ERPs

Embed IBAN verification into accounting, treasury, invoicing, or vendor management software to improve data quality and trust.

​
How it works

A verification request follows the following lifecycle:
1

Submit IBAN and name

Send account number and expected holder name: full name for an individual account or a legal name for a business account.
2

Real-time bank query

Ibantrack queries the account-holding bank
3

Instant response

Receive match, close_match, or no_match
Each verification returns a unique identifier that can be stored for audit, reconciliation, and compliance purposes.

​
Match results

A verification can return one of the following outcomes:
  • match: The provided name matches the account holder name registered by the bank.
  • close_match: Minor discrepancies with the name registered by the bank. (e.g. spelling, maiden name). The bank’s registered name is provided to help you manually or programmatically reconcile the record.
  • no_match: The provided name does not match the account holder name registered by the bank.
  • unable_to_match: Inconclusive. The bank was reached but cannot perform the verification for this account

​
Authentication

The Ibantrack API uses OAuth 2.0 Client Credentials authentication. Before calling any API endpoint, you must obtain an access token and include it in the Authorization header of your requests. See Authentication.

​
Sandbox environment

A sandbox environment is available to help you test your integration. See Sandbox. Sandbox endpoints behave like production endpoints but allow you to force specific verification outcomes for testing purposes. The same authentication endpoint is used for both production and sandbox environments.

​
Next Steps

Quickstart

Make your first verification in 5 minutes

API Reference

Explore endpoints and parameters

Sandbox Testing

Test with predictable responses

Match Results

Understand verification outcomes
Need help? Our team responds to integration questions within 24 hours. Email [email protected]