WiFi Billing System Kenya: How to Sell WiFi Like Airtime with M-Pesa and MikroTik

If you want to sell internet access in Kenya—on the street, in an apartment block, in a mall, at a café, or across multiple sites—you need a WiFi billing system that takes instant M-Pesa payments, issues access fairly, and protects your revenue. This guide shows you what a modern WiFi billing system in Kenya should do, how to package and price plans Kenyans actually buy (like KES 10/KES 20 hotspot bundles), what to expect during MikroTik setup, and how Pawa WiFi helps you sell WiFi like airtime from day one.

What a WiFi billing system in Kenya actually is

A WiFi billing system is the engine behind your hotspot business. It combines a captive portal (the login page users see), payment collection (often M-Pesa STK), access control (who gets which speed/limit), customer and voucher management, and reporting.

In Kenya, “good” means:

• Instant M-Pesa STK push so people pay and get online in seconds.
• Captive portal that loads quickly on Android/iOS and low-end phones.
• Simple packages: e.g., KES 10 for 30 minutes, KES 20 for 1 hour, KES 100/day, KES 1,500/month in apartments.
• Support for vouchers where cash sales are common (kiosk, caretaker, attendant).
• Smooth MikroTik onboarding and stable RADIUS authentication.
• Clear daily reports for reconciliation and agent payouts.
• Revenue protection: device limits, expiry, and fair usage so one buyer doesn’t share the whole neighborhood.

Pawa WiFi is built for Kenya-first operators with these realities in mind.

Who uses a WiFi billing system in Kenya?

• Street hotspots and town WiFi vendors selling KES 10/KES 20 bundles.
• Cafés, salons, restaurants that want paid access instead of open WiFi.
• Apartment ISPs and property managers handling monthly renewals and upgrades.
• Cyber cafes and co-working spaces with timed/day passes.
• Schools, hostels, and churches running weekend access.
• WISPs operating multiple locations who need central management and reporting.

If you collect money for WiFi, you need billing that’s fast, fair, and simple to reconcile.

Core building blocks you should insist on

• M-Pesa STK push on the captive portal: Customer selects a package, enters phone number, receives STK, pays, and gets online automatically.
• Vouchers: Generate printable or digital voucher codes and sell through agents—no phone number required.
• Packages with speed, time, and/or data limits: e.g., 2 Mbps for 1 hour, 5 Mbps for 24 hours, 500 MB for KES 50.
• Device controls: limit number of devices per purchase, device binding (MAC), and prevent simultaneous sessions when not allowed.
• MikroTik hotspot integration: Cloud AAA (RADIUS), walled garden for payment pages, and profile-based shaping.
• Reports: daily totals, per-location performance, per-package revenue, and agent sales.
• Revenue protection: auto-expiry, one-time voucher use, session enforcement, and automatic logouts when time/data ends.

Pawa includes these out of the box so you can focus on sales and network quality.

Packaging your WiFi the Kenyan way: What actually sells

Start with 3–5 packages. Don’t overcomplicate on day one. Mix short, medium, and daily options people can understand quickly.

Example hotspot menu:

• KES 10: 30 minutes, up to 2 Mbps
• KES 20: 1 hour, up to 3 Mbps
• KES 50: 3 hours, up to 5 Mbps
• KES 100: Day pass (24 hours), up to 5 Mbps

Apartment or monthly menu:

• KES 1,000: 30 days, up to 5 Mbps (single device)
• KES 1,500: 30 days, up to 10 Mbps (2 devices)
• KES 2,000: 30 days, up to 15 Mbps (3 devices)

Tips that work in Kenya:

• Keep the short options cheap (KES 10/20). They drive high conversion at the hotspot.
• Make device limits clear. Many users have two devices; price a two-device plan attractively.
• Use speed tiers for fairness. 2–5 Mbps is enough for mobile social apps; reserve higher speeds for pricier plans.
• Put the most popular plan in the middle of your list. People tend to pick it.
• Offer vouchers at the same price as STK to avoid confusion.

With Pawa, create packages in minutes and push them to one or many locations instantly.

Payment flows that feel natural in Kenya (and how Pawa handles them)

1) M-Pesa STK push (C2B) on the captive portal

• User connects to your SSID; captive portal opens automatically.
• They select KES 10/KES 20/etc., enter their M-Pesa number, and tap Pay.
• An STK prompt appears on their phone. Once paid, Pawa authorizes the session.
• Access starts immediately with the package’s speed/time/data.

Why it matters: no manual reference numbers, no screenshots. It’s quick and reduces disputes.

2) Manual Paybill/Till with reference (fallback)

• If STK is slow or a user prefers manual payment, they can pay to your Paybill/Till.
• They enter the M-Pesa confirmation code on the portal.
• Pawa verifies and, when valid, grants access.

Use case: When STK push delays occur during network congestion.

3) Vouchers for cash sales and agent networks

• Your agent sells a voucher (e.g., KES 20, 1 hour) printed or digital.
• User connects, enters the voucher code, and goes online.
• Pawa enforces one-time use and expiry.

Great for shops, cinemas, salons, apartments with caretaker sales, and places with limited mobile money connectivity.

4) Apartment monthly renewals with reminders

• Tenant connects, selects their monthly plan, and pays via STK.
• On renewal day, they repeat the flow from the captive portal.
• You can display renewal messaging inside the portal as the end date approaches.

Tenants don’t need to call you; they pay and continue immediately. Pawa automatically ends access at expiry and resumes after payment.

M-Pesa reconciliation: keep every shilling accounted for

Daily discipline keeps your hotspot honest and profitable.

Recommended reconciliation routine with Pawa:

• Check Pawa’s daily revenue summary by location and by package.
• Match totals to your M-Pesa statements for your Paybill/Till.
• Review agent voucher sales versus cash collected and outstanding stock.
• Investigate mismatches: common causes include reversed payments, delayed callbacks, or manual entry errors.
• Export Pawa reports to CSV for your bookkeeper.

If a customer disputes payment:

• Search by phone number or M-Pesa code in Pawa.
• Confirm whether access was granted and for how long.
• If an M-Pesa reversal occurred, the portal will show it; access should have ended accordingly.

Pawa logs each transaction and session, so you can verify facts quickly.

Voucher sales that don’t leak revenue

Vouchers work well in high-traffic, cash-friendly spots. Best practices:

• Choose secure code lengths (8–10 characters) to prevent guessing.
• Print cleanly; smudged codes slow buyers down.
• Display a simple price board: KES 10 (30 mins), KES 20 (1 hr), KES 100 (day).
• Train agents: one code per sale, no code previews before payment.
• Track agent stock in Pawa; settle commissions against redeemed codes.
• Rotate voucher batches periodically and archive old ones for audit.

With Pawa, you can generate voucher batches per location/agent, set batch expiry, and view redemption rates in real time.

MikroTik setup in Kenya: what to get right from day one

MikroTik is popular because it’s affordable, stable, and widely supported by installers in Kenya. To run a clean hotspot with Pawa’s cloud AAA, focus on the following.

Network design essentials

• Use a dedicated LAN/VLAN for hotspot users; keep management devices separate.
• Place access points on a bridge behind the MikroTik; avoid double NAT if possible.
• Ensure stable upstream bandwidth; shape per-user at the MikroTik to avoid congestion.

Time and identity

• Set the correct timezone and NTP so voucher and session expiry are accurate.
• Give your router a unique identity that matches your Pawa location name.

Hotspot server and RADIUS

• Create the hotspot on the interface/bridge serving users.
• Enable login methods compatible with captive portals (HTTP-CHAP/HTTP-PAP as needed).
• Add Pawa as a RADIUS server (AAA) using the secret provided in your Pawa dashboard.
• Set accounting to send start/stop updates for precise reporting and expiry.

Walled garden and DNS

• Whitelist Pawa’s captive portal and payment endpoints in the hotspot walled garden so users can reach the portal before paying.
• Ensure DNS works fast; consider using a reliable public resolver if upstream DNS is slow.

Bandwidth shaping per package

• Use MikroTik profiles or RADIUS attributes from Pawa to set rate limits per plan.
• Start conservatively (e.g., 2–5 Mbps per user on short plans) and adjust after observing peak-time performance.

Basic security

• Change default passwords; use strong secrets for RADIUS.
• Disable unused services on the MikroTik and limit Winbox/SSH to management IPs.
• Back up the config after every change.

Common pitfalls in Kenya (and how to avoid them)

• Double NAT behind the ISP router: put the ISP device in bridge mode or request a public IP; if not possible, ensure consistent port forwarding for RADIUS if required.
• Wrong timezone: sessions don’t expire as expected. Set Africa/Nairobi and enable NTP.
• STK push not arriving: usually poor mobile signal, M-Pesa congestion, or phone in airplane mode. Offer voucher fallback.
• Captive portal not popping: some phones need the user to visit a site first; show posters with “Connect to SSID, open your browser, visit any page to see the portal.”
• Slow portal on cheap phones: keep your portal design light; Pawa’s default theme is optimized for speed.

Quick-start checklist for MikroTik + Pawa

• Set timezone to Africa/Nairobi and enable NTP.
• Create bridge for hotspot; attach AP ports.
• Configure DHCP on hotspot bridge.
• Run hotspot setup on the bridge.
• Add Pawa RADIUS server details from your dashboard.
• Enable RADIUS accounting.
• Add walled garden entries for Pawa portal and M-Pesa endpoints.
• Create NAT masquerade for hotspot subnet.
• Test with KES 10/KES 20 packages before opening to the public.

Pawa’s router onboarding shows you the exact fields to copy, the secret to use, and the URLs to walled garden, reducing guesswork.

Revenue protection: stop freeloading without punishing honest buyers

A Kenya-ready WiFi billing system should provide:

• Device limits per purchase (e.g., 1 or 2 devices on short bundles, more on monthly).
• Session enforcement: prevent simultaneous logins beyond the device limit.
• One-time voucher use, hard expiry, and auto-logout on time/data end.
• Per-user bandwidth caps so one user doesn’t saturate your link.
• Optional idle timeouts to recycle capacity during peak hours.

Pawa enforces these rules centrally so your MikroTik stays lean and predictable.

Launch-day checklist: hit revenue on day one

• Captive portal is branded, loads fast, and shows 3–5 clear packages.
• M-Pesa STK push tested on at least three different networks/devices.
• Voucher batch printed and counted for initial agents.
• MikroTik backed up; hotspot portal and RADIUS accounting verified.
• Posters with “How to connect and pay” placed near sitting areas and entrances.
• Speed limits tested at peak time; adjust if necessary.
• Staff briefed on handling common questions (see FAQ below).

With Pawa, you can simulate payments in a sandbox window during setup to test the full flow without charging real money.

Apartment WiFi renewals without drama

Apartments in Kenya need smooth monthly cycles.

How to run clean renewals with Pawa:

• Offer 30-day plans with 1–3 device options; price gaps should be simple (e.g., +KES 500 per device tier).
• Show renewal date inside the portal; tenants can check status easily.
• Let tenants pay via STK 24/7—no need to call caretakers.
• If someone downgrades or upgrades mid-cycle, Pawa applies the new limits to their next cycle or prorates if you enable that policy.
• For shared family WiFi, bind 2–3 devices to the account to reduce password sharing.

Caretakers can also sell monthly vouchers if you prefer offline collection, then you reconcile weekly.

Reporting that keeps you in control

Use Pawa’s reports to answer these questions every day:

• How much did we collect today per location and per package?
• Which packages are selling the most (KES 10 vs KES 20 vs daily)?
• Which locations are underperforming and need better signage or AP placement?
• How many vouchers were sold and redeemed by each agent?
• What are peak usage times and average session lengths?

Then act:

• Promote the top two packages on posters.
• Adjust speeds if complaints correlate with congestion.
• Move or add APs in dark spots.
• Reward high-performing agents and rotate stock where sales lag.

Export CSVs and share with your accountant or investor. Keep a simple weekly dashboard meeting: revenue, complaints, uptime, plan changes.

Practical buyer’s checklist: choosing a WiFi billing system in Kenya

• Payments
  • M-Pesa STK push on portal
  • Manual Paybill/Till fallback with ref code verification
  • Automated C2B reconciliation and reversal handling
• Access and packages
  • Time, data, and speed-based plans
  • Device limits and session control
  • Captive portal that’s lightweight and mobile-friendly
• Vouchers
  • Batch generation, expiry, and agent tracking
  • One-time use enforcement
• Router integration
  • Clean MikroTik onboarding, RADIUS compatibility
  • Walled garden management and accounting updates
• Reporting
  • Daily totals by location/package/agent
  • CSV export for accounts
• Operations and growth
  • Multi-location management from one dashboard
  • Branding and easy content edits on the portal
  • Support that understands Kenyan connectivity realities

Pawa ticks these boxes and is built around M-Pesa-first customer behavior.

Troubleshooting playbook: fast fixes to common Kenyan issues

• STK delays or timeouts
  • Ask user to check mobile signal and SIM balance.
  • Retry payment or offer a voucher code.
• Portal doesn’t show after connect
  • Instruct user to open a browser and visit any site.
  • Check walled garden and DNS on the MikroTik.
• One user hogs the link
  • Lower their plan’s bandwidth cap from Pawa or create a fair-use tier.
• Dispute about time remaining
  • Look up the session in Pawa; show start time, expiry, and data used.
• Voucher “already used” complaint
  • Confirm the code and redemption time; offer goodwill replacement only if it’s clearly a printing error or agent mishandling.

Growth levers: small changes that raise revenue

• Raise visibility: bigger portal buttons for KES 20 and KES 100 plans.
• Bundle upsell: offer KES 50 for 3 hours prominently during evenings.
• Apartment retention: position two-device plan as the default pick for families.
• Agent motivation: give a small bonus on every 100 vouchers sold.
• Data-light portal: avoid heavy images; faster load equals higher conversion.

Track each tweak in Pawa’s reports to see what moves the needle.

Short FAQ: WiFi billing system Kenya

• Can I run both M-Pesa and vouchers together? Yes. Many Kenyan operators run STK push for self-serve and vouchers for cash buyers at the same location.

• Do I need a public IP from my ISP? Not always. Many setups work behind NAT. Avoid double NAT where possible, and follow Pawa’s onboarding guidance.

• Will the captive portal work on iPhones and low-end Androids? Yes. Pawa’s portal is optimized for common devices. Some users may need to open a browser if the OS doesn’t auto-capture.

• Can I limit to one device for KES 10 but allow two devices for KES 20? Yes. Set device limits per package in Pawa.

• How do I handle M-Pesa reversals? Pawa records reversal events and can end access for reversed transactions. Review daily reports to reconcile.

• What if internet goes down after someone pays? Your policy options include time pause during outage or goodwill credits. Pawa’s session tracking helps you make fair decisions.

• Does this work for apartment monthly subscriptions? Yes. Tenants can pay monthly via STK on the portal; Pawa activates or renews access instantly.

• Can I manage multiple towns and sites from one account? Yes. Create locations in Pawa, assign routers, set packages per site, and view consolidated reports.

Why Pawa WiFi for Kenya

Pawa is a Kenya-first MikroTik hotspot billing SaaS designed to help you sell WiFi like airtime. You get:

• M-Pesa STK on the captive portal for instant access
• Voucher generation and agent tracking
• Packages with time/data/speed limits and device controls
• Simple MikroTik router onboarding and RADIUS
• Customer, payments, and session records for quick support
• Clear reports and automated revenue protection

From KES 10/KES 20 bundles at hotspots to monthly apartment renewals, Pawa gives you the tools to launch fast and grow confidently.

Next steps: get Pawa running in days, not months

• Have a MikroTik router and an internet link ready.
• Create your first three packages (KES 10, KES 20, KES 100) in Pawa.
• Onboard your router using the Pawa RADIUS details and walled garden list.
• Test STK, test vouchers, go live.

Ready to sell WiFi like airtime? WhatsApp Pawa to set up your hotspot now, or start your setup and we’ll guide you step by step.