Bank data API

Resolve bank identifiers with source evidence.

Search BIC and domestic bank identifiers, inspect canonical institution records, and receive source, freshness and match context for payment QA, routing normalization and bank-data workflows.

Search bank coverage Read bank API docs One-time access

Quickstart

Resolve a BIC

curl -X POST https://ibangen.com/api/v1/bank-intelligence/lookup \
  -H 'X-API-Key: YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"type":"bic","value":"COBADEFFXXX"}'

Response shape

Inspect the contract before integration

{
  "success": true,
  "results": [{
    "query": {"type": "bic", "value": "COBADEFFXXX"},
    "matches": [{"name": "Commerzbank AG", "country_code": "DE"}]
  }],
  "registry_generated_at": "2026-08-27T00:00:00Z"
}

Coverage boundary

What this workflow proves — and what it does not

Coverage differs by country, identifier type and source licensing; the API never promises every bank worldwide.
A BIC or registry match does not prove that a specific customer account exists or is reachable.
Source freshness is reported per published registry snapshot and should be evaluated for the intended workflow.

Registry source catalogue Machine-readable sources Coverage report JSON OpenAPI JSON

Canonical identity

Aliases and identifiers resolve to a canonical institution record instead of leaving each integration to normalize names alone.

Source provenance

Responses preserve registry source and freshness context so teams can audit where a bank fact came from.

Fail-closed matching

Unsupported or conflicting targets return no match instead of presenting an inferred institution as authoritative.

Workflows

Common QA workflows

BIC and bank-code lookup Start with a focused example, then reuse the same workflow for your own test data. Payment routing normalization Start with a focused example, then reuse the same workflow for your own test data. Registry change QA Start with a focused example, then reuse the same workflow for your own test data. Payment form QA dataset 100 repeatable rows with a stable seed and export-ready schema.

Questions teams ask

Before you choose a workflow

Which identifiers can the bank data API resolve?

It resolves BIC and supported domestic identifiers from the currently published source catalog. Available types vary by country and source.

What happens when an identifier is ambiguous or missing?

The API returns an explicit no-match or bounded candidate response. It does not silently guess a bank identity.

Can I audit where a bank record came from?

Yes. Bank intelligence responses and linked registry pages expose source and freshness context for supported records.