Bank data Free+ Pro Guide JSON
Registry intelligence
Use for Bank data, history and change alerts
API
Registry Intelligence

Bank registry intelligence for BIC and payment QA.

IBANgen combines bank and identifier records with field-level provenance, snapshot context and deterministic QA workflows. Use the free preview to understand coverage, then connect lookup, changes and fixtures through the API.

Scope: Synthetic and sandbox-only. This page documents QA and integration workflows; it does not claim live account verification or production payment execution.

Use it in three steps

1. Resolve

Search a BIC, LEI, domestic identifier or institution name and see the canonical match context.

Explore resolve →

2. Compare

Inspect current-versus-previous registry changes and keep a watchlist for qualified targets.

Explore compare →

3. Replay

Generate a synthetic before/after migration fixture with a stable seed and artifact hash.

Explore replay →

How the coverage counts relate

These counters describe separate evidence layers. They are not additive, and none of them represents live account ownership or payment availability.

20K+

generator metadata rows

Merged country/bank inputs used by the generator; a row is not a separate legal entity.

10K+

unique generator bank names

Normalized display-name variants available to bank-targeting controls.

8.8K+

generator BIC samples

Distinct BIC/SWIFT samples associated with generator metadata, subject to source freshness.

684K+

public registry graph records

Separate multi-source records for identifiers, institutions, places, rails and relationships.

119

IBAN format rules

Country-level format and checksum contracts; not a count of banks or live accounts.

Interpretation: The generator layer and the public registry graph are related but not interchangeable. A registry record can provide provenance or relationship context without being a generatable bank row, and a generator row never proves account ownership or payment availability.

Sources and freshness

Public data source/licence manifest

Open the documented source or runtime contract before relying on this workflow.

View source →Page evidence checked 2026-08-20

Questions teams ask

Does Registry Intelligence verify live bank accounts?

No. It resolves public registry and identifier evidence for QA, routing and data-integration workflows; it does not verify account ownership or payment availability.

Can I monitor a bank or BIC for changes?

Authenticated users can create scoped watchlists and inspect field-level changes when a supported registry snapshot changes.

Can I use the results in production payments?

Use the data as an integration and QA input. Confirm source rights, freshness and operational controls before using any identifier in a live payment decision.

Next in your workflow