From M-Pesa to Reconnection: How Kenyan ISPs Process Payments Behind the Scenes
Here's the full chain, step by step, in a properly automated Kenyan ISP setup:
1. Invoice generated automatically on the customer's billing cycle — no staff involvement.
2. Customer pays via M-Pesa — Paybill with a unique account number (best for monthly PPPoE/static IP subscribers) or Till Number (better for hotspot vouchers, since there's no account number to remember).
3. Safaricom confirms the transaction, pushed back via the Daraja API within seconds if the billing platform is properly integrated.
4. The payment is matched to the customer account automatically. This is where manual setups fall apart — someone has to read a statement and guess which "JOHN K 254712…" line belongs to which customer. A well-built system matches this instantly by account number or phone number, and flags true mismatches (a typo, a payment from someone else's phone) to an exceptions screen instead of derailing the whole day's reconciliation.
5. The router is instructed to reconnect the customer — and this is the step that reveals whether you're using a billing tool or an ISP management platform. A pure billing tool stops at "payment recorded" and expects you (or a separate RADIUS system) to handle the network side. A platform like Beam, where customer billing and MikroTik router control live in the same system, triggers the reconnection itself — no second login, no second tool, no delay waiting for someone to notice the payment came in.
6. The customer gets a confirmation SMS, closing the loop without a "did my payment go through?" phone call.
Done right, steps 2 through 6 take under a minute, with zero staff involvement. That gap — between a system that just tracks the money and one that actually acts on it — is the difference between an ISP that runs itself and one where the owner is still the bottleneck at 500 customers. See How Do Internet Service Providers Handle Customer Payments? for the bigger picture, or sign up and try Beam free to see this exact flow — M-Pesa payment to reconnected customer — running on your own router.