Payments Reconciliation & Anomaly Detection

An independent settlement feed runs alongside the observability platform's live transactions, and a batch engine matches the two every 30 seconds — the same shape as a real intraday reconciliation cycle, compressed so the breaks it catches are visible in a single sitting.

Reconnecting…
Match rate (latest run)
waiting for first run
Origination volume
matched, latest run
$ in open breaks
across last 0 run(s)
Overall match rate
last 0 run(s)

Breaks by type

Missing settlement0
Duplicate settlement0
Amount mismatch0
Orphaned settlement0

How this works

Every payments platform keeps at least two independent records of the same money movement: the system that originated it, and a downstream system that confirms it settled (core banking, a card network file, a correspondent bank). Those two records drift — a gateway times out after the money already moved, a settlement file gets a manual adjustment with no reference number, a batch runs twice. Reconciliation is the process that catches this before it becomes a customer-facing problem.

This module simulates that independent settlement feed and reconciles it against the observability platform's transaction ledger — reading the same database directly rather than over an API, since both are ultimately consumers of the same shared history.

Reconciliation breaks

Click a row for detail
DetectedTypeChannelOriginationSettlementDescription
No breaks yet — waiting for the first reconciliation run.