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.

How this becomes a moat

Teams can pin a registry version in CI, detect an official identifier transition, generate migration fixtures and keep the same target under watch. The value is repeatability and provenance—not a larger random IBAN counter.