> ## 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.

# Introduction

> Verify IBAN holder name in real-time with a simple REST API  and prevent payment errors and frauds. 

## 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:**

<Columns cols={2}>
  <Card title="Vendor IBAN verification" icon="shop">
    Verify supplier bank accounts before initiating payments and reduce the risk of fraud, misdirected transfers, or invoice manipulation.
  </Card>

  <Card title="Employee IBAN verification" icon="users">
    Validate employee IBANs during onboarding or payroll setup to prevent salary payment errors at scale.
  </Card>

  <Card title="Credit & lending workflows" icon="hand-holding-dollar">
    Confirm borrower IBAN ownership as part of KYC checks, loan origination, or repayment account validation.
  </Card>

  <Card title="Insurance claim verification" icon="shield-check">
    Verify beneficiary IBANs before indemnification to ensure funds are paid to the rightful account holder.
  </Card>

  <Card title="KYC & identity platforms" icon="id-card">
    Integrate IBAN holder verification as an additional signal within broader identity or document verification workflows.
  </Card>

  <Card title="Financial software & ERPs" icon="calculator">
    Embed IBAN verification into accounting, treasury, invoicing, or vendor management software to improve data quality and trust.
  </Card>
</Columns>

***

## How it works

A verification request follows the following lifecycle:

<Steps>
  <Step title="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.
  </Step>

  <Step title="Real-time bank query">
    Ibantrack queries the account-holding bank
  </Step>

  <Step title="Instant response">
    Receive `match`, `close_match`, or `no_match`
  </Step>
</Steps>

```mermaid theme={null}
sequenceDiagram
autonumber
participant App as Your Application
participant IT as Ibantrack API
participant Bank as Banking Network
App->>IT: POST /account-holder-verifications (IBAN + name)
activate IT
IT->>Bank: Request ownership confirmation
activate Bank
Bank-->>IT: Match result (Match/No Match/Close match)
deactivate Bank
IT-->>App: JSON Response (match_result)
deactivate IT
```

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.
* `account_not_verifiable`: Inconclusive. The bank was reached but the verification is not applicable for this account (e.g. savings accounts or closed accounts)

***

## 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](/api-reference/authentication/get-token).

***

## Sandbox environment

A sandbox environment is available to help you test your integration. See [Sandbox](/api-reference/sandbox/create-sandbox-verification).

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

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/documentation/getting-started/quickstart">
    Make your first verification in 5 minutes
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/verifications/create-verification">
    Explore endpoints and parameters
  </Card>

  <Card title="Sandbox Testing" icon="flask" href="/api-reference/sandbox/create-sandbox-verification">
    Test with predictable responses
  </Card>

  <Card title="Match Results" icon="circle-check" href="/documentation/core-concepts/match-results">
    Understand verification outcomes
  </Card>
</CardGroup>

***

<Tip>
  **Need help?** Our team responds to integration questions within 24 hours. Email [contact@ibantrack.com](mailto:contact@ibantrack.com)
</Tip>