Why we built this
Built on a lesson the industry learned the hard way.
On The Ledger exists because mutable ledgers fail — not in theory, but in practice, with real consequences for real people.
The problem
When ledgers can't agree, no one can prove who is right.
Modern financial platforms rarely operate alone. A payments company sits atop a banking partner, which settles through a licensed institution. Each layer maintains its own records. Each record tells a slightly different story. Under normal conditions the differences are small enough to ignore. Under stress, they compound into disputes that no one can resolve — because there is no authoritative record, only competing claims.
A real story
When the ledgers couldn't reconcile, the system froze.
The discrepancies
A gig-economy payments platform moved millions of dollars each month to independent contractors on behalf of business clients. It was built on a Banking-as-a-Service provider, which in turn cleared through a licensed bank. Three layers, three ledgers — each with its own version of reality.
Over time, discrepancies appeared between the platform's records and the BaaS provider's records. Under pressure to keep the books aligned, the team took the expedient path: they edited historical transactions directly. Not adjusting entries — edits to records that should have been permanent. The ledger stopped reflecting what actually happened and started reflecting what they needed it to say.
The dispute
Eventually, a larger discrepancy surfaced that couldn't be patched away. The BaaS provider and the bank found themselves in fundamental disagreement over the balance — the BaaS provider's records showed tens of millions of dollars more than the bank acknowledged. Neither party could prove their position. There was no immutable record. There was no cryptographic chain. There were only two mutable ledgers pointing at each other.
The bank froze all transactions for the BaaS provider pending resolution of the dispute.
The consequences
Overnight, the payments platform stopped paying contractors. Workers who depended on those payments went weeks without income. Most of the platform's clients, unable to wait, found other providers. The BaaS provider entered collapse proceedings. Millions of dollars in ordinary customers' savings were frozen with no clear timeline for resolution.
No one set out to commit fraud. Everyone was acting in good faith with imperfect tools. The tools were the problem.
Our answer
A ledger that can prove itself.
On The Ledger is built on the premise that financial records should be provably correct — not just to the people who operate them, but to any party who needs to verify them.
Immutability by design
Every transaction is permanent once posted. Corrections are made through new transactions, not edits. History cannot be changed — only extended.
Cryptographic chain
Each transaction is linked to the one before it through a cryptographic hash. Alter any record and the chain breaks, making tampering immediately detectable during any audit.
Independently verifiable
The event log — the true source of truth — is append-only. No operator can silently rewrite it. Any authorized party can replay the log and verify that the current ledger state exactly matches the events that produced it.
Disputes resolved with evidence
If two parties share a ledger built on On The Ledger, their records cannot diverge in ways that go undetected. Disagreements become questions of evidence, not trust.
Who it's for
Built for anyone who moves money across systems.
FinTech platforms
Move money on behalf of customers with a provable audit trail at every step.
BaaS providers
Give your platform clients confidence that your books and theirs will always reconcile.
Banks and institutions
Provide partners with independently verifiable records. Resolve disputes with evidence, not assertions.
Any business with financial complexity
If you need to prove to an auditor, a partner, or a regulator that your records are complete and untampered, On The Ledger is your foundation.