Truss is made by Islands Digital.
Truss grew out of consulting work on why transfers on Nigerian rails report success and then don’t settle. We saw the cost land on operations teams, and built the tools we wanted them to have.
Payments are fast. Confirmation is slow.
Money moves in seconds, but settlement arrives hours later in batches. In between, a transfer can look complete when it isn’t, and the customer often notices first.
We didn’t want to add another system in the middle of the money. Truss Reliability Control Plane sits alongside it, keeps an accurate record of each transaction and flags the ones that fail. Truss Core Banking and the Truss apps apply the same approach to the ledger and the customer’s phone.
Our one fixed rule
Islands Digital never holds or moves customer money. Truss keeps records and sends instructions. The licensed institution moves the money, including when it runs Truss Core Banking as its own ledger.
Our principles.
Settlement is the proof
A success message is a claim. We design for the gap between the claim and settlement.
Show the evidence
Every number we show traces back to data the customer already has.
Read before acting
We show value read-only first. Acting is optional, and the bank carries it out.
‘Unknown’ is a valid answer
If we can’t tell yet, we say so and flag it. We don’t guess.
Take as little data as possible
Only what’s needed, kept in your environment where we can, tokenised when it has to move.
Correctness blocks release
Anything that could affect money must pass its tests before it ships.