Vouchers, mobile money and the routers that carry the traffic — one system,
Nothing here is theoretical - this is the exact sequence the system performs, in order, for every single person who connects.
The router hands out an address and redirects anything unpaid to the portal. WMS never has to guess who arrived - the router tells it.
Three ways in, one outcome: a voucher code, a customer sign-in, or a package bought on the spot with mobile money.
The USSD prompt goes to the payer's phone. Access is granted when the provider confirms the payment - not when the request was sent.
A hotspot user and a queue are created on the MikroTik with the speed, data cap and device count that package was sold under.
Session time, download, upload and daily totals come back from the router and land against the customer, the voucher and the router.
Sized by how much of your week they take, not by how they fit a grid.
Generate one card or two thousand. Each voucher carries a snapshot of the package it was sold under, so editing a package tomorrow never changes what somebody already paid for.
Several MikroTik routers and their access points, each with its own credentials stored encrypted. Status, CPU, memory, uptime and interfaces are read from RouterOS itself — when a router cannot be reached the system says so and raises an alert instead of filling the gap with a number it made up.
Accounts, devices, sessions, usage and payment history in one profile. Suspend, activate or investigate without leaving the page.
Price, duration, data cap, speeds and how many devices may share it. Nothing hard-coded — build the plans your market actually buys.
A provider layer with SonicPesa built in for M-Pesa, Tigo Pesa, Airtel Money and Halopesa — plus a demo provider for testing.
Who is online, on which device, through which access point, using how much — with the disconnect button on the same screen.
Revenue, customer growth, voucher performance and network load. On screen, printable, CSV ready, over any date range.
Download, upload, connected time and daily totals — per customer, per voucher and per router.
Four roles out of the box, each a set of permissions checked on the server rather than hidden in the interface — and a log of who did what, kept whether or not anyone is watching.
What you configure is exactly what the customer sees — this list comes out of the same table the portal reads.
A voucher is a package that has already been paid for. It carries its own speed, cap, expiry and device count, so an agent at a counter with no connection can still hand one over and be sure of what they sold.
Redeem a codeRouter commands live in one service. Adding or swapping equipment means one provider class, not forty pages.
Every screen asks the same service, and the service asks the provider.
You are holding other people's money and other people's traffic. These are the defaults, not the upgrades.
Customers get online in three taps. Staff get the control centre, with everything above it in one place.