Bank data Free+ Pro
Registry time machine
Use for Debugging old or changed bank codes
  1. 1Enter source_id and record key
  2. 2Inspect the timeline
  3. 3Watch the record
Registry Time Machine

See the identifier state across time.

Resolve one supported bank or identifier record, then compare the current record with published before-and-after diffs and any source-published effective dates. Missing history stays visible as unavailable.

Evidence boundary: this is registry and QA evidence, not live account verification, ownership proof or a prediction of future bank changes.

Inspect a source record

Use the stable source_id and record_key returned by Bank Intelligence. The lookup is bounded and read-only.

Current

Available

Deutsche Bank · active

{ "city": "Aachen", "confidence": "authoritative", "country_code": "DE", "entity_type": "domestic_bank_registry", "id": 24944, "identifiers": [ { "type": "bank_code", "value": "39070024" }, { "type": "bic", "value": "DEUTDEDB390" } ], "name": "Deutsche Bank", "postal_code": "52062", "record_type": "bank", "source_id": "deutsche_bundesbank_blz", "source_record_id": "bundesbank-de-39070024-050001", "status": "active", "updated_at": "2026-09-07", "valid_to": "2026-12-06" }
Previous observed

0 diffs

Published snapshot changes only. Each row carries its own snapshot ID and detected-at time.

Upcoming

1 date

Future-validity evidence from the source, not an IBANgen forecast.

Published diffs

Before and after values are shown only when the registry published them.

2026-10-15T03:35:33.978121Z
No published snapshot diff is available for this target in the current history window.

Source-published upcoming dates

Deutsche Bank
effective_to · 2026-12-06 · Deutsche Bundesbank bank sort code file

Turn evidence into a repeatable test

Save this exact source/key pair to a user-scoped watchlist. When a supported diff appears, IBANgen can create a deterministic synthetic before/after migration fixture.

Next in your workflow