Does this reconstruct every historical state?

No. It reports the current record plus published snapshot diffs that IBANgen actually retains. Missing history stays explicitly unavailable.

What does upcoming mean?

It is a future valid-from or near-term valid-to date published by a supported source. It is not a prediction generated by IBANgen.

Can I automate a migration test?

Authenticated watchlists can inspect changes and create a deterministic synthetic before-and-after fixture for CI or a migration review.

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.

Inspect a target Read API docs

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

Erste Group Bank AG · active

{ "city": "Wien", "confidence": "authoritative", "country_code": "AT", "entity_type": "swiss_bank_master", "id": 641887, "identifiers": [ { "type": "bic", "value": "GIBAATWGXXX" }, { "type": "iid", "value": "89099" }, { "type": "sic_iid", "value": "890990" } ], "name": "Erste Group Bank AG", "postal_code": "1100", "record_type": "bank", "source_id": "six_bank_master", "source_record_id": "sic:890990:1139", "status": "active", "valid_from": "2026-08-31" }

Previous observed

1 diff

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

Upcoming

0 dates

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-08-30T03:40:35.026543Z

2026-08-30T03:40:09.192065Zadded

Detected 2026-08-30T03:40:24.424723Z · Changed: address, city, confidence, country_code, details, entity_type, name, postal_code, record_type, source_id, source_record_id, status, valid_from

Before

{}

After

{ "city": "Wien", "confidence": "authoritative", "country_code": "AT", "entity_type": "swiss_bank_master", "name": "Erste Group Bank AG", "postal_code": "1100", "record_type": "bank", "source_id": "six_bank_master", "source_record_id": "sic:890990:1139", "status": "active", "valid_from": "2026-08-31" }

Source-published upcoming dates

No upcoming effective date is published for this target.

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.

Watch this record Browse change digest