Billing, ERP, communication and streaming software from Dhaka. Every day • 10:00 AM – 10:00 PM01347-536500 to 01347-536509info@sweetbilling.com

RADIUS or MikroTik API: Which Should Your ISP Billing Use?

A plain comparison of RADIUS and the MikroTik API for PPPoE authentication and billing, with when each one makes sense.

By the Sweet Billing team Updated 3 min read Facebook WhatsApp

Two ways to control access

With the MikroTik API, the billing system writes PPPoE secrets directly into each router. With RADIUS, routers keep no user list; they ask a central RADIUS server every time a customer connects. Both work. The right choice depends on how many routers you run and how much you want to centralise.

When the API approach is enough

For an ISP with one to a few routers, the API is simple to run. There is no extra server, and secrets stay on the router even if the billing server is briefly unreachable. The billing system must keep every router in sync, so it needs to handle routers that are offline at the moment of a change.

When RADIUS pays off

Once customers can connect through several routers, or you add POPs often, RADIUS keeps one source of truth. A customer can move between NAS devices without copying secrets, and accounting records give exact session start, stop and usage data.

What to check in either case

Ask how expiry is enforced, how fast a paid customer is restored, what happens when a router or the RADIUS server is down, and whether session logs are kept for investigation. These details decide how much manual work remains.

Sweet ISP Billing supports both

Sweet ISP Billing works with MikroTik through the API and also supports RADIUS-based setups, so an ISP can start simple and move to RADIUS as it grows without changing its billing data.

See it working

Open a live demo or talk to the Sweet Billing team about your setup.

More guides