Payment systems development
Money movement that balances, every time.
Who this is for
Businesses moving money between parties—M-Pesa, bank rails, or crypto—where a lost or double-counted transaction is a support ticket at best and a compliance problem at worst.
What we build
Settlement where two legs of a trade only complete together: an M-Pesa payment confirms before a wallet is credited, so a failure partway through can’t leave one side paid and the other not. Every movement of money posts to a double-entry ledger, so nothing can disappear silently and every balance is reconcilable after the fact. Idempotent processing means a retried request or a duplicate webhook can’t double-charge or double-credit anyone.
We built ChamaMa’s ledger this way: every contribution, withdrawal, and loan disbursement posts to a double-entry ledger that stays balanced under concurrent access, so a member’s balance is always reconcilable. See ChamaMa’s ledger in production →
pesabit applies that same two-leg settlement to crypto rails: it escrows a seller’s crypto, waits for an M-Pesa STK push to confirm the buyer’s payment, and only then releases the crypto and updates the seller’s KES balance, with a hold window that protects against chargebacks. See how pesabit handles two-leg settlement →
What you get
- Reconciliation that doesn’t depend on someone comparing two spreadsheets by hand
- An audit trail for every transaction
- Settlement logic that survives a network failure mid-transaction