NEWWatch an agent's payment get refused, and read the reason, in the live browser demo.Open the demo
AxorumAxorum

Cross-rail reconciliation

Category

Cross-rail reconciliation is the work of producing one authoritative set of books when value moves over several payment rails at once — cards, ACH, stablecoin transfers, and machine payment protocols. Each rail reports only its own share, so no rail's report shows the total position with any counterparty.

How it works

Every rail keeps a partial record. A card processor knows card transactions; a bank knows ACH; a settlement network knows on-chain transfers. None of them knows what the others carried. The participant is the only party positioned to hold the complete record, and reconciling it means normalizing several formats, timings, and identifiers onto one counterparty and one set of accounts.

Example

In March, Northwind pays one vendor $3,200 by machine payment protocol, $450 by corporate card, and $1,100 by ACH — $4,750 in total. The card statement shows $450. The bank shows $1,100. The settlement record shows $3,200. If Northwind's exposure limit for that vendor is $4,000, no single report reveals the breach.

Common questions

Why not reconcile in the general ledger?

You can, but usually only after the period closes, which makes it detective. Enforcing a cumulative limit requires the position to be current at transaction time.

Does adding rails make this worse?

Yes, and the pattern is familiar. Merchants who added payment providers for resilience and coverage found transaction visibility degraded as integrations multiplied. Agent payments repeat the pattern with more rails and faster settlement.

By Tim Fisher, Co-founder, Axorum · Updated