The ledger stays stricter than the rail
Why I keep a wallet's balances separate from the payments company underneath them.
A payments company can move money. It should not become the product.
I keep seeing designs where the wallet, the ledger, and the rail get folded into one sentence. Then a balance becomes whatever the last callback said. A dispute becomes a screenshot. The person holding the phone cannot tell whether the money is held, released, or lost.
Three lines, not one
On Reton I keep those as three lines:
- Wallet — what a person sees.
- Ledger — double-entry, and stricter than the partner’s status codes.
- Rail — Interswitch underneath: cards, transfers, and bill payments.
The rail reports movement. The ledger decides what the product is allowed to believe.
That split is also what I look at in a consultation. A useful design review starts by asking which system is allowed to say the balance changed.
If the answer is “whatever the gateway returned,” the product is already softer than the money it claims to hold.