KES billing and network operations for Kenyan ISPs
Collect customer payments through M-Pesa, Pesapal or Flutterwave, send local SMS through three Kenyan providers, and operate FTTH or wireless networks from one platform.
M-Pesa, Pesapal & Flutterwave
Africa’s Talking, TextSMS & Advanta
KES invoices & payment reconciliation
Billing, messaging and network state
Verify every provider event before the customer ledger and access workflow move forward.
- CurrencyKES billing and receipts
- AccessRADIUS · MikroTik · OLT
- MapsWoosmap default · Google optional
KESLocal-currency billing
3Payment gateways
3SMS gateways
MixedFTTH & WISP operations
Explore by market
Built for the operating reality
Local collections, messaging and access operations should share one record.
Kenyan ISP teams need billing, mobile-money confirmation, subscriber messages and network access to share one operating record. ISPbills connects those steps while keeping merchant credentials and provider approval under the ISP’s control.
Collections arrive through different rails
M-Pesa, card and bank-payment events need verified callbacks, clear references and a consistent subscriber-ledger update.
Message delivery depends on local approval
Sender IDs, API credentials and delivery routes differ across providers and must be tested before automated notices are enabled.
Billing and network teams lose context
FTTH and wireless faults are harder to resolve when payment, RADIUS, router, OLT, ONU and map data live in separate tools.
🇰🇪 Kenya
From KES invoice to verified payment and service state.
Build one controlled path from a KES invoice through an approved payment provider, subscriber notification and verified access-state update.
01 · Bill
Create the KES billing cycle
Configure packages, due dates, balances and invoice records for the Kenyan operation.
02 · Notify
Use an approved Kenyan SMS route
Send bills, reminders and confirmations through Africa’s Talking, TextSMS Kenya or Advanta SMS.
03 · Collect
Verify the provider event
Accept M-Pesa STK Push, Pesapal or Flutterwave payments only after the provider callback and transaction details are verified.
04 · Operate
Keep service state aligned
Use the confirmed account state alongside RADIUS, MikroTik, OLT, ONU and support workflows.
Operational capabilities
Kenyan payment and messaging rails connected to ISP operations.
Connect KES invoices, M-Pesa, Pesapal or Flutterwave payments, Kenyan SMS delivery and subscriber access in one traceable workflow.
KES subscriber billing
Create recurring invoices, balances, receipts and collection reports in Kenyan shillings.
Three Kenyan payment gateways
Configure M-Pesa Daraja STK Push, Pesapal hosted checkout or Flutterwave checkout for customer payments.
Three Kenyan SMS gateways
Send operational messages through Africa’s Talking, TextSMS Kenya or Advanta SMS using your own provider account.
Subscriber access control
Coordinate account state with PPPoE, Hotspot, MikroTik and FreeRADIUS workflows.
Fiber and wireless operations
Manage supported routers, OLTs and ONUs across FTTH, WISP and mixed deployments.
GIS planning and field visibility
Map subscribers and network assets with Woosmap by default or a group-owned Google Maps key.
Market readiness
Validate the Kenyan collection-to-access path before launch
Confirm the exact merchant product, settlement path, callback, sender approval and device behavior available to your organization before launch.
Payment product and settlement
Confirm live API approval, callback URLs, KES settlement, reversals and the exact merchant product enabled by M-Pesa, Pesapal or Flutterwave.
SMS sender and consent
Register the required sender identity, test Kenyan mobile-number formatting and confirm consent, template and delivery-report requirements.
Tax and invoice review
Have a qualified Kenyan adviser verify invoice fields, tax treatment, reporting and record-retention obligations for the operating entity.
Network and map readiness
Inventory device models and firmware, verify access workflows, and replace the shared Woosmap trial key with a group-owned key within seven days.
Important: ISPbills provides configurable software workflows, not tax, telecom or legal advice. Your team remains responsible for confirming current requirements with its providers and local advisers.
Controlled rollout
Prove one Kenyan customer journey end to end
Test successful, pending, failed and reversed payments plus SMS delivery and access changes with representative subscribers and network equipment.
- 01
Choose and approve providers
Confirm the merchant or messaging product, settlement account, sender identity, credentials and commercial approval for the ISP.
- 02
Test the complete customer journey
Use sandbox credentials where offered, then verify payment callbacks, exceptions, SMS delivery and ledger reconciliation with controlled records.
- 03
Connect access and field operations
Validate RADIUS, MikroTik, OLT and ONU actions, then set accurate GIS coordinates before expanding the rollout.
Operational fit
Keep every KES payment, message and access decision traceable.
Give billing, support and NOC teams the same view of the KES balance, provider event, subscriber message and current service state.
KESLocal-currency billing
3Payment gateways
3SMS gateways
MixedFTTH & WISP operations
Questions from ISP teams
Kenya payment, messaging and network questions
Direct answers about M-Pesa, Pesapal, Flutterwave, local SMS providers, GIS and access operations.
Which Kenyan payment gateways does ISPbills support?
Kenyan group administrators can configure M-Pesa Daraja STK Push, Pesapal and Flutterwave. Each gateway requires an approved merchant account and its own credentials.
Which Kenyan SMS providers can I use?
Africa’s Talking, TextSMS Kenya and Advanta SMS are available. Use an approved sender identity and test delivery with your own provider account before enabling automation.
Can payments update subscriber service automatically?
Supported payment workflows verify provider results before posting a successful customer payment. Test successful, failed, pending and reversed cases before connecting broad access automation.
Does GIS require Google Maps?
No. Woosmap is the default. A shared platform key is available for the first seven days; the group administrator must then save an organization-owned Woosmap key or explicitly switch to Google Maps and provide a Google key.
More deployment models
Explore other ISP solutions
By region
Bangladesh ISPs
Bill subscribers in BDT, reconcile bKash, Nagad and local gateway payments, and operate MikroTik, RADIUS and fiber networks from one platform.
Explore solution →
By region
India ISPs
Automate INR billing, UPI and gateway collections, subscriber messaging and network operations without maintaining separate systems.
Explore solution →
By region
Pakistan ISPs
Run PKR billing, collect through Easypaisa, JazzCash and HBL Konnect, and automate subscriber notifications and access-network operations.
Explore solution →Start running your ISP on a platform your team will actually use
Start a free trial today — no credit card, no commitment.