Wallet infrastructure with a ledger you can audit line by line.
WalletD gives fintech teams the whole money stack, wallets, top-ups, payments, rewards, marketplace, on a double-entry ledger of record that reconciles by construction. One API. Your infrastructure.
var body = Map.of(
"from", "user-42",
"to", "@grace",
"amount", 2500, // minor units, $25.00
"currency", "USD");
Transfer transfer = client.post(
"/v1/transfers", body, "xfer-ada-grace-001", Transfer.class);
No SDK to install. The API is plain HTTP + JSON with a published OpenAPI spec. Amounts are integer minor units, never floats.
Why WalletD
The correctness of a ledger. The reach of a wallet platform.
Ledger tools keep your books but leave you to build the product. Wallet platforms ship the product but cannot show you clean books. WalletD is both halves, provably tied together.
Provable correctness
A true double-entry ledger of record where every movement writes balanced legs that net to zero per currency. Integer minor units, never floats. Idempotent calls replay byte-for-byte. A built-in verifier re-checks seven invariants on every ledger, on a schedule.
The complete money stack
Not just bookkeeping. Wallets, top-ups, peer-to-peer, payments with holds, refunds, payouts, credit lines, fee schedules, a rule-based rewards engine, subscriptions, and marketplace commission, all behind one REST API, all posting to the same auditable ledger.
Deploy anywhere, own your data
Multi-tenant by design, with each tenant's ledger physically isolated on its own database and role. Runs on your own infrastructure via Docker, no black box, no data leaving your control. The ledger core is domain-agnostic: nothing wallet-shaped is baked in.
One platform
Every movement lands in the ledger of record.
Your app calls one API. WalletD runs the money paths; LedgerD keeps the books, physically isolated, append-only, and verified on a schedule. Nothing settles that the ledger did not record.
Your application
REST, HTTP + JSON
Edge gatewayauth, rate limiting, fail-closed on money routes
WalletDtop-ups, transfers, payments and holds, refunds, payouts, rewards, subscriptions, marketplace
Identity and credentials
Signed webhooks
double-entry postings
LedgerD, ledger of recordappend-only, idempotent, verified, one isolated database per tenant
Evidence, not adjectives
Books that reconcile to the entry.
An independent audit recomputed the entire ledger directly from raw records, no trusting the software's own checker. Every figure below is cited to that audit and to the load baseline, and every number is from testing on synthetic data.
5,455,009
ledger entries recomputed with zero exceptions
Independent SQL audit, 2026-08-18. Conservation, reconciliation, authorisation and lifecycle checks all returned zero over 5 ledgers.
0
balance drift across 7,463 accounts
Cached balances vs. balances recomputed from full history. Total absolute drift: 0.
1,394,739
reward grants tie out exactly to the ledger
Domain records reconciled against ledger postings on both count and amount. Zero missing, duplicate, or non-positive grants.
400 tx/s
sustained payments in the load baseline
Synthetic benchmark, single host, split-ledger architecture (2026-08-14). A payment is authorize plus capture. Correctness invariants held throughout.
We are working with a small number of teams building wallet and money products on WalletD. If that is you, let's talk. You will get direct access to the people who built it.