Skip to content

The ledger is the product: what African fintech should learn from Synapse

A US banking-as-a-service intermediary froze roughly $265M because its ledger never reconciled with the partner bank's. That is not an American problem — it is a warning about how African rails are built.

Author
Mozaca Labs
Published
June 20, 2026
Read time
7 min read

In 2024 a banking-as-a-service intermediary collapsed and froze roughly a quarter of a billion dollars of end-customer money. No rail went down. No exchange was hacked. The company's internal ledger simply stopped agreeing with the partner bank's records, and once the two diverged, nobody could prove who was owed what. It is tempting to read that as an American problem. It is not. It is a warning about how most pooled-account financial products — including African mobile money — are built.

01 / 03

The failure was a reconciliation failure

The money moved through pooled 'for benefit of' accounts: one big balance at a bank, subdivided by an intermediary's own ledger into thousands of customer positions. That design is fine — until the intermediary's ledger and the bank's balance drift apart and there is no continuously reconciled, per-beneficiary record to fall back on. Regulators responded by expecting daily, per-beneficiary reconciliation of custodial accounts. The market responded by realizing something simpler: for infrastructure, the ledger is not a feature behind the product. It is the product.

02 / 03

African rails have the same shape

Mobile money runs on pooled trust accounts. Agent networks run on float that is constantly rebalanced. Cross-border corridors settle through several parties before value lands. Every one of those is the same pooled-balance, per-beneficiary-attribution problem, at a scale where a small reconciliation gap becomes a large, unprovable one. When Union54's card program suffered an attempted $1.2B chargeback fraud, card issuing across parts of the continent paused for months. That was not a design-polish failure — it was a settlement-and-risk-engineering failure. The lesson repeats: the parts customers never see are the parts that decide whether the product survives.

03 / 03

What 'a better ledger' actually means

  • Double-entry and immutable: balances are derived from an append-only event log, never edited in place.
  • Reconciles to the partner, not just to itself: the load-bearing control is agreement with the bank's and rail's records, matched continuously.
  • Per-beneficiary sub-ledger: every shilling in a pooled account is attributable to a named owner at all times.
  • Continuous, not end-of-day: drift surfaces in exception queues as it happens, not at month-end.
  • Signed and recoverable: hash-chained, correlation-ID'd evidence lets you reconstruct position at any past moment.

None of this is glamorous, and none of it demos as well as a wallet animation. But it is the difference between a product a regulator trusts and one that freezes customer money the first time two systems disagree. That is why, when we describe Mozaca's platform, we lead with the ledger — not because it is the most exciting part, but because it is the part everything else depends on.

End · Mozaca Labs

Have a system worth building?

Brief us on the seam you’re trying to engineer.