Settlement truth wins. Always.
A transaction is real when the rail settles it, not when an API says so. Truss makes that one rule non-negotiable and builds everything around it. Here’s the path every transaction takes, and what happens the moment the bank’s record and the settlement record disagree.
A transaction moving through the engine.
This is the real flow, animated: transactions stream in, get checked against settlement, and the ones that fail get diverted instead of silently passing. Click any transaction in the feed to inspect it.
From intake to confirmed, or flagged.
Take it in, exactly once
Truss ingests your transaction records and the rail callbacks. An idempotency key at the door means a retry can never become a second debit.
One book of record
Every transaction and every state change is written to a single canonical store, append-only and timestamped, a history you can replay, never rewrite.
Match against settlement
Each record is compared with the settlement truth from NIBSS. A success callback is treated as a claim; only the settlement record can mark a transaction settled.
Confirm or flag
Agree, and it’s confirmed. Disagree, and it’s flagged as an incident with a deadline, never quietly marked done.
Why a “success” is never enough.
In a healthy system the bank’s record and the settlement record agree. Truss exists for the moments they don’t.
When your core banking says SUCCESSFUL but the NIBSS settlement record says FAILED, that is a ghost success: the customer believes they were paid, but no money moved. Truss never lets that reach a settled state. It raises an incident, drives the transaction toward reversal, and shows you both records side by side so you can confirm it against your own systems.
Settlement-truth-wins
The transition to settled is gated on a settlement record, never on an API response or a callback. A success message that contradicts settlement can never be treated as done.
Including the honest one: “we don’t know yet.”
- Settled, both records agree. The money truly moved. Done.
- Pending / in flight, too early to judge. Normal, not alarming.
- Ghost success, the bank says paid, settlement says failed. The dangerous one. Flagged, never settled.
- Orphaned debit, charged, never credited, never reversed. Money left and went nowhere.
- Duplicate, the same payment counted twice.
- Reversed, it failed, and the money was correctly returned.
- Unknown, Truss genuinely can’t tell yet, so it flags it for a human instead of guessing.
One place to plug in: your bank.
Money moves along the rail between licensed parties. Truss plugs into one point, your bank, reads every transaction and the settlement it receives, and flags what’s broken. Explore the map below.
Bring us a window of your traffic.
We’ll reconcile it against your settlement file and show you exactly what was stuck, ghosted, or doubled, on a short call, no obligation.
Request a demo