MikroTik ISP Billing System: A Complete Guide for Internet Providers
Running an internet service provider requires more than fast links and reliable routers. An ISP must also authenticate subscribers, apply the correct speed plan, monitor usage, suspend overdue accounts, record payments, and give support teams accurate customer information.
That is where a MikroTik ISP billing system becomes valuable. When properly designed, it connects MikroTik RouterOS with a subscriber database, RADIUS authentication, payment processing, customer management, and reporting. The result is a more controlled way to manage broadband, wireless, hotspot, PPPoE, and reseller customers.
This guide explains how a MikroTik billing system works, which components an ISP needs, what features to look for, and how to implement one without creating avoidable network and billing problems.
What is a MikroTik ISP billing system?
A MikroTik ISP billing system is a software platform that manages subscribers and communicates with MikroTik routers to control internet access. It typically handles customer registration, service plans, invoices, payments, authentication, bandwidth profiles, usage records, account expiry, and service suspension.
MikroTik RouterOS is usually the network enforcement point. It establishes the customer session and applies the access policy. The billing application stores the commercial and subscriber information. A RADIUS server connects the two systems.
This separation is important. MikroTik can authenticate users, enforce queues, manage PPPoE and HotSpot services, and send accounting data. However, a full ISP billing operation also needs functions such as invoices, receipts, payment reconciliation, customer notifications, tax settings, support tickets, and financial reports. Those functions are normally provided by the billing application rather than by the router itself.
How the system works
A typical architecture has five layers:
1.Customer or subscriber portal: Used for registration, plan selection, payments, password changes, and account status.
2.Billing application: Stores customer profiles, packages, invoices, payments, renewals, notifications, and administrative records.
3.RADIUS server: Performs authentication, authorization, and accounting for subscriber sessions.
4.MikroTik RouterOS: Connects customers and enforces the profile returned by the billing system.
5.Monitoring and operations tools: Track router health, links, traffic, active sessions, outages, and service quality.
When a subscriber connects through PPPoE or a MikroTik HotSpot, the router sends an authentication request to the RADIUS server. The RADIUS server checks the customer’s account and service plan. If the account is active, it returns the authorization attributes, such as username, IP address, session limit, and rate limit. The router then permits the connection and applies the policy.
RouterOS supports RADIUS authentication and accounting for services including PPP, PPPoE, and HotSpot. According to MikroTik documentation, accounting information can be sent to the RADIUS server so the provider can maintain centralized session records.
When the user disconnects, the router sends an accounting update. Interim updates can also be configured so the billing system receives periodic information about active sessions, traffic, and uptime.
Core features of a MikroTik billing system
Subscriber management
The system should maintain a complete customer record, including name, contact details, installation address, service area, identity information where required, assigned router or access point, username, package, billing cycle, and account status.
A good customer record should also show the customer’s active sessions, payment history, invoices, support notes, assigned IP addresses, and equipment information. This gives the support team one reliable view instead of forcing staff to search across spreadsheets, router logs, and messaging applications.
Internet packages and speed profiles
An ISP billing platform should allow administrators to create service plans such as:
•20 Mbps residential broadband
•50 Mbps business broadband
•Unlimited monthly wireless access
•Data-limited prepaid packages
•Time-based hotspot vouchers
•Dedicated bandwidth plans
•Reseller or sub-provider packages
Each package can be linked to a MikroTik profile or RADIUS attributes. Depending on the network design, the returned policy may define upload and download limits, burst settings, priority, address pools, VLAN information, session duration, or data limits.
This makes it possible to change a customer’s plan from the billing platform rather than manually editing several routers. Changes should be tested carefully because a wrong rate-limit attribute can affect customer experience and network capacity.
PPPoE subscriber control
PPPoE is widely used by fixed-line and wireless internet providers because it gives each subscriber a clear login identity. A billing system can use PPPoE credentials to authenticate the customer and apply the correct service plan.
Common PPPoE billing functions include automatic account creation, password reset, package upgrades, expiry control, simultaneous-session limits, static IP assignment, and automatic disconnection of suspended accounts.
For larger networks, central authentication is easier to manage than maintaining separate local PPP secrets on every MikroTik router. It also improves reporting because subscriber activity is collected in one place.
HotSpot and voucher billing
MikroTik HotSpot provides a captive portal for public or semi-public internet access. It can authenticate clients using a local database or a remote RADIUS server, and it can record user accounting information locally or remotely.
This makes HotSpot suitable for cafés, hotels, schools, campuses, apartment buildings, transport terminals, and prepaid Wi-Fi services.
A billing system can generate voucher codes with specific validity periods, bandwidth limits, data quotas, or usage rules. Staff can print vouchers, sell them through agents, or allow customers to purchase access online.
The portal should clearly show the plan name, expiry time, remaining quota, support contact, and terms of use. A simple and mobile-friendly login experience is essential because many HotSpot users connect from phones.
Invoices, payments, and account lifecycle
Billing automation is one of the main reasons providers deploy an ISP billing platform. The system should generate recurring invoices, record payments, send reminders, and update account status automatically.
A typical lifecycle is:
1.The system creates an invoice before the renewal date.
2.The customer receives a message by email, SMS, or another supported channel.
3.The customer pays through a configured payment method or at an office or agent location.
4.The payment is recorded and matched to the invoice.
5.The account remains active or is renewed.
6.If payment is not received after the grace period, the system changes the account status.
7.The billing platform sends a suspension instruction or changes the customer’s RADIUS authorization.
The exact suspension method depends on the integration. Some systems reject new authentication attempts. Others send a disconnect request for active sessions and place the account in a restricted or walled-garden profile.
Providers should test the full cycle. A system that creates invoices but fails to suspend overdue sessions still leaves the most important control dependent on manual work.
MikroTik User Manager or a separate billing platform?
MikroTik User Manager is a RouterOS-based RADIUS server that provides centralized authentication and authorization. MikroTik documentation describes features such as user profiles, usage statistics, limitations, reports, and customer access to account information through a web interface.
User Manager can be useful for smaller deployments, hotspot vouchers, and environments that need straightforward centralized subscriber authentication. It can define download, upload, transfer, and uptime limits, provided that accounting and interim updates are configured appropriately.
A separate ISP billing platform is often more suitable when the provider needs advanced invoicing, multiple payment gateways, tax handling, customer portals, field-service operations, reseller management, detailed notifications, accounting integration, or multi-router administration.
The practical choice is not always one or the other. Many providers use an external billing application for business operations and RADIUS, while MikroTik routers remain responsible for access enforcement. User Manager may be used as the RADIUS layer, or the external platform may integrate with FreeRADIUS or another RADIUS implementation.
Benefits for internet providers
A MikroTik billing system can help an ISP in several ways.
Centralized control: Subscriber credentials and packages are managed from one system instead of manually across every router.
Faster provisioning: New users can be activated automatically after registration or payment.
Reliable suspension: Overdue accounts can be restricted according to defined rules instead of relying on staff memory.
Fewer configuration errors: Plans and policies are applied consistently through profiles and RADIUS attributes.
Better customer service: Support agents can see account status, payments, active sessions, assigned plans, and usage information in one place.
Improved reporting: Managers can track active subscribers, churn, revenue, arrears, package popularity, usage, and network demand.
Scalable operations: The provider can add routers, towers, access concentrators, or service areas without recreating every customer manually.
Security and reliability considerations
Billing systems control access to a network, so they must be treated as critical infrastructure.
Use strong, unique RADIUS shared secrets and restrict RADIUS traffic to trusted network paths. MikroTik supports RadSec, which uses TLS for RADIUS communication when certificates are correctly configured.
Keep management access away from the public subscriber network and use role-based administrator permissions.
Back up the billing database and router configurations regularly. Store backups outside the router and test restoration procedures. A backup that has never been restored is only an assumption.
Design for RADIUS failure. Decide whether the router should fail open or fail closed, and document the operational consequences. Maintain a backup RADIUS server where possible. Monitor authentication latency, reject rates, accounting updates, and disconnect messages.
Protect customer data as well. Billing records may contain identity information, addresses, payment references, and support history. Apply access controls, encryption, retention rules, and appropriate privacy notices.
Implementation roadmap
Start by documenting the current network. List routers, RouterOS versions, access methods, IP pools, PPP profiles, HotSpot servers, VLANs, upstream links, and existing customer records.
Next, standardize service plans. Give every plan a clear name, speed policy, billing period, quota, grace period, and suspension rule. Avoid creating dozens of nearly identical profiles without a clear operational reason.
Deploy the RADIUS service and test one router first. Verify successful login, wrong-password rejection, rate-limit enforcement, accounting records, interim updates, and session termination.
Connect the billing application after the network authentication flow is stable. Import customers carefully and reconcile account balances before activating automatic suspension.
Run a pilot with a small group of internal or low-risk customers. Test activation, renewal, upgrade, downgrade, expiry, refund handling, password reset, router failure, RADIUS failure, and payment webhook delays.
Only then expand to the rest of the network. Keep a rollback plan and retain an emergency administrative path for network operations.
Common mistakes to avoid
The most common mistake is treating a billing system as only a payment page. Payments are important, but the system must also control access, record sessions, and keep customer data consistent.
Another mistake is enabling automatic suspension before testing grace periods, time zones, failed payments, manual extensions, and support overrides. A small date or status error can disconnect many legitimate customers.
Providers also sometimes rely on local router users for a large subscriber base. This makes centralized changes, auditing, and reporting more difficult.
Finally, do not ignore accounting updates. Without accurate interim accounting, quota enforcement and session reporting may be delayed or incomplete. MikroTik’s User Manager documentation specifically notes the importance of RADIUS accounting and interim updates for seamless limitation handling.
Conclusion
A MikroTik ISP billing system gives internet providers a structured way to connect commercial operations with network access control. MikroTik RouterOS enforces the connection, RADIUS manages authentication and accounting, and the billing application manages customers, packages, invoices, payments, notifications, and account status.
The best implementation is not necessarily the most complicated one. It is the one that accurately reflects the provider’s network, automates routine operations, protects customer data, and gives staff a dependable way to resolve problems.
Start with one access method, a small number of standardized plans, and a controlled pilot. Once authentication, accounting, payment status, and suspension rules work reliably, expand the system across the network.
Ready to get started?
Internet providers can
Frequently asked questions
Can MikroTik be used for ISP billing?
MikroTik can provide the network authentication, authorization, accounting, bandwidth enforcement, PPPoE, and HotSpot functions required by an ISP billing environment. A complete commercial billing solution usually adds a separate application for invoices, payments, customer records, notifications, and reporting.
What is the role of RADIUS in MikroTik billing?
RADIUS provides centralized authentication, authorization, and accounting. It checks subscriber credentials, returns service attributes such as speed or session limits, and receives records about active and completed sessions.
Is MikroTik User Manager enough for a small ISP?
It may be enough for a small provider with straightforward subscriber authentication, profiles, usage limits, vouchers, and basic reports. Providers that need advanced invoicing, payment integrations, tax workflows, reseller management, or field-service features may need a separate billing platform.
Does a MikroTik billing system support PPPoE?
Yes. A common design uses MikroTik PPPoE servers with RADIUS authentication. The billing system creates or updates the subscriber account, while RouterOS applies the returned profile and bandwidth policy.
Can the system automatically disconnect unpaid customers?
It can, if the billing application and RADIUS integration are configured to change authorization or send a supported disconnect message. The provider should test active sessions, grace periods, manual extensions, and failed payment scenarios before enabling automation.
What should I check before choosing a billing platform?
Check support for your MikroTik RouterOS version, PPPoE and HotSpot, RADIUS accounting, interim updates, bandwidth profiles, IP pools, payment methods, customer notifications, backups, reporting, API access, and multi-router management.
Ready to get started?
Internet providers can
