So you're weighing STK Push against a manual Paybill for your hotspot? Okay, we'll go over how each handles passes, why the payment prompts sometimes glitch out, and how to set up your login page so customers can pay without running into problems.

20 Nov,2026, 8:29
Hey, how you ask customers to pay can make a real difference to how many of them actually finish paying. Usually there are two options: STK push or having people type in the details manually (Paybill).
Today we're going to go over what we know and don't know about conversion rates for each one and how to figure out which works best for your hotspot
Overview of options
I know the question makes it sound like Paybill and STK push are opposites, but they aren't. Paybill is a business account type. STK push just means starting a payment. With Safaricom's business tools, you can send an STK push to a Paybill or a Till, so you can have both a Paybill and STK push. The real difference for hotspots is whether the payment gets started by the system or manually by the user. With the STK push, the user gets a prompt to pay right on their phone. With manual paybill, users have to type the Paybill and account number into M-Pesa themselves.
User journey (STK push)
The customer connects to the Wi-Fi, picks a package, types in their phone number, and hits pay. A prompt pops up on their phone asking them to pay the amount to the business. They enter their M-Pesa PIN, the payment goes through, the system confirms it, and the internet gets turned on. They've only had to enter two things.
User journey (manual Paybill)
The customer connects to Wi-Fi, picks a package, and writes down the amount, business number, and account number. They close the page and open M-Pesa, choose 'Lipa Na M-Pesa,' and then Paybill. They type in the business number, account number, amount, and PIN. Then they go back to the login page, where they might need to enter the M-Pesa confirmation code, or it might confirm on its own. Internet gets turned on. That's four details to enter, and they had to leave the page and come back.
More steps mean more chances for mistakes, frustration, or people giving up. Because of that, STK push is generally expected to convert better. But...
Is it really better for conversions?
For most small packages, STK push should get more people to finish. There's less for the user to type, they don't have to copy info between pages, and they never leave the page. There is no risk of a wrong account number, and the amount fills in automatically so nobody can underpay. Since the system started the payment, it's also easier to match it to the right customer. That is why most small package billing systems use STK push as their main option.
Still, STK push can sometimes fail, and manual payments get around some of those problems. If the customer's phone is off or has no signal, they won't get the prompt. If the prompt shows up out of the blue, they might think it's a scam and cancel. They might type their number wrong or use someone else's number that never replies. If they get distracted, they might miss it, since the prompt expires after about a minute. If they already have another M-Pesa transaction going, the prompt may be delayed until that one finishes. Some phones also struggle with the menu. And if a customer doesn't have enough money, the payment fails with either option.
Manual Paybill can fail too. Customers might enter the wrong business number, account number, or amount. They might forget to come back to the login page. If they get confused, they might give up. And if someone pays with the wrong account number, there's no way to match that payment to anyone, so it has to be tracked down later.
So what's our conclusion?
For short-term passes, STK push is probably the best main option, but keep manual payment available as a backup in case STK push causes problems.
For monthly payments, though, the answer is different. Which method works better for your hotspot depends on your customers, your login page and how strong the mobile signal is where your customers are. You can measure that for yourself.
Causes of failure with STK push and solutions
Safaricom's tools will state why the STK push failed, and your billing system can read this. The common causes of failure are customer cancellation, no response within the time limit, phone unreachable, incorrect PIN, insufficient balance, another transaction in progress, expiration, and failure to send. Each of these issues can be solved on your login page.
Cancelled
Some customers may cancel by accident. To reduce this, explain clearly what will happen before they press pay.
No response
Customers may not see the prompt. When they press pay, show a clear, visible message saying, "Check your phone and enter your M-Pesa PIN." Include a countdown timer, or let them know the prompt will expire in about one minute. Let customers retry the payment.
Phone unreachable
Ask customers to make sure their phone is switched on and that they have entered the right number. Show the number in the format "We sent a request to 07xx xxx xxx." That makes it easy to spot a wrong number. Let customers change the number.
Incorrect PIN or insufficient balance
Tell customers clearly what went wrong.
For example: "The PIN was not correct. Try again" or "Your M-Pesa balance is too low for this pass." Don't just show "Failed," because that puts people off.
Transaction in progress
Ask customers to wait a minute and try again.
Payment not sent
Add a second payment option to the page, such as manual payment details. Make it easy for customers to pay that way. This means a technical issue won't stop sales.
Issues from your side
If customers don't see the prompt straight away, they may press pay several times and receive multiple prompts. Once pay has been pressed, disable the button and tell the user that a request has been sent. Don't wait for Safaricom to send a response to your system, because it may be delayed.
A good system will also ask Safaricom for the payment status of any pending payments. Once the pass is active, always send a confirmation message so customers know the payment went through.
Design Your Login Page to Improve Conversions
You can lose a sale before a customer even reaches the payment step. A few simple changes can make it easier for people to sign up and pay.
Offer just a few packages, and clearly show the price and what's included in each one. Too many choices can put people off, so put your most popular package first. Show prices in shillings, not codes or symbols.
Make the phone number field easy to use.
Open the phone keypad automatically, and don't restrict the number format. Accept numbers that start with 07, 01, or +254. If a customer has used your site before, fill in their number for them where you can.
Keep the form short.
Asking for extra details like a name or email address can make people give up.
Make the pay button big and easy to reach with a thumb.
After someone taps it, show them what's happening: request sent, check your phone, enter your PIN, and waiting for confirmation. Once the payment goes through, update the page and give them internet access automatically. They shouldn't have to press anything else.
Keep the page light and reliable.
Some customers may open your page without an internet connection, so keep it lightweight. Test it on different real devices, including older phones, and make sure it loads quickly, since people don't want to wait long on a login page.
Add the payment page URL to your walled garden list, and check that people who haven't paid can still open it. Include a phone number customers can call if they get stuck.
Offer manual payment as a backup.
Manual payment should be available, but it doesn't need to be the first option. Put it below the main pay button, or show it if the STK push fails.
Clearly display the business number, the account number, and a simple way to confirm payment. This gives customers another option if they'd rather pay from inside M-Pesa or never get the STK push prompt, without getting in the way of everyone else.
If you need to match payments to customers using an account number, give each customer a number they can easily copy, and ask them to enter it exactly as shown.
When is a manual Paybill useful?
Manual payment isn't the best fit for everyone, but it can work well for some customers.
For example, monthly home customers using PPPoE connections already have an account number. Paying through Paybill with that number makes it easier to keep track of payments. These customers usually aren't in a hurry to log in, so they can pay when it suits them. You can also send them a payment reminder by SMS or WhatsApp with the Paybill details.
Parents or landlords paying on someone else's behalf may prefer to start the payment themselves. With the STK push, the payment can only be sent to the number entered. And since STK push can sometimes fail for technical reasons outside your control, manual payment is a useful backup for all customers.
Also think about customers who can't use M-Pesa. If they only have access to another mobile money service, neither payment option will work for them. To give them a way to pay for hotspot access, you could sell vouchers for cash through agents.
To cut costs and keep clear payment records, you can use Paybill or Till alongside STK push. Many ISPs use STK push to a Till for hotspot packages and Paybill with account numbers for monthly packages. Read our article comparing Paybill and Till to learn how their fees and payment matching differ.
Figuring out which option gets you more conversions
The easiest way to check is to track conversions at each stage. For every customer who reaches your login page, track whether they opened the page, picked a package, started payment, finished payment, and got access. Your billing system should have this. Then see where most people get stuck. If lots of people pick a package but few start payment, the problem is probably your page. If lots of people start payment but few finish it, the problem is probably the prompt. If lots of people finish payment but few get access, the problem is probably the network.
Next, compare the two options. Over one week, let some customers start with STK push as the main option and let others start with manual payment as the main option. Keep track of how many people finish payment in each group. If you can't split customers this way, compare two different weeks with a similar number of customers.
Reasons for failure
If lots of payments time out, customers probably aren't seeing the prompt. Try making the instructions clearer or adding a retry button. If lots of payments get cancelled, customers may not recognise the prompt. If lots of payments fail because of low balance, offering a cheaper starting package may help. Fix the biggest problem first, then measure again.
The best option for your customers is whichever one gets you more conversions. STK push is a good place to start because it takes less effort from customers. It's still worth offering manual Paybill as a backup for people who can't pay that way.
Monthly payments often use manual Paybill as the main method. To decide which option should come first on your page, measure conversions on the page. Change one thing at a time, and let the data tell you which option to prioritise.
Popular Posts