Public Change Digest

Bank registry changes and source freshness.

The free digest makes registry freshness visible before you commit to a paid watchlist or API workflow. It reports the snapshot context we actually have and stays empty rather than inventing a change when no source diff is available.

Open the workflow Read API docs
Scope: Synthetic and sandbox-only. This page documents QA and integration workflows; it does not claim live account verification or production payment execution.

Use it in three steps

1. Inspect

Review the most recent supported change records and their source/effective context.

Explore inspect →

2. Watch

Save a matching source/key pair when a target needs recurring monitoring.

Explore watch →

3. Replay

Generate a deterministic migration fixture after a change is confirmed.

Explore replay →

Latest supported changes

Rows come from the published snapshot history. An empty table is valid: no supported change is reported rather than guessed.

Snapshot 2026-10-01T03:24:52.912893Z
DetectedSourceRecordChangeFields
2026-10-01T03:24:40.068901Z eba_psd2 FR_ACPR!755646 removed address, city, confidence, country_code, details, entity_type, name, postal_code, record_type, source_id, source_record_id, status
2026-10-01T03:24:40.068901Z fdic_locations 675081 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 61121 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 572289 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 563024 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 558805 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 508316 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 457839 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 430042 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 364061 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 282893 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id
2026-10-01T03:24:40.068901Z fdic_locations 2603 removed address, city, confidence, country_code, details, entity_type, name, parent_source_record_id, postal_code, record_type, region, source_id

Sources and freshness

Public registry source manifest

Open the documented source or runtime contract before relying on this workflow.

View source →Page evidence checked 2026-08-20

Questions teams ask

How often is the digest updated?

It reflects the latest successfully published registry snapshot. Each row carries its detected-at or snapshot context; cadence depends on the upstream source.

Why can the digest be empty?

An empty digest means no supported change rows are available in the current history window. IBANgen does not create synthetic change claims just to fill a page.

Can I receive an alert for a specific target?

Yes. Create an authenticated watchlist for the exact supported source and record key, then inspect changes and migration fixtures in the account workflow.

Availability and source coverage are bounded by the current registry, fixture catalog and plan entitlements. If a target is not matched, IBANgen reports that state instead of inventing authoritative coverage.