Find failed transfers before your customers do.
It matches every transaction to the NIBSS settlement record and flags the ones that failed. It never holds or moves money.
What it does.
One record per transaction
An append-only record of every transaction and each change to it. A transfer is only marked settled when a settlement record confirms it. A success callback on its own isn’t enough.
Reconciliation
Matches your transaction records against the settlement record from the rail and decides: settled, wait, or mismatch. Mismatches become incidents.
Automatic detection
Stuck transfers, duplicate payouts, missing reversals and false successes are each detected within a set time. The detectors lean towards flagging anything that could affect money.
Side-by-side evidence
For any transaction, see your core banking record next to the settlement record, with the difference highlighted, so you can check the finding yourself.
Value at risk
The total value of stuck and failed transfers over any period, broken down to each transaction. This is money that would otherwise surface as complaints or write-offs.
Operations dashboard
Search by any reference, see a transaction’s full history, work the incident queue and watch live traffic. Every action is logged.
Check it yourself.
You don’t have to take our numbers on trust.
When Truss flags a false success, it shows your two systems disagreeing: core banking says SUCCESSFUL and the NIBSS settlement record says FAILED, side by side, with a link to the source file. The ‘value we’d have caught’ figure is just the sum of a list of transactions, each of which you can open and check against your own ledger or export to a spreadsheet.
Every figure traces back
Search by customer, account or reference. Open any transaction to see its history, both records and where the settlement data came from. Export it if you need to.
Choose how far it goes.
Start read-only to see what it finds in your real traffic. Later, let it send retry and reversal instructions for your bank to carry out. It stays non-custodial at every stage.
Read-only
Connect your traffic. Truss keeps the record, reconciles and reports what it would have caught. It changes nothing.
Daily use
Support, reconciliation and operations teams work from the dashboard each day.
Full detection
All detectors switched on, tuned to the patterns in your traffic.
Through your bank
Retry and reversal instructions that your bank carries out. Truss still never moves the money.
Tested against known failures
Each detector is tested with a simulator that injects known failures and checks that none are missed.
Want the technical detail?
We can take your architects through the data model, the settlement rule and how Truss connects to BankOne, Qore and NIBSS.
Request a demo