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

# Enrichment

> Understanding IBAN enrichment data and its availability

In addition to account holder verification, Ibantrack may provide **optional enrichment data** derived from the submitted IBAN.

Enrichment is **non-blocking** and **independent** from the verification result.\
Its availability depends on the IBAN country and the enrichment type.

***

## What is enrichment?

Enrichment consists of **non-sensitive metadata** inferred from the IBAN structure, such as:

* BIC code
* Bank name

This data helps you:

* display contextual information to users,
* improve internal reconciliation,
* enrich audit logs and reporting.

Enrichment **never affects** the verification outcome.

***

## Availability

Enrichment is currently available **only for French IBANs (FR)**.

For IBANs outside France:

* the `enrichment` object may be absent, or
* enrichment fields may be returned with a `not_applicable` status.

This behavior is expected and should be handled gracefully.

***

## Enrichment object structure

When available, enrichment is returned under the `enrichment` object:

```json theme={null}
{
  "enrichment": {
    "status": "completed",
    "bic_code": {
      "value": "BNPAFRPPXXX",
      "status": "completed"
    },
    "bank_name": {
      "value": "BNP PARIBAS",
      "status": "completed"
    }
  }
}
```

***

## Enrichment fields

### BIC code

The `bic_code` field contains the BIC (Business Identifier Code) associated with the provided IBAN.

* Derived from authoritative IBAN routing data
* Provided only when available and applicable

| Field    | Description                               |
| :------- | :---------------------------------------- |
| `value`  | The BIC code derived from the IBAN        |
| `status` | The availability status of the enrichment |

***

### Bank name

The `bank_name` field contains the name of the financial institution associated with the IBAN.

* Intended for informational and display purposes
* Not guaranteed to reflect branding or commercial naming

| Field    | Description                               |
| :------- | :---------------------------------------- |
| `value`  | The financial institution name            |
| `status` | The availability status of the enrichment |

***

## Enrichment status values

Each enrichment field includes a `status` attribute describing its availability.

| Status           | Meaning                                                 |
| :--------------- | :------------------------------------------------------ |
| `pending`        | Enrichment processing is ongoing                        |
| `completed`      | Enrichment data successfully retrieved                  |
| `unavailable`    | Enrichment is supported but data could not be retrieved |
| `not_applicable` | Enrichment is not supported for this IBAN               |

***

## Relationship with verification results

Enrichment data is **independent** from the account holder verification result.

For example:

* a verification may result in `match`, `no_match`, or `account_not_verifiable`,
* while enrichment data may still be `completed`, `unavailable`, or omitted.

Clients **should not** infer verification outcomes from enrichment data.

***

## Best practices

* Treat enrichment as **supplementary information**
* Do not rely on enrichment availability for business-critical logic
* Always base verification decisions on:
  * `status`
  * `match_result`
  * `status_reason`

***

## Future extensions

Additional enrichment attributes and country coverage may be introduced over time.

Any changes will be documented and versioned to ensure backward compatibility.