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.
Search a BIC, LEI, domestic identifier or institution name and see the canonical match context.
Explore resolve →Inspect current-versus-previous registry changes and keep a watchlist for qualified targets.
Explore compare →Generate a synthetic before/after migration fixture with a stable seed and artifact hash.
Explore replay →These counters describe separate evidence layers. They are not additive, and none of them represents live account ownership or payment availability.
Merged country/bank inputs used by the generator; a row is not a separate legal entity.
Normalized display-name variants available to bank-targeting controls.
Distinct BIC/SWIFT samples associated with generator metadata, subject to source freshness.
Separate multi-source records for identifiers, institutions, places, rails and relationships.
Country-level format and checksum contracts; not a count of banks or live accounts.
Open the documented source or runtime contract before relying on this workflow.
View source →Page evidence checked 2026-08-20No. It resolves public registry and identifier evidence for QA, routing and data-integration workflows; it does not verify account ownership or payment availability.
Authenticated users can create scoped watchlists and inspect field-level changes when a supported registry snapshot changes.
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.