A static bank lookup answers one question. A watchlist answers what changed, when it became effective and how to replay the affected payment workflow. IBANgen keeps this layer synthetic, source-aware and fail-closed.
Save a source/key pair from a bank or BIC page and review changes in your account.
Explore watch a target →See the source, record key, snapshot and changed fields before acting on a diff.
Explore review evidence →Download a stable synthetic fixture so routing and payment-form tests can reproduce the transition.
Explore replay migration →Open the documented source or runtime contract before relying on this workflow.
View source →Page evidence checked 2026-08-20The current worker queues pending verification alerts only. Outbound delivery remains disabled until a deployment explicitly configures and verifies a sender.
Supported registry fields can include names, identifiers, statuses, relationships, payment-rail flags and source metadata. Each diff reports the exact fields available in the snapshot.
No. Watchlist limits are plan-scoped so the service can keep storage and alert processing bounded.