A ledger that always balances.
Double-entry, append-only, integer cents. Every movement on the platform posts as balanced entries, holds are reserved the moment a payment is created, and pending, posted and available balances reconcile by construction — not by a nightly job that might disagree.
The three rules the books never break.
Balanced, always
Every transaction posts debits equal to credits. A transaction that doesn't balance is rejected before it is written — the ledger can never hold a movement that doesn't sum to zero.
Integer cents, never floats
Money is a decimal in minor units, precision fixed. No float rounds a fraction of a cent into existence or out of it. What the ledger says is exactly what is owed.
Append-only
Entries are never edited or deleted. A correction is a new, offsetting entry. The book is a full history, so it can always answer not just what a balance is but how it came to be.
Model the money the way the business thinks about it.
Name the buckets that matter.
Carrier Payables, Tax Reserve, Settlement Clearing, Operating — the accounts your operators actually reason about. A payment names the ledger account it posts against, so the money's meaning is captured at creation, not reconstructed later from a memo field.
- Caller-specified account on every payment order
- Entries, running balances and history per account
An account number per customer, on one real account.
Issue virtual account numbers so inbound money arrives already attributed — this dealer, this tenant, this invoice — instead of landing in one pooled account you have to reconcile by hand. Attribution happens at the rail, not in a spreadsheet.
- Inbound funds mapped to the right party automatically
- One banking relationship, many addressable endpoints
For-benefit-of, reconciled to the penny.
Hold customer funds in an FBO structure where the sub-ledger must always sum to the cash in the bank account — every day, across every tenant. The reconciliation is the platform's invariant, so "the money we hold" and "the money we owe" are the same number by construction.
- Sub-ledger balances tie to the settlement account
- Daily reconciliation designed to the penny, per tenant
Pending, posted, available — and why the difference matters.
A balance isn't one number. The platform tracks what has cleared, what is committed but not yet settled, and what you can actually spend right now — and keeps them consistent through the whole life of a payment.
Hold at creation
The moment a payment order is created, a pending hold posts to the ledger. Available balance drops immediately, so you can never double-spend money that's already promised — even before it leaves the bank.
Post at settlement
When the payment completes, the hold converts to a posted entry. If it returns or fails, the hold reverses. Posted balance only ever reflects money that truly moved.
Available = the truth
Available balance is posted minus outstanding holds. It's the number an operator can trust to make the next decision, because it already accounts for everything in flight.
Read a ledger account
GET /v1/ledger-accounts/:id { "name": "Carrier Payables", "currency": "USD", "pendingBalanceCents": 250000, "postedBalanceCents": 0, "availableBalanceCents": -250000 }
Walk the entries
GET /v1/ledger-accounts/:id/entries [ { "direction": "Debit", "amountCents": 250000, "status": "Pending", "transactionId": "tx_…" }, // posts to "Posted" on settlement, // reverses on return — never edited ]
The ledger is the source of truth, so it acts like one.
Every rail posts here
ACH, RTP, wire, book transfer and USDC all settle to the same double-entry ledger. Treasury reads one book across every network — fiat and stablecoin land in the same place, in the same units.
Accruals are real postings
When a liability is fixed — a fuel-tax return filed, an operator settlement owed — it books as a balanced accrual and relieves to zero when paid. The obligation lives in the ledger, not in someone's notes.
A basis it can defend
Every figure carries its origin. The irreversible acts — remitting, settling, collecting — refuse a figure whose basis is demo data or a missing input, rather than posting a number the book can't stand behind.
History that can't be rewritten
Because entries are append-only, an audit is a read, not an investigation. The path from a raw movement to a reported balance is always fully in the book.
Books your finance team can stand behind.
Double-entry, append-only, and reconciled to the cent — under every payment you make.
Request access → Compliance & controls →