Build
E-commerce & payments
M-Pesa Daraja, card acquiring, and the part most people skip: reconciliation and settlement reporting your accountant can actually use.
Who this is for
Money is coming in, and matching it to what was ordered is somebody’s Friday afternoon. The checkout is the easy half; the half that costs you is everything after the payment succeeds.
A retailer taking M-Pesa
STK push at checkout, with the order marked paid by the callback rather than by a screenshot.
A SACCO collecting repayments
Payments matched to members and loans automatically, with the unmatched ones queued for a human.
A county collecting revenue
Paybill collections reconciled against the bank statement, not against a till printout.
A school collecting fees
Per-student ledgers, receipts issued automatically, and arrears visible without a spreadsheet.
What you get
A checkout that finishes
Few steps, honest totals, and a state machine that survives a dropped connection mid-payment.
Callbacks handled properly
Idempotent, retried, logged, and verified against the payment API rather than trusted.
Reconciliation your accountant uses
A daily settlement report that ties transactions to orders to the bank, with exceptions listed.
Refunds and reversals
A documented path for the ones that go wrong, with an audit trail.
PCI-sensible card handling
Card details go to the acquirer, never through your server or ours.
Source code and documentation
In your name, in your repository. You are never locked in to us.
How the build runs
Each stage ends with something you can open, and a decision you have to make. No month of silence.
- 011 week
Money mapping
Every way money arrives today, and who reconciles it. Usually the first time it has been written down.
- 021 week
Integration design
Daraja and acquirer setup, callback contracts, retry and failure policy, signed off.
- 032–6 weeks
Build
Catalogue, checkout and the settlement reporting, with a sandbox you can put test payments through.
- 041–2 weeks
Live with small amounts
Real transactions at low value until the reconciliation report matches the bank exactly.
- 051 week
Handover and care
Runbook for failed payments, training for finance, and code and accounts in your name.
What we need from you
Three things, and a project runs on time.
Most delays are not technical. They are a decision nobody was able to make, or data nobody could find.