Payments · Kenya & East Africa
M-Pesa integration that works after go-live
Sandbox demos are easy. Production payouts, callbacks, and reconciliation are not. We ship Daraja-backed flows inside lending, school-fee, and ops products — with founders still in the channel at cutover.
What we build
Customer payments
STK Push, Paybill, and Till collection wired into your checkout or fee flows — with clear pending / paid / failed states.
Disbursements & B2C
Loan payouts and refunds with idempotent requests so retries do not double-pay.
Ops & reconciliation
Admin views, audit trails, and hooks to match platform records to settlement reports without a spreadsheet sidecar.
Proof from products we shipped
Not a slide about “payments expertise” — live platforms with M-Pesa in production.
Questions we hear most
Do you integrate STK Push, Paybill, and B2C payouts?
Yes. We implement the Daraja flows your product needs — customer payments (STK / C2B), till and paybill collection, and B2C disbursements — with idempotency, callbacks, and ops-visible states.
Can you connect M-Pesa to an existing app or only greenfield builds?
Both. We add M-Pesa to existing backends and ship it as part of new lending, school-fee, commerce, or ops products. Scope starts with your current stack and failure modes.
How do you handle failed payouts and reconciliation?
Explicit state machines, retry-safe disbursement keys, callback verification, and admin views so ops can reconcile without DMing an engineer. See our Insights note on shipping M-Pesa in production.
What else do you usually integrate alongside M-Pesa?
SMS, card gateways (Paystack, Stripe), CRMs, and internal APIs — with auth and monitoring that fit Kenyan network realities.
Have a payments cutover on the books?
Bring your flow, stack, and go-live window. We’ll stress-test feasibility and whether we’re the right partner.