Billing should control service state
Small ISPs often run billing in one place and MikroTik access rules in another. That creates manual work: support checks payment status, finance confirms the balance, then someone logs into RouterOS to suspend, restore, or change speed.
ISPAgents connects the billing workflow to MikroTik so paid, overdue, upgraded, or downgraded subscribers can be handled with clear approval and audit evidence.
MikroTik billing workflows
| Workflow | ISPAgents role | |---|---| | Automatic suspension | Preview and apply the right RouterOS or RADIUS action for overdue accounts. | | Payment restoration | Restore service after payment confirmation and keep evidence on the customer record. | | Plan changes | Move a subscriber to the correct queue, profile, address list, or RADIUS policy. | | Support checks | Show payment, access state, router context, and recent automation results together. | | Audit and rollback | Record what changed, who approved it, when it ran, and how to recover. |
Direct RouterOS control and RADIUS
ISPAgents should support the common MikroTik patterns that real ISPs use:
- RouterOS API for queues, address lists, firewall policy, DHCP, and status.
- Existing FreeRADIUS for PPPoE, Hotspot, policy, and accounting workflows.
- ISPAgents Managed RADIUS when the operator wants cloud-managed access.
- Custom connectors for private networks, NATed sites, unusual queue layouts, or vendor-specific steps.
Why this matters for small ISPs
Every manual access change creates delay, errors, and missing proof. A serious MikroTik billing system should reduce the work without hiding the risk. The operator needs command preview, approvals, connector health, retry state, failure explanations, and a complete customer timeline.
FAQ
Can ISPAgents cut off MikroTik internet automatically?
Yes. ISPAgents can automate suspension and restoration through RouterOS, RADIUS, or a custom connector depending on how the ISP designed the network.
Does MikroTik billing require managed RADIUS?
No. Some operators start with direct MikroTik control. Others use existing FreeRADIUS or managed RADIUS. ISPAgents should support all three paths.