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

Absa Bank Zambia PLC · ACTIVE

{ "city": "Lusaka", "confidence": "authoritative", "country_code": "ZM", "entity_type": "GENERAL", "id": 1681, "identifiers": [ { "type": "bic", "value": "BARCZMLXXXX" }, { "type": "business_register_id", "value": "119710006444" }, { "type": "lei", "value": "213800O9L2G7HXZTRN43" } ], "name": "Absa Bank Zambia PLC", "postal_code": "72053", "record_type": "legal_entity", "source_id": "gleif_lei", "source_record_id": "213800O9L2G7HXZTRN43", "status": "ACTIVE", "updated_at": "2026-01-13T16:01:46.851Z", "valid_from": "1971-09-07T00:00:00.000Z" }
Previous observed

0 diffs

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
No published snapshot diff is available for this target in the current history window.

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.