PPPoE billing depends on access policy
PPPoE networks commonly use RADIUS, NAS devices, service profiles, and speed policies. ISPAgents should connect billing state to those access policies so customers are suspended, restored, and moved between plans with evidence.
PPPoE workflows
| Workflow | ISPAgents role | |---|---| | Subscriber identity | Track PPPoE username, customer, service, plan, NAS, and location. | | Payment restore | Restore access after confirmed payment through RADIUS or MikroTik workflow. | | Overdue suspension | Apply blocked policy, disconnect, or custom access state based on billing rules. | | Plan change | Move profile, group, queue, or speed policy when customer package changes. | | Support evidence | Show last session, payment, policy, connector action, and ticket history. |
Safe automation
PPPoE automation should preview affected subscribers, show policy mapping, and record execution results before support relies on the change.
FAQ
Can ISPAgents work with MikroTik PPPoE?
Yes. MikroTik can be controlled directly or through RADIUS depending on how the ISP built the network.
Can PPPoE billing support prepaid?
Yes. Prepaid and postpaid workflows can both map to PPPoE access policies.