MikroTik billing software
Add a subscriber and the PPPoE secret, profile and queue are written to your MikroTik over the RouterOS API. Change their package and the router follows. Let the bill lapse and the line is suspended or parked; pay it and the line comes back — without anybody opening Winbox.
On the router
The panel is where a subscriber is added, billed and cut off. The router is told, over the API, and checked afterwards to see that it listened.
A new subscriber's secret, profile and queue are written over the RouterOS API. A package change moves them to the new profile and makes the session re-dial onto it.
The secrets and profiles already on the router are read in when you connect it. Anything that does not match up is listed on its own rather than merged quietly.
Every ten minutes the router is compared with the panel. A secret somebody added by hand, or a profile that no longer matches its package, shows up as drift — not as a surprise at the end of the month.
A captive portal, time-based passes, vouchers and scratch cards — for a café, a hostel or a market, billed in the same system as the home lines.
Authentication and accounting over RADIUS, with every session kept: who was online, from when, and for how long.
If you turn it on, an overdue subscriber is moved to a slow profile and any web page they open shows how to pay. Pay, and the session is moved back to the full package.
Connecting a router
On API-SSL the panel signs in only to the certificate you pinned. A router whose certificate has been replaced is refused until you pin it again, rather than trusted because it answered.
A router behind NAT or CGNAT dials out to the panel over a WireGuard tunnel. Nothing on your network has to be opened to the internet for the panel to reach it.
Existing profiles become packages you can price, and existing secrets become subscribers you can bill. Nobody starts from an empty list.
Health, sessions and a ping every minute, an alert when the router stops answering, and its configuration exported over SSH every night — signed in only to the router's pinned host key.
On a live network
A billing system that writes to the router can disconnect a paying customer. These are the rules it keeps so that it does not.
Questions
No. A router on a public address, a LAN or a port-forward is reached directly; one behind NAT or CGNAT dials out to the panel over a WireGuard tunnel instead.
No. Connecting a router reads its secrets and profiles in. What does not match the panel is listed for you to decide about, and the regular checks after that only read.
The payment is recorded and the invoice settled straight away — billing does not live on the router. Switching the line back on is held and retried until the router answers.
An alternative to cutting an overdue subscriber off. They are moved to a low-speed profile, and their web traffic is sent to a page that tells them their account needs paying and can text them their payment link. When they pay, their session is kicked so it re-dials onto the full package. It is off unless you turn it on.
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