One job, done without compromise.
Know the true state of every transaction, and act on the ones that go wrong, without ever being the system that moves the money. That’s the whole product. Here’s what’s inside.
What it does.
Canonical record & state machine
A single, append-only source of truth for every transaction, with an explicit lifecycle. The move to settled is gated on a settlement record, not a callback, so a contradicting success can never be treated as done.
Reconciliation engine
Joins your transaction record against the settlement truth from the rail and decides: settle, wait, or mismatch. Contradictions become incidents instead of silent rows.
Automated detectors
Stuck and hung transfers, duplicate payouts, missing reversals, ghost successes, each pattern is detected on a deadline, with a bias toward never missing a money-affecting case.
Side-by-side proof
For any transaction, see your core-banking record beside the settlement record, with the disagreement highlighted, so you confirm a finding against your own systems, not our word.
Value-at-risk reporting
A clear figure for what you’d have caught over any window, the stuck and ghosted value that would otherwise have surfaced as tickets and write-offs, drillable down to each transaction.
Operate dashboard
Multi-key search, a full transaction timeline, the incident queue, and a live view. The daily workspace for support, reconciliation, and ops, with an audit trail on every action.
Confirm it yourself.
Truss never asks you to take a number on faith.
When Truss flags a ghost success, it doesn’t show an opinion, it shows your two systems disagreeing: your core banking saying SUCCESSFUL, the NIBSS settlement record saying FAILED, side by side, with provenance back to the exact source file. The headline “value we’d have caught” is simply the sum of a list of specific transactions, each one openable and checkable against your own ledger. And you can export the side-by-side data to analyse in your own spreadsheet.
Trace every claim
Search by customer, account, or reference. Open any transaction. See its full timeline, both records, and the settlement provenance. Export it. Nothing is a black box.
Run it at the depth you choose.
Run Truss at the depth you choose. Keep it read-only to prove value against your real traffic, or let it act, issuing retry and reversal instructions your bank executes. Every mode is non-custodial.
Read-only
Point Truss at your traffic. It holds canonical state, reconciles, and shows what it would have caught, touching nothing.
Daily workspace
Support, recon, and ops work the dashboard every day: search, timelines, incident queue.
Full automation
The complete detector suite plus rail and bank reliability intelligence, sharpened on your patterns.
Act via your bank
Durable retry and reversal instructions your bank executes. Truss still never moves the money itself.
Proven, not promised
Every detector is graded against a simulator that injects known failures and verifies none are missed. Correctness is the bar, not a coverage percentage.
Want the technical detail?
We’re happy to walk your architects through the data model, the settlement-truth-wins guarantee, and how Truss integrates with BankOne / Qore and NIBSS, in depth.
Request a demo