ISP Billing System Kenya: Common Problems and How to Solve Them

Billing Problems Cost You Money Every Day

When your ISP billing system isn't working properly, the effects are immediate: subscribers get free internet, revenue is miscounted, and you spend hours doing manual fixes. Here are the most common problems Kenyan ISPs face and how to address them.

Problem 1: M-Pesa Payments Not Matching Subscribers

Cause: The subscriber used the wrong account reference, or the M-Pesa callback failed to reach your billing system.

Solution: Use STK Push instead of manual Paybill entry — this eliminates wrong account references entirely. Ensure your billing system has a payment retry queue for failed callbacks.

Problem 2: Subscribers Not Reconnecting After Payment

Cause: MikroTik API connection failure, or the billing system didn't receive the M-Pesa callback in time.

Solution: Ensure your billing system has a stable connection to your MikroTik router. Monitor API connectivity. A good system will alert you when the router connection drops.

Problem 3: Double Billing

Cause: Duplicate M-Pesa callbacks being processed twice.

Solution: Your billing system must have idempotency checks — detecting and ignoring duplicate transaction IDs from Safaricom.

Problem 4: Subscribers Not Getting Disconnected at Expiry

Cause: The billing system's scheduler is not running, or MikroTik API is unreachable at expiry time.

Solution: Use a cloud billing system with guaranteed uptime. On-premises systems that go offline at night fail to run expiry jobs.

Problem 5: Revenue Reports Don't Match M-Pesa Statements

Cause: Refunds, failed transactions, or manual payments not captured in the billing system.

Solution: Ensure all payment channels flow through the billing system. Avoid accepting manual payments outside the system.

Jasiyo addresses all of these problems with built-in retry logic, duplicate detection, and 24/7 cloud uptime.