Payments for Kenyan developers and online sellers
Accept M-Pesa and cards from one clear dashboard
Collections, subscriptions and payouts for Kenyan businesses, with every feature honestly labelled live, test-mode or planned.
Takes you to sign-up.
Honest by design
Every feature carries a status you can read
Payments products tend to overstate. SokoFlow is modular, so providers, banks and countries are added independently, and each one is labelled as it stands today.
- Live
- Available to use with real money. Nothing carries this label until it has been put into production.
- Test mode
- Works against sandbox credentials so you can build and check your integration without moving funds.
- Planned
- On the roadmap and not yet usable. We list it so you can plan around it, not so you can rely on it.
How a payment flows
From the customer's phone to your bank statement
-
Collect
A customer pays by M-Pesa or card. Each payment lands in one list with its method, status and amount in KSh.
-
Bill
Recurring plans keep a next charge date per customer, so you can see who is due and who is past due.
-
Pay out
Funds settle to your bank as a payout. Each payout shows the bank, its status and the payments it contains.
-
Reconcile
Match settlements against payments in the same dashboard instead of stitching exports together.
The old way and this way
Built for teams tired of fragmented gateways
| Fragmented gateways | SokoFlow | |
|---|---|---|
| Where you look | Several gateway dashboards and spreadsheets | One dashboard for collections, subscriptions and payouts |
| Developer experience | Uneven tooling and documentation | A clean developer API alongside the dashboard |
| Reconciliation | Opaque, done by hand after the fact | Payouts show the payments they contain |
| Adding a provider or bank | Rework around one gateway | Modular, so each is added independently |
| What is ready | Hard to tell from the marketing page | Labelled live, test-mode or planned |
Payments infrastructure, built for Kenya first.