Hotspot billing software
A captive portal in your own colours, time passes the router enforces rather than trusts, vouchers you can print by the hundred, and a guest who pays from the sign-in page with the wallet already on their phone — for a café, a hostel, a market or a whole bazaar.
A guest, from arrival to online
The captive portal carries your name, your logo and your own photographs — not a router's default login box. The pictures are yours to change from the panel, without a deploy.
A phone number and an SMS code, or the code printed on a voucher. A voucher is both payment and proof of who they are, so a card-only guest never needs an account at all.
They pick a wallet, see the number to send to, and send it. The payment SMS lands on your collector phone, is matched to them, and they are connected — with nothing to navigate to, because a captive mini-browser that follows a checkout loses the router's login with it.
A minute or hour pass is enforced by the router's own uptime counter. The portal asks the router what is really left, so a guest is never told they have time the router will refuse.
What you sell
Minutes, hours or days, priced as you like. When a guest buys again, the router's counter is zeroed for them — so a spent pass never locks out a paying customer.
Generate them in batches, with a real expiry date rather than a vague one, and print them for the counter. Big batches are queued instead of holding the screen.
Issue a batch to the shop that sells it. Cards stay tied to whoever holds them, and the sales stay theirs to account for.
bKash and Nagad from the portal, cash at the counter, or a card bought in advance. All three land in the same ledger as your home-line billing.
Who was online, from when, and for how long — kept as sessions, not guessed from a router screen you happened to be watching.
Hotspot profiles are provisioned on the same MikroTik, from the same packages screen your PPPoE subscribers are billed from.
Hotspot users do not count against your plan
A voucher login creates a customer row per redemption. Counting those as subscribers would fill a small plan in a week of selling cards, so they are not counted — you pay for the subscribers you actually bill.
Questions
Yes. They pick a wallet on the sign-in page, send the money to your number, and the payment SMS on your collector phone is matched to them automatically. Nothing navigates away from the captive page, which is what usually breaks a hotspot checkout.
Each batch is generated with an expiry date you choose, so a card printed today cannot be redeemed years later at today's price.
The router's own uptime limit ends the session — the panel does not have to poll for it. Buying again zeroes the counter, so they get the time they just paid for rather than a locked account.
Yes, and from one router. The packages, the payments, the reports and the subscriber records are the same set — a hotspot pass is simply a package with a short validity.
The rest of SKYNITY
Billing, the routers and the fibre share one set of records, so a payment, a package change or a failing ONU is the same fact everywhere it shows up.
Tell us how many subscribers, which routers and what packages, and the demo is set up the way you actually run.
Request a demoor email support@skynity.net
SKYNITY