RADIUS billing

RADIUS Billing Software

Connect billing and payments to RADIUS policy with controlled subscriber access, support evidence, and finance state alignment.

Managed RADIUS
Operator console

Subscribers, devices, and access in one view

subscribers
4.2k
sites live
3
critical fails
0
LiveSubscriber + device identityMapped
ActionGuarded command previewApproved
AuditEvery change loggedTracked
One operator surface ties each subscriber to their devices, access, and history.
Page type
Solutions
Primary search
RADIUS billing software
Updated
2026-06-07

Billing and RADIUS must stay aligned

When billing says a customer paid but RADIUS still blocks them, support loses time and customers lose trust. ISPAgents should connect billing state, payments, and RADIUS policy with visible evidence.

RADIUS billing workflows

WorkflowISPAgents role
Plan mappingMap service packages to groups, profiles, rate limits, or access policies.
SuspensionPreview and change access state for overdue subscribers according to operator rules.
RestorationRestore paid customers through RADIUS or CoA where the NAS and tenant policy support it.
AccountingUse session context and customer history for support and NOC visibility.
Hybrid rolloutKeep existing FreeRADIUS or move selected sites to managed RADIUS after tenant-specific launch proof.

Access evidence

Support should see username, NAS, policy, service plan, last payment, last automation result, and the reason for blocked or restored service.

FAQ

Does ISPAgents require managed RADIUS?

No. ISPAgents should treat existing FreeRADIUS, managed RADIUS, MikroTik direct control, and custom connectors as separate validated deployment paths. Managed RADIUS is available as commercial early access after tenant launch proof and signed failure posture.

Can RADIUS and MikroTik direct control coexist?

Yes. Many networks need both patterns for different sites, packages, or legacy workflows.

Next step

See how this works in your network.