How the Reliability Control Plane works.
A transfer counts as done when the rail settles it, not when an API says so. Everything in the Reliability Control Plane follows from that rule. This page shows the path each transaction takes and what happens when your bank’s record and the settlement record disagree.
A transaction moving through the engine.
An animated version of the real flow. Transactions arrive, are checked against settlement, and the ones that fail are pulled aside. Click any transaction to inspect it.
From intake to confirmed or flagged.
Taken in once
Truss reads your transaction records and the rail callbacks. Each carries a unique key, so a retry can’t become a second debit.
One record
Every transaction and every change to it is written to one append-only, timestamped store. You can replay the history but not rewrite it.
Match to settlement
Each record is compared with the NIBSS settlement record. A success callback is treated as a claim. Only settlement can mark a transfer settled.
Confirm or flag
If the records agree, it’s confirmed. If not, an incident is opened with a deadline.
Why ‘successful’ isn’t enough.
Normally your bank’s record and the settlement record agree. Truss is there for the times they don’t.
If core banking says SUCCESSFUL and the NIBSS settlement record says FAILED, that’s a false success: the customer thinks they’ve paid, but no money moved. Truss won’t mark it settled. It opens an incident, pushes it towards reversal, and shows you both records so you can check.
Settlement decides
A transaction only becomes settled when a settlement record confirms it. An API reply or callback that contradicts settlement is never treated as final.
Including ‘we don’t know yet’.
- Settled: both records agree and the money moved.
- Pending: too early to say. This is normal.
- False success: the bank says paid, settlement says failed. Flagged and never marked settled.
- Unreversed debit: the customer was charged, the beneficiary wasn’t credited and nothing was reversed.
- Duplicate: the same payment recorded twice.
- Reversed: it failed and the money was returned.
- Unknown: Truss can’t tell yet, so it asks a person to look rather than guess.
Three ways to connect.
Listed from lightest to most involved. None of them put Truss in the payment flow. Your bank remains the only party that moves money.
Rail callbacks
Add one webhook address to your bank’s existing NIP callbacks. Truss gets a copy of each callback you already receive. Your rail integration doesn’t change. This is the quickest start.
Settlement files
NIBSS settles in twelve sessions a day. Truss collects each session’s file by SFTP or upload, decrypts and parses it, and reconciles it against your ledger.
Core banking
For anything not seen in callbacks, Truss queries your core banking (BankOne or Qore) read-only on a schedule you set. An adapter maps vendor fields, so changing core banking means changing one file.
Optional: send instructions
If you switch it on, Truss sends retry and reversal instructions to your bank’s existing transfer API. Your bank carries them out. You control whether this is enabled.
It connects at your bank.
Money moves along the rail between licensed parties. Truss connects at one point, your bank. It reads each transaction and the settlement your bank receives, and flags what’s wrong. Explore the map below.
Send us a sample of your traffic.
We’ll reconcile it against your settlement file and show you what was stuck, falsely reported or duplicated, on a short call.
Request a demo