📱Accept M-Pesa Payments on Your Website: A Kenyan Guide

Roughly 96% of Kenyan households use M-Pesa. When a customer lands on your site and the checkout asks for a card they don't have — or worse, for a 'paybill then screenshot' dance — you've already lost them. Friction is the silent killer in Kenyan e-commerce, and the fix is letting customers pay in the way they already pay for everything else.

The good news: accepting M-Pesa online has moved from 'enterprise integration' to a standard feature. The costs are modest, the developer ecosystem is mature, and it unlocks serious conversion gains for booking, retail and service businesses.

STK push is the 'please enter your M-Pesa PIN' flow you see in apps like Uber and e-commerce stores. Your customer checks out, enters their phone number, M-Pesa opens on their phone, they confirm, and your site verifies the payment in seconds — all automatically.

This is done through Safaricom's Daraja API (the Lipa na M-Pesa Online / STK Push endpoint). It's the right choice for any checkout that should feel instant: e-commerce, bookings, deposits, pay-per-view content. Of the three options it requires the most development work, but it's a solved problem — experienced developers implement it in days, not months.

A paybill number is how many Kenyan businesses still collect M-Pesa. The website shows your paybill and account number, the customer pays in their M-Pesa app, and — with API integration — the site automatically reconciles the payment against their order.

Paybill works well for larger bills, invoices and when you already have a paybill for other channels. The catch: it's more manual and reconciliation-heavy. Combined with a website it still saves your team hours a week compared to matching screenshots by hand.

A till number on a website with 'send us your receipt' is what most Kenyan businesses do, but it's a placeholder, not a solution. It means someone on your team matches payments to orders manually — a cost, and a source of errors, that grows with every order.

If your volume is a handful of orders a week, a till with manual confirmation works while you validate your product. Plan from day one to upgrade to STK push as volume grows.

The API itself is free to integrate — Safaricom charges per transaction (roughly 1%–1.5% depending on your merchant agreement and tariffs). The real cost is development: expect STK push integration to add KES 20,000–60,000 to a build, depending on whether you need receipts, refunds, invoice generation and reconciliation dashboards.

You'll also need a merchant/API account with Safaricom (Daraja credentials) and, for compliance, your business registration details. A good developer handles the full application flow — many Kenyan businesses stall here because the paperwork is unfamiliar, not because it's hard.

Before approving a build with M-Pesa: does the quote include the Daraja account setup? Will payments be verified automatically or manually at first? What happens if a transaction times out? Is there a reconciliation report, or just a payment log? Do they test with real and sandbox credentials? And who maintains the integration — M-Pesa's API changes break silent sites?

Buying a payment integration is buying a promise that money works end-to-end. The difference between a well-built integration and a bolted-on one shows up on your first busy day.