M-Pesa STK Push vs Paybill for Your Kenyan Website: Which One Actually Converts Better?
Two ways to take M-Pesa on your website. One is killing your sales.
If you sell anything online in Kenya, you need M-Pesa. But how you implement it matters enormously. We've analyzed checkout data from 40+ Kenyan e-commerce sites using both methods. The difference in conversion rate is staggering.
Option 1: Paybill/Till Number (The Old Way)
How it works
Customer checks out → sees your Paybill or Till number → opens M-Pesa app (leaves your site) → sends money manually → enters reference number → comes back to your site → clicks "I've paid" → you manually confirm.
Conversion rate data from our analysis
- Average completion rate: 35-45%
- Drop-off points: Opening M-Pesa app (15% drop), entering reference number (20% drop), coming back to site (10% drop)
- Average time to complete: 2-4 minutes
- Manual reconciliation needed: Yes (time and errors)
Pros
- Easiest to set up (no coding needed, just display your Paybill number)
- Works on any website, any platform (even Wix, Squarespace)
- No Safaricom API approval needed
- No ongoing technical maintenance
Cons
- Very low conversion rate — 40% of customers who start checking out never complete
- Manual reconciliation — you or someone on your team must match payments to orders (errors happen)
- No instant confirmation — customers aren't sure if you received payment
- High support burden — "Did you get my payment?" questions constantly
- Reference number errors — customers type wrong number, payment gets lost
Option 2: STK Push via Daraja API (The Right Way)
How it works
Customer checks out → enters Safaricom phone number → clicks "Pay" → receives pop-up on their phone → enters M-Pesa PIN → payment confirms instantly → order completes automatically. They never leave your site.
Conversion rate data from our analysis
- Average completion rate: 70-85%
- Drop-off points: Entering PIN (the only step — 15-30% drop)
- Average time to complete: 30-45 seconds
- Manual reconciliation needed: No (automatic)
Pros
- 40-50% higher conversion rate vs Paybill
- Frictionless experience — customer never leaves your site
- Instant confirmation — automatic order completion
- No manual reconciliation — system matches payment to order
- Better customer experience — feels professional and trustworthy
- Works on mobile perfectly — designed for phones
Cons
- Requires developer setup (not DIY on most platforms)
- Needs Safaricom Daraja API approval (3-7 business days, free)
- Requires HTTPS (SSL certificate) — you should have this anyway
- Small ongoing maintenance (Safaricom occasionally updates API)
The data: Real examples from Kenyan businesses
Case 1: Nairobi fashion store
- Switched from Paybill to STK Push
- Checkout completion: 38% → 82%
- Monthly revenue increase: KES 280,000
- Manual reconciliation time: 15 hours/week → 0 hours
Case 2: Kiambu restaurant (online ordering)
- Switched from Paybill to STK Push
- Order completion: 42% → 76%
- Abandoned carts recovered: KES 45,000/month
Case 3: Mombasa tour operator (deposits)
- Switched from Paybill to STK Push
- Deposit completion: 51% → 88%
- "Where's my payment?" emails: 40/week → 3/week
Customer psychology: Why STK Push wins
When customers see a Paybill number, they think: "This is inconvenient. I'll do it later." Later never comes. Or: "I'll copy this number wrong." Or: "I'll forget to come back."
When customers see an STK Push prompt, they think: "Oh, this is easy." They enter their number. The phone buzzes. They enter PIN. Done. The mental friction is minimal.
What about customers without Safaricom?
STK Push only works on Safaricom (about 85-90% of Kenyan mobile money users). For Airtel/Telkom customers, offer Paybill as a fallback. Best practice: Primary STK Push for Safaricom, secondary Paybill for others.
Implementation cost comparison
Paybill implementation
- Setup: Free (just display your number)
- Hidden cost: Reconciliation time (5-15 hours/week = KES 10,000-30,000/month in staff time)
- Lost sales: 40-50% of checkout abandonments
STK Push implementation
- Setup: KES 15,000-30,000 one-time (developer time + API integration)
- Safaricom approval: Free
- Monthly: Negligible (just standard M-Pesa transaction fees)
STK Push pays for itself in recovered sales within 1-2 months for most businesses.
Which platforms support STK Push?
- WordPress/WooCommerce: Yes (plugins or custom)
- Custom site (React, Next.js, HTML): Yes (direct API integration)
- Shopify: Yes (via Flutterwave or Paystack apps)
- Wix: Limited (some workarounds, not ideal)
- Squarespace: No (Paybill only)
The bottom line
If you're serious about selling online in Kenya, STK Push is non-negotiable. Paybill leaves 40-50% of your sales on the table. The upfront developer cost is minor compared to the monthly revenue you're losing.
Need STK Push on your site?
We integrate M-Pesa STK Push on all our web design projects. If you have an existing site on Paybill, we can upgrade it. Message us on WhatsApp for a fixed quote — usually KES 15,000-25,000 depending on your platform.

