Invoice, payment and access, in that order
Every change stays attached to the subscriber record. Package, invoice, payment and the RADIUS reply are one loop, so the account and the session never disagree about what has been paid for.
- Package
- Home 5 Mbps
- Attached to
- Turi-01
- Renews
- 9 Nov
- Renew automatically
- Send SMS receipt
- Suspend when overdue
-
Invoice INV-8412 paid KES 2,400 · M-Pesa
-
Expiry moved 9 Oct → 9 Nov
-
Rate limit written Mikrotik-Rate-Limit 10M/10M
-
Session restored 10.40.12.7 on Turi-01
-
Receipt sent SMS to +254 7•• •••142
Sell the package the customer can actually use
Speed, data cap and validity belong to the package, not to whoever remembers to type them into the router. The invoice and the RADIUS reply read the same numbers, so a renewal cannot half-happen.
Packages that price themselves
Speed, cap and validity live on the package, with one price the invoice and the reply both use.
Learn moreRenewals that arrive on time
The next invoice is raised before the session would have dropped, not after the customer calls to ask.
Learn moreAccess that follows payment
Expiry and rate limit are answered from the account, so a cleared payment restores access by itself.
Learn moreHow it works
Four steps, and the system carries the paperwork between them rather than a person.
-
1. The subscriber exists
Name, package and the router they sit behind. One record, and no second copy in a spreadsheet.
-
2. The invoice is raised
On the renewal date, at the package price, with anything unpaid carried forward onto the same account.
-
3. The payment clears
Paybill, cash at the counter or a bank transfer, matched to the account number the customer was given.
-
4. The reply is written
Expiry and rate limit are stored against the credentials, and the next session picks them up without a restart.
Setup guides
The parts of the platform this model depends on, documented on their own.
PPPoE subscriptions
Monthly broadband subscribers authenticated by account number against their subscription.
Routers and network accessMikroTik provisioning
Register a router and it receives a tunnel and identity without manual configuration.
Billing and paymentsM-Pesa collections
Take payment by STK push or paybill reference without leaving the platform.
Common questions
Does the customer have to wait for a renewal to be processed?
No. Access is decided from the account, so a payment that clears at 21:42 restores the session at 21:42. There is no nightly job that has to run first.
What happens to a subscriber who pays late?
The expiry date passes and the next RADIUS reply refuses the credentials. When the payment lands, the expiry moves forward from the date that lapsed, not from the date of payment, unless you configure it otherwise.
Can one customer have several packages?
Yes. A subscriber can hold more than one subscription, each with its own package, credentials and renewal date, and each invoiced separately.
Put your subscribers on it this week
Start with the network you already have. Add a router, publish what you sell, and let the payments and reconnections look after themselves.