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
- display contextual information to users,
- improve internal reconciliation,
- enrich audit logs and reporting.
Availability
Enrichment is currently available only for French IBANs (FR). For IBANs outside France:- the
enrichmentobject may be absent, or - enrichment fields may be returned with a
not_applicablestatus.
Enrichment object structure
When available, enrichment is returned under theenrichment object:
Enrichment fields
BIC code
Thebic_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
Thebank_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 astatus 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, orunable_to_verify, - while enrichment data may still be
completed,unavailable, or omitted.
Best practices
- Treat enrichment as supplementary information
- Do not rely on enrichment availability for business-critical logic
- Always base verification decisions on:
statusmatch_resultstatus_reason

