Integrate M-Pesa STK Push checkout for a Nairobi store: 2026 guide

The verdict in three sentences

A native mobile money checkout — where the customer pays without leaving your page — completes at 68 % versus 41 % for a plain redirected external link (2026 order of magnitude, East African stores). M-Pesa's Daraja STK Push charges roughly 1.5 % merchant fees with a KES 250,000 per-transaction cap, still competitive for local commerce. The real technical decision isn't *whether* to integrate but how: a fast hosted SDK or a controllable direct API.

Hosted SDK or direct API: the structuring decision

Most mobile money rails offer two integration paths. The hosted checkout creates a payment session on the provider side and redirects (or overlays) a secure page; you never touch the customer's credentials. The direct API — Daraja STK Push in M-Pesa's case — lets you build your own screen, trigger the collection and manage status via webhook: more control, more responsibility.

For a first Nairobi store that needs to collect payments fast, the hosted checkout is enough. Once volume passes a few hundred orders a month and the brand wants a consistent funnel, the direct API earns its keep.

Fees, caps and latency: the 2026 numbers

Costs drive your margin. Here are early-2026 orders of magnitude for a Kenyan merchant, with Wave (Côte d'Ivoire) as a comparison since many stores target multiple countries.

Two recurring traps: never confirm an order on the redirect alone (the customer may close the tab) but always wait for the signed webhook; and set a 90 s order timeout with a reversible "pending" status, because real latency climbs at peak hours.

Mini case study

Grace, who runs a cosmetics shop in Westlands (Nairobi), sold via an M-Pesa Paybill number pasted into DMs. Of 300 payment attempts per month, only 123 completed (41 %). After integrating STK Push directly into her online store, completion rose to 68 %, i.e. 204 payments for the same traffic. Average basket KES 2,300: she moves from KES 282,900 to KES 469,200 in monthly collected revenue, up KES 186,300. M-Pesa fees (~1.5 %) on that surplus cost only KES 2,795. The 4-day build pays for itself within the first two weeks.

FAQ

What does M-Pesa STK Push really cost a merchant in 2026? Budget around 1.5 % per collection, with a KES 250,000 per-transaction cap. On KES 1,000,000 collected you keep about KES 985,000.

Is a webhook mandatory? Yes, for reliable accounting. A redirect can fail (closed tab, dropped network) whereas the signed webhook confirms the real payment within 3 to 8 seconds.

Does hosted checkout hurt the mobile experience? No — the provider page is mobile-optimised and fast even on 3G. You lose some visual control but gain compliance and 2 dev days.

Can one codebase collect both M-Pesa and Wave? Not directly, but through a payment abstraction layer exposing a single checkout() interface that routes to M-Pesa (Kenya) or Wave (Côte d'Ivoire). That's exactly the architecture we deploy.

How long to reach production? Between 2 and 4 dev days depending on hosted SDK vs direct API, plus 24-48 h of merchant KYC validation.

Let's talk about your project. We integrate M-Pesa STK Push into your checkout in 2-4 days, webhook and reconciliation included. WhatsApp +221 77 596 93 33.