PPPoE Billing System Kenya: Monthly Subscribers and the Renewal That Has to Happen Every Month
PPPoE billing system Kenya requirements are decided by one fact about the market that operators elsewhere never have to think about: there is no automatic monthly debit. In most of the world, a broadband subscriber gives a card or a bank mandate once and the money arrives on the first of every month without anyone doing anything.
Here, the subscriber pays by M-Pesa, which means every single month every single subscriber has to be prompted, has to act, and has to be reconnected or cut off depending on whether they did. An operator with three hundred PPPoE subscribers is running three hundred small renewals a month, and how that renewal is handled — the reminder before expiry, the prompt on the day, the grace period, the suspension, the reactivation the moment payment lands — determines whether the operator collects ninety-five percent of its billing or seventy.
That is the difference between a business and a struggle, and it is the difference that a billing system exists to make. Everything else PPPoE involves — credentials, bandwidth profiles, RADIUS, the MikroTik server, IP management, monitoring, support — matters and is largely settled engineering.
The renewal cycle is where operators here win or lose. This guide covers the whole model: how PPPoE differs from hotspot commercially, subscriber records and plans, installation and credentials, the authentication chain, automatic activation, the billing cycle from reminder to suspension, arrears and partial payment, plan changes, IP and bandwidth management, resellers, monitoring, support, churn and reporting.
The value of a PPPoE billing system Kenya is a renewal cycle that runs itself, and a PPPoE billing system Kenya that prompts, collects, activates and suspends without the operator touching each subscriber is what makes monthly broadband scalable here — which is why a PPPoE billing system Kenya should be assessed on the renewal cycle before anything else.
Table of Contents
- What PPPoE Is and Why It Suits Fixed Subscribers
- Hotspot and PPPoE Are Different Businesses
- The Kenyan Context
- Who Runs PPPoE Billing
- The Subscriber Record
- Plans and Bandwidth Profiles
- Pricing Monthly Plans
- Fair Use on Monthly Plans
- Installation and Customer Equipment
- Credentials and Authentication
- RADIUS and the MikroTik PPPoE Server
- Automatic Activation on Payment
- The Billing Cycle and Expiry
- Recurring Collection Without Auto-Debit
- Reminders Before Expiry
- Grace Periods
- Suspension and Reactivation
- Arrears and What to Do About Them
- Partial Payment and Top-Ups
- Plan Changes, Upgrades and Proration
- IP Address Management
- Bandwidth Shaping and Queues
- Multi-Site and Reseller Structures
- Router and Network Monitoring
- Support Tickets and Common Faults
- Churn and Retention
- Subscriber Communication
- Running Hotspot and PPPoE Together
- Fibre and Wireless as Access Media
- Reporting for the Operator
- Licensing and Compliance
- Data Protection
- Security
- Costs and Implementation
- Frequently Asked Questions
What PPPoE Is and Why It Suits Fixed Subscribers {#what-pppoe}
PPPoE is the authentication method behind most fixed broadband and understanding why explains the billing model.
A subscriber’s router authenticates to the operator’s network with a username and password.
The session is established once and persists, unlike a hotspot session that a user starts on a portal.
The subscriber’s equipment stays connected without the person doing anything.
Bandwidth, addressing and access are applied to the session by the operator’s system.
It suits a customer who has a fixed location, their own router and an ongoing relationship.
It does not suit a passer-by at a stage buying an hour, which is the hotspot’s customer.
The distinction defines the business, and a PPPoE billing system Kenya manages ongoing subscriptions where a hotspot system manages transient purchases, which means a PPPoE billing system Kenya is built around the monthly cycle rather than the session.
Hotspot and PPPoE Are Different Businesses {#hotspot-vs-pppoe}
Operators frequently run both and should understand how they differ.
Hotspot sells time or data to anyone who connects, paid before use, with no ongoing relationship.
PPPoE sells a monthly service to a known subscriber at a fixed location, with an ongoing relationship and recurring payment.
Hotspot revenue is transactional and variable; PPPoE revenue is recurring and predictable.
Hotspot churn is invisible since customers simply stop buying; PPPoE churn is a subscriber who did not renew.
Hotspot customers need no installation; PPPoE subscribers need equipment at their premises.
Hotspot support is portal and payment problems; PPPoE support is connection and speed problems at a fixed location.
Hotspot works for stages, shops and public spaces; PPPoE works for homes, offices and estates.
The billing system must handle each on its own terms, and a PPPoE billing system Kenya that treats subscribers like hotspot buyers will fail at renewal, while a PPPoE billing system Kenya built for the recurring model handles the cycle that hotspot never has.
The Kenyan Context {#kenyan-context}
Local conditions shape the model substantially.
M-Pesa is how subscribers pay, and it has no standing-order mechanism a small operator can use, which means every renewal is an action the subscriber takes.
That single fact drives the reminder, prompt, grace and suspension design that this guide spends most of its length on.
Monthly income cycles concentrate renewals around month end and the first days of the month.
Estates and apartment buildings are the natural PPPoE market, with fixed subscribers at density.
Small operators run PPPoE alongside hotspot, frequently on the same MikroTik.
Wireless is the common access medium with fibre growing in urban areas.
Subscriber churn to competitors is high where several operators serve an area.
Power interruptions drop subscriber sessions and generate support calls that are not faults.
Licensing for providing broadband applies and should be confirmed, which the compliance section addresses.
A PPPoE billing system Kenya designed for a card-payment market with auto-debit does not fit here, and a PPPoE billing system Kenya built around prompted M-Pesa renewal fits how subscribers actually pay.
Who Runs PPPoE Billing {#who-runs}
The operators are recognisable.
Estate and apartment WiFi operators moving residents from hotspot to monthly plans.
Small wireless ISPs serving neighbourhoods.
Fibre operators serving buildings and estates.
Hotspot operators adding monthly subscribers for regulars who want always-on access.
Resellers operating under a larger provider.
Business and office connectivity providers.
Each has subscribers who expect the connection to simply work every month, and a PPPoE billing system Kenya serves them all with the same cycle, since a PPPoE billing system Kenya that handles a residential estate handles an office block with different plans.
The Subscriber Record {#subscriber-record}
The subscriber is the centre of the system and the record should be complete.
Identity and contact including the phone number that pays.
Location and installation address.
Plan and its bandwidth profile.
PPPoE credentials.
Equipment installed and its identifiers.
Billing cycle dates.
Payment history.
Current status, whether active, in grace, suspended or terminated.
Support history.
Notes.
The phone number that pays matters particularly, since a PPPoE billing system Kenya that knows which number pays for which subscriber matches M-Pesa payments automatically, and a PPPoE billing system Kenya without that link leaves the operator matching transactions to subscribers by hand every month.
Keep it current, since subscribers change numbers and routers.
Plans and Bandwidth Profiles {#plans}
Plans define what the subscriber buys and profiles define what they get.
Speed tiers, typically several from basic to premium.
Monthly, though some operators offer weekly or quarterly.
Bandwidth profile per plan, applied to the session on authentication.
Upload and download limits.
Burst where offered.
Fair use where applied, which the fair use section addresses.
Named clearly so subscribers understand.
Few rather than many, since a portal with three or four plans converts where one with ten confuses.
The profile is enforced automatically, since a PPPoE billing system Kenya that applies the plan’s bandwidth when the session authenticates needs no manual queue configuration per subscriber, and a PPPoE billing system Kenya that upgrades a subscriber’s speed the moment they pay for the higher plan has removed a support ticket.
Pricing Monthly Plans {#pricing}
Monthly pricing is the operator’s decision and the constraints are real.
Cost basis including upstream bandwidth per subscriber at realistic contention, which the ISP start-up guide develops.
Market comparison, since subscribers know what competitors charge.
Mobile data as the alternative every subscriber has.
Price points that suit M-Pesa payment, since round figures transact more easily.
Tier differentials that reflect a difference subscribers can feel.
Installation fee and whether it is charged or waived.
Equipment cost and whether it is sold, rented or provided.
Model the net, since a PPPoE billing system Kenya operator who priced without deducting transaction charges and upstream cost may be below margin, and a PPPoE billing system Kenya that reports revenue per subscriber against cost per subscriber shows whether each plan earns.
Do not race competitors to the bottom, since reliability holds subscribers where price alone does not.
Fair Use on Monthly Plans {#fair-use}
Unlimited monthly plans need a fair use position.
A minority of subscribers consume disproportionately.
Speed-tiered plans manage it by limiting rate rather than volume.
Volume thresholds with reduced speed beyond them are an alternative.
Transparency at signup, since a subscriber who discovers a throttle they were not told about will leave.
Consistent application.
Monitoring consumption per subscriber to see who is affected.
Upselling heavy users to higher tiers rather than punishing them.
State the policy, since a PPPoE billing system Kenya that shows the fair use terms on the plan page has been honest, and a PPPoE billing system Kenya that tracks consumption per subscriber can apply the policy where it says it will rather than arbitrarily.
Installation and Customer Equipment {#installation}
PPPoE subscribers need equipment at their premises and installation is a real operation.
A router capable of PPPoE at the subscriber’s location.
Wireless subscriber unit or fibre terminal depending on the access medium.
Configuration of PPPoE credentials on the router.
Testing before the installer leaves.
Equipment ownership, whether sold, rented or provided against the subscription.
Recovery on termination.
Records of what was installed where, with serial numbers.
The subscriber’s own WiFi behind the router, which is their concern and generates support calls that are not the operator’s fault, as the coverage article explains.
Record it against the subscriber, since a PPPoE billing system Kenya that holds the installed equipment against the subscriber record knows what to recover when they leave, and a PPPoE billing system Kenya without it loses routers at every departure.
Credentials and Authentication {#credentials}
The username and password are the subscriber’s identity on the network.
Generated per subscriber, unique.
Configured on the subscriber’s router at installation.
Authenticated on every session establishment.
Tied to the subscriber’s plan and status.
Changeable if compromised.
Not shared between subscribers, since shared credentials mean one payment serves two households.
Session limits so one credential cannot establish multiple sessions from different locations.
The credential is where billing meets the network, since a PPPoE billing system Kenya that knows a credential’s status can accept or reject the session accordingly, and a PPPoE billing system Kenya that rejects a suspended subscriber’s authentication has enforced non-payment without anyone touching the router.
RADIUS and the MikroTik PPPoE Server {#radius-mikrotik}
The technical chain connects the billing system to the network.
The MikroTik runs the PPPoE server that subscribers’ routers connect to.
RADIUS authenticates each session against the billing system’s subscriber record.
The billing system returns the plan’s bandwidth profile and any other attributes.
Accounting reports session data back for consumption tracking.
Disconnect messages terminate sessions when a subscriber is suspended.
Reachability between the MikroTik and the billing system is essential, and behaviour when it fails should be defined, as the MikroTik configuration article discusses.
The chain is standard and it must be configured correctly, since a PPPoE billing system Kenya where RADIUS accounting is not flowing cannot track consumption or enforce fair use, and a PPPoE billing system Kenya where disconnect messages are blocked by the firewall cannot suspend a subscriber until their session happens to drop.
Test authentication, accounting and disconnect explicitly before going live.
Automatic Activation on Payment {#activation}
Activation on payment is the core automation and it removes the operator from every renewal.
The subscriber pays by M-Pesa.
The payment is matched to the subscriber by phone number or reference.
The subscriber’s expiry is extended by the plan period.
If suspended, the subscriber is reactivated and their session permitted.
Confirmation is sent to the subscriber.
No operator action.
Seconds rather than hours, since a subscriber who paid and waits for someone to reconnect them is a support call and a frustrated customer.
This is what makes hundreds of subscribers manageable, since a PPPoE billing system Kenya that activates automatically handles three hundred renewals with no manual work, and a PPPoE billing system Kenya that requires the operator to confirm each payment and reconnect each subscriber caps the business at what one person can process.
Handle the failure cases, including unmatched payments and payments for the wrong amount, which the recurring collection section addresses.
The Billing Cycle and Expiry {#billing-cycle}
Every subscriber has a cycle and the system tracks it.
Start date from activation.
Expiry date at the end of the paid period.
Renewal extending the expiry.
Anniversary billing, where each subscriber’s cycle runs from their own start date.
Fixed-date billing, where all subscribers renew on the same day of the month.
Anniversary spreads renewals through the month; fixed-date concentrates them.
Fixed-date suits estates where residents pay with rent; anniversary suits mixed subscriber bases.
Expiry is the trigger for everything that follows, and a PPPoE billing system Kenya that knows every subscriber’s expiry drives reminders, grace and suspension from it, while a PPPoE billing system Kenya tracking expiry in a spreadsheet will miss some.
Choose the cycle deliberately and be consistent.
Recurring Collection Without Auto-Debit {#recurring-collection}
This section is the heart of the guide because it is where the local market differs.
There is no mechanism for a small operator to pull a monthly payment from a subscriber’s M-Pesa automatically.
Every renewal requires the subscriber to pay.
The operator’s job is to make that as easy and as timely as possible.
STK push on or before expiry, prompting the subscriber to confirm a payment on their phone, which is the closest thing to auto-debit available and it still requires a tap.
PayBill or Till with a reference the subscriber uses, which works and produces reference errors.
Payment links sent by message.
Matching payments to subscribers by the paying phone number, which removes most reference problems.
Unmatched payments handled promptly, since a subscriber who paid and was not activated is the worst outcome.
Wrong amounts handled, including underpayment and overpayment.
The design that works is reminder, prompt, match, activate, and a PPPoE billing system Kenya that pushes a payment prompt to each subscriber’s phone at expiry with one tap to confirm collects far more than one that waits for subscribers to remember, since a PPPoE billing system Kenya that made renewal a single confirmation has removed the friction that causes lapses.
Reminders Before Expiry {#reminders}
Reminders prevent lapses and they should be automatic.
A message several days before expiry.
A message on the day.
A message when suspended.
Each with the amount, the plan and how to pay.
Sent automatically from the subscriber’s expiry date.
Courteous and brief.
Not excessive, since daily messages are muted.
Delivery confirmation where the channel supports it.
Most lapses are forgetfulness rather than refusal, and a PPPoE billing system Kenya that reminds every subscriber automatically three days before expiry will see most renew before the day, while a PPPoE billing system Kenya without reminders will suspend subscribers who would have paid if asked.
Measure the effect, since collection rate before and after reminders shows what they achieve.
Grace Periods {#grace}
Grace is the time between expiry and suspension and it is a commercial decision.
Zero grace suspends at expiry, which is strict and generates immediate calls.
A day or two of grace absorbs the subscriber who pays on the second.
Longer grace becomes free service.
Grace with reduced speed is a middle position that keeps the subscriber connected enough to pay.
Consistent policy, since grace applied to some and not others produces complaints.
Communicated, since a subscriber who knows they have two days plans around it.
Grace is also cash flow, since an operator whose subscribers all renew two days late has moved its income two days.
Set it deliberately, since a PPPoE billing system Kenya with a defined grace period applied automatically is consistent, and a PPPoE billing system Kenya where the operator decides per subscriber whether to cut them off has a policy that depends on mood.
Suspension and Reactivation {#suspension}
Suspension is the enforcement and reactivation is the recovery.
At the end of grace, the subscriber’s authentication is rejected and any active session terminated.
The subscriber’s portal or landing page should explain why and how to pay, since a subscriber who simply loses connectivity calls support.
Redirect to a payment page where the setup allows, which turns suspension into a renewal prompt.
Reactivation the moment payment lands, automatically.
Session re-established when the subscriber’s router reconnects.
Confirmation to the subscriber.
No manual step, since a PPPoE billing system Kenya that suspends and reactivates automatically runs the enforcement without the operator, and a PPPoE billing system Kenya that requires someone to re-enable each paying subscriber will have subscribers waiting for a person who is asleep.
The redirect page is what turns a cut-off into a payment, since a subscriber who sees “your plan expired, pay here” pays and one who sees nothing calls or leaves.
Arrears and What to Do About Them {#arrears}
PPPoE arrears are different from hotspot because the subscriber is known and the relationship is ongoing.
A suspended subscriber who does not renew for a period.
Whether the operator carries a balance or treats each month as new.
Prepaid models carry no arrears since service stops at expiry; postpaid models do.
Prepaid is strongly preferable here, since a PPPoE billing system Kenya operating prepaid has no receivables and no collection burden, and the suspension is the collection mechanism.
Where postpaid exists, ageing and follow-up as any receivables.
Reconnection fees where the operator charges them, stated in advance.
Termination after a defined period of non-renewal.
Equipment recovery on termination.
Win-back contact to lapsed subscribers, since a subscriber who lapsed may return if asked.
Track lapsed subscribers, since a PPPoE billing system Kenya that reports who has not renewed in thirty days gives the operator a list to contact, and lapsed subscribers are cheaper to recover than new ones are to acquire.
Partial Payment and Top-Ups {#partial-payment}
Subscribers pay the wrong amount and the system should handle it.
Underpayment, where the subscriber paid less than the plan.
Overpayment.
Payment for a different plan than subscribed.
Options include crediting the balance, activating a shorter period proportionate to the amount, or holding the payment until topped up.
Proportionate activation is subscriber-friendly, since a PPPoE billing system Kenya that activates fifteen days for half a month’s payment keeps the subscriber connected and paying, and a PPPoE billing system Kenya that rejects the payment leaves them disconnected and confused.
Balance tracking so overpayments carry forward.
Top-up flows so a subscriber can add to a partial payment.
Clear communication of what a payment did.
Define the rules and apply them automatically.
Plan Changes, Upgrades and Proration {#plan-changes}
Subscribers move between plans and the system should make it easy.
Upgrade mid-cycle, applied immediately with the difference charged or the cycle adjusted.
Downgrade at the next renewal, or immediately with credit.
Proration rules stated.
Bandwidth profile changed on the live session or at next authentication.
Confirmation to the subscriber.
Upgrades are revenue, and a PPPoE billing system Kenya that lets a subscriber upgrade from the portal and applies the new speed immediately has captured revenue that a phone call to the operator and a manual change would have delayed, while a PPPoE billing system Kenya with self-service plan changes has removed a category of support ticket.
Keep the rules simple enough to explain.
IP Address Management {#ip-management}
Every PPPoE session needs an address and the pool needs managing.
Address pools sized for the subscriber count with headroom.
Dynamic assignment per session for most subscribers.
Static assignment for subscribers who need it, including businesses.
Private addressing behind the operator’s NAT for most residential subscribers.
Public addresses where required, at a cost.
Pool exhaustion presenting as subscribers unable to connect.
Record which subscriber has which address at which time, since abuse reports and lawful requests refer to addresses.
Plan the pool, since a PPPoE billing system Kenya that manages address assignment per plan handles static and dynamic subscribers without manual configuration, and a PPPoE billing system Kenya whose pool was sized for last year’s subscriber count will produce mysterious connection failures when it fills.
Bandwidth Shaping and Queues {#queues}
Each session’s bandwidth is enforced by queues the system creates.
Per-subscriber queues from the plan’s profile.
Applied on authentication, removed on disconnect.
Burst configuration where used.
Aggregate shaping on the uplink.
Queue type affecting fairness under contention.
Priority for business subscribers where offered.
Automatic creation matters, since a PPPoE billing system Kenya that creates the queue from the RADIUS attributes needs no per-subscriber router configuration, and a PPPoE billing system Kenya that leaves queues to manual setup will have subscribers on the wrong speed.
Monitor utilisation at peak, since an oversold uplink degrades every subscriber regardless of their plan.
Multi-Site and Reseller Structures {#resellers}
Operators grow across sites and through resellers.
Multiple MikroTiks at different locations under one billing system.
Subscribers assigned to a site.
Resellers operating their own subscriber base under the operator’s platform.
Reseller pricing and revenue share.
Reseller visibility limited to their own subscribers.
Consolidated reporting for the operator.
Settlement to resellers documented.
The hotspot billing article covers reseller structures and the same applies, since a PPPoE billing system Kenya with multi-tenant capability lets a reseller manage their subscribers while the operator sees the whole, and a PPPoE billing system Kenya that calculates reseller revenue share automatically prevents the settlement dispute.
Router and Network Monitoring {#monitoring}
Subscribers notice outages before the operator does unless monitoring exists.
MikroTik reachability and health.
Active session count per router.
Uplink utilisation.
Authentication failures, which may indicate a RADIUS problem or a mass credential issue.
Session drops, which may indicate power or upstream problems.
Alerting to someone who acts.
Per-site views for multi-site operators.
The hotspot billing article’s monitoring points apply, and a PPPoE billing system Kenya that shows router health and session counts in the same dashboard as billing lets the operator see that a site’s sessions dropped to zero at the moment its router went offline, while a PPPoE billing system Kenya without monitoring learns about the outage from the support queue.
Support Tickets and Common Faults {#support}
PPPoE support has recognisable patterns.
Cannot connect, which is usually credentials, suspension or the subscriber’s router.
Slow speed, which is usually the subscriber’s WiFi, the uplink at peak or the wrong profile.
Paid but not activated, which is a matching failure and the most urgent ticket.
Session dropping, which is usually power or a marginal wireless link.
Router offline at the subscriber’s premises.
Ticketing so faults are recorded, assigned and closed.
Subscriber lookup so the agent sees status, payment and history immediately.
Categorisation so patterns are visible.
The paid-but-not-activated ticket should never exist, and a PPPoE billing system Kenya with reliable payment matching makes it rare, while a PPPoE billing system Kenya where the agent can see the subscriber’s status and last payment in one screen resolves most of the rest in a minute.
Track causes, since a rising number of “slow speed” tickets at one site is an uplink problem.
Churn and Retention {#churn}
PPPoE churn is visible and it determines whether growth is real.
A subscriber who did not renew is churn.
Causes include price, reliability, moving, a competitor and poor support.
Measure it monthly as a proportion of the base.
Identify lapsed subscribers promptly.
Win-back contact.
Reliability is the largest controllable factor, since subscribers leave operators who cannot keep them connected.
Support responsiveness is the second.
Track it, since a PPPoE billing system Kenya reporting churn rate shows whether the operator is building a base or replacing one, and a PPPoE billing system Kenya that lists who lapsed this month gives the operator someone to call.
The ISP start-up guide develops churn economics.
Subscriber Communication {#communication}
Communication drives renewal and retention.
Reminders and payment prompts.
Confirmation of payment and activation.
Outage notices, since subscribers told about a problem are patient.
Plan and price changes with notice.
Support responses.
Not marketing to subscribers who did not consent to it.
Automated where the event is standard, personal where the situation is not.
A subscriber who received a reminder, paid with one tap and got a confirmation has had a renewal that took thirty seconds, and a PPPoE billing system Kenya that does that every month for every subscriber is running the business, while a PPPoE billing system Kenya that leaves communication to the operator’s phone will miss subscribers every month.
Notify during outages, since silence loses subscribers that a message would have kept.
Running Hotspot and PPPoE Together {#both-models}
Most operators run both and the system should hold both.
Hotspot for transient users and PPPoE for fixed subscribers on the same infrastructure.
Different portals, different payment flows, different records.
Migration path from hotspot to PPPoE for regulars, since a customer buying daily hotspot packages every day is a monthly subscriber who has not been offered the plan.
Combined reporting.
One M-Pesa integration serving both.
The same MikroTik running both services.
Offer the migration, since a PPPoE billing system Kenya that identifies hotspot customers buying daily for a month can offer them a monthly plan at a saving, and a PPPoE billing system Kenya that converts them has turned transactional revenue into recurring revenue.
Fibre and Wireless as Access Media {#access-media}
PPPoE runs over either and the billing does not care.
Wireless subscriber units connecting to a base station, then PPPoE to the MikroTik.
Fibre terminals at the premises, then PPPoE.
The authentication and billing chain is identical.
Installation and support differ, since wireless has line of sight and interference issues while fibre has cable and terminal issues.
Fibre operators may add ONU provisioning through SmartOLT-style workflows alongside billing.
Mixed networks run both.
The billing system should be indifferent, since a PPPoE billing system Kenya that manages subscribers regardless of how they reach the network serves a mixed operator, and a PPPoE billing system Kenya tied to one medium constrains growth.
The fibre-versus-wireless article covers the medium choice from the subscriber’s side.
Reporting for the Operator {#reporting}
A focused set runs a subscription business.
Active subscribers and trend.
Revenue by plan and by month.
Collection rate, being renewals against expiries.
Subscribers in grace and suspended.
Churn rate and lapsed subscribers.
New subscribers.
Revenue per subscriber against cost per subscriber.
Payments unmatched.
Router and session health.
Support ticket volume and causes.
Collection rate and churn are the two that matter, since a PPPoE billing system Kenya reporting that ninety-four percent of expiries renewed and three percent churned has described a healthy business in two numbers, and a PPPoE billing system Kenya that surfaces unmatched payments daily prevents the paid-but-not-activated ticket.
Mobile access, since operators are frequently on site.
Licensing and Compliance {#compliance}
Providing broadband is regulated and the position should be established.
Licensing requirements for providing communications services are administered by the Communications Authority of Kenya, and which category applies depends on what the operator does and at what scale.
Reselling under a licensed provider may differ from operating independently.
Requirements, process and fees should be confirmed with the Authority directly rather than assumed.
Consumer protection considerations may apply to advertised speeds and terms.
Records including which subscriber held which address at which time may be required.
Tax obligations including any fiscal invoicing requirements.
Establish it before scaling, since a PPPoE billing system Kenya operator with hundreds of subscribers and no established regulatory position has an exposure, and a PPPoE billing system Kenya can keep the records the requirements specify but cannot determine what they are.
Take qualified advice alongside the Authority’s guidance.
Data Protection {#data-protection}
Subscriber records are personal data and the Data Protection Act applies.
Identity, contact, address, payment history and session records.
Session records show when a household was online, which is private.
Address assignment records link activity to a subscriber.
Access restricted by role, and a reseller sees only their own subscribers.
Retention defined, with any regulatory retention requirements confirmed.
Marketing to subscribers requires consent beyond the service relationship.
Never disclose a subscriber’s payment position to neighbours or landlords.
Security of the record.
Confirm obligations with qualified advice, and a PPPoE billing system Kenya should be configured to whatever position that establishes, since a PPPoE billing system Kenya holding hundreds of households’ connection and payment records has obligations the operator should understand.
Security {#security}
The billing system controls access and revenue and it should be protected.
Administrative access restricted with strong authentication.
Default credentials changed on every router.
RADIUS shared secrets managed.
Management network separated from subscriber traffic.
Subscriber isolation so households cannot see each other.
Payment endpoint verification so fraudulent confirmations cannot activate subscribers.
Firmware currency on routers.
Audit logging of administrative actions including manual activations.
The MikroTik configuration article covers hardening, and a PPPoE billing system Kenya where an administrator account is compromised allows free activation for anyone, which is why a PPPoE billing system Kenya should log every manual activation with who did it.
Costs and Implementation {#costs}
Pricing models vary and the renewal automation is what to buy.
Subscription tiers by router and subscriber count, commonly from around KES 1,500 monthly for a small operation to more for larger ones.
Collection fees where the platform collects payments, versus using the operator’s own PayBill or Till.
Transaction charges on M-Pesa, which are separate and affect net revenue per subscriber.
MikroTik hardware.
Subscriber equipment per installation.
Implementation should begin with the subscriber record and plans, since a PPPoE billing system Kenya cannot renew subscribers it does not have on record with correct expiry dates.
Configure the RADIUS chain and test authentication, accounting and disconnect.
Configure reminders, grace and suspension before migrating subscribers.
Migrate subscribers with accurate expiry dates, since a wrong date suspends a paying subscriber.
Test the payment flow including unmatched and partial payments.
Weigh cost against collection rate, since a PPPoE billing system Kenya that raises collection from seventy-five to ninety-five percent has paid for itself many times over, and the difference is the renewal cycle running itself.
Frequently Asked Questions {#faqs}
How is PPPoE billing different from hotspot billing?
Hotspot sells time or data to anyone who connects, paid before use, with no ongoing relationship. PPPoE sells a monthly service to a known subscriber at a fixed location with equipment installed and recurring payment. The revenue is predictable, churn is visible, and the whole system is built around a monthly cycle rather than a session.
Why is the renewal cycle so important here?
Because there is no auto-debit. A subscriber elsewhere gives a card once and pays automatically; here every subscriber has to act every month. The reminder before expiry, the STK prompt on the day, the grace period, the suspension and the automatic reactivation the moment payment lands are what determine whether an operator collects ninety-five percent of billing or seventy.
What is the closest thing to automatic payment?
An STK push to the subscriber’s phone at expiry, so renewal is a single tap to confirm. Combined with a reminder a few days before and automatic matching of the payment by the subscriber’s phone number, it removes most of the friction that causes lapses. It still requires the subscriber to act, which is why grace and reactivation matter.
Should we run prepaid or postpaid?
Prepaid, strongly. Service stops at expiry, so there are no receivables and no collection burden — suspension is the collection mechanism. Postpaid means funding subscribers who have not paid and chasing them afterwards. Use a short grace period to absorb the subscriber who pays on the second.
A subscriber paid but is still cut off. What went wrong?
Payment matching, almost always — a wrong reference or a payment from a number not on the record. This is the most urgent ticket and it should be rare. Match by paying phone number rather than reference where possible, surface unmatched payments daily, and let the agent see status and last payment in one screen.
What about the subscriber’s WiFi being slow in the bedroom?
That is their router’s coverage, not your connection, and it generates a large share of support calls. Test at the router: if it is fine there and poor elsewhere, it is in-building coverage. The WiFi coverage article covers it, and a link to it in your support responses saves both parties time.
Do we need a licence?
Confirm it with the Communications Authority directly and with qualified advice, since the category depends on what you do and at what scale, and reselling under a licensed provider may differ from operating independently. Establish it before scaling — a billing system keeps the records the requirements specify but cannot determine what they are.
What two numbers tell us the business is healthy?
Collection rate — renewals against expiries — and churn rate. A PPPoE billing system Kenya reporting that ninety-four percent of expiries renewed and three percent of the base churned has described a healthy subscription business in two figures, and tracking both monthly shows whether you are building a base or replacing one.