What STK Push actually does for a Kenyan checkout

If you sell anything in Kenya online or on a phone, you have felt the gap between “customer says they paid” and “money is actually in the business.” STK Push—officially Lipa Na M-Pesa Online—closes that gap by putting the payment prompt on the customer’s phone instead of asking them to remember a till or paybill.

This article is for owners and builders who want the mental model, not a dump of API fields. When you understand the flow, choosing tools (including NetPay at pay.nethub.co.ke) gets easier.

The customer experience in one minute

Your system decides an amount and a phone number. Safaricom sends a prompt to that handset. The customer enters their M-Pesa PIN. If they accept, funds move according to your shortcode setup. Your server should learn the outcome from Safaricom’s callback—not from a forwarded SMS screenshot.

That last point matters. Manual confirmation is slow and easy to fake. Automated confirmation is what lets you release goods, unlock a subscription, or mark an invoice paid without a human in the loop.

What has to be true on the business side

You need a legitimate collection channel (paybill or till) and a way to talk to Daraja or a provider that talks to Daraja for you. Sandbox lets you practice without real money. Production needs HTTPS callbacks, careful logging, and a plan for failed or timed-out prompts.

None of this replaces good product design. A clear amount, a sensible timeout message, and a way to retry still matter when the network hiccups.

Where this fits with NetPay

NetPay is NetHub’s collections surface for teams that want M-Pesa payment flows without rebuilding Daraja plumbing every time. Use this guide to understand the job; use the product when you are ready to collect in production. For deeper trade-offs between direct Daraja and hosted APIs, read our comparison of payment approaches in Kenya.