Mikrotik Hotspot Billing: A RouterOS Setup Guide for ISPs

Mikrotik routers dominate the small-to-mid ISP and hotspot market in Kenya for a good reason: RouterOS exposes a full API that lets external software manage hotspot users, PPPoE sessions, and bandwidth profiles programmatically. That API is what makes automated billing possible in the first place — without it, every session extension or cutoff would be a manual login to WinBox.

Which RouterOS version and hardware works

Any Mikrotik device running RouterOS 6.x or 7.x with the API service enabled is a candidate. In practice, common choices for hotspot and small-ISP deployments are the hAP ac², hAP ax², the CCR series for higher-throughput sites, and various RB-series boards — the model matters less than whether RouterOS and the API service are both present and enabled.

Enabling the API service

By default the API service is often disabled or restricted. Under IP → Services in WinBox (or the equivalent CLI), confirm the API service is enabled and, ideally, restricted to the IP address of whatever machine or server your billing platform runs on — there is no reason to expose the API port to the wider internet.

Matching billing plans to RouterOS profiles

Each package you sell — say, "1 Day Unlimited" or "1GB Weekly" — should map to a hotspot user profile or PPPoE profile on the router that defines the actual speed limit. Your billing platform's job is to create the hotspot/PPPoE user with the right profile when a customer pays, and disable or remove it when their time or data runs out. Getting the profile names consistent between your billing system's plan configuration and what actually exists on the router is the single most common setup mistake — a plan pointing at a profile name that doesn't exist on the router will fail silently at session-creation time.

Hotspot mode vs PPPoE mode

RouterOS supports both, and which one you use changes how sessions are tracked and enforced. If you're deciding between the two for your deployment, that trade-off deserves its own look — see our guide on choosing between PPPoE and hotspot billing.

Most operators get a router fully configured and connected to a billing platform in under two hours once the API service is confirmed enabled and profile names are agreed on — the setup work is mostly upfront, one-time configuration rather than ongoing maintenance.