Best Hotspot & Prepaid Card System: An ISP Buyer’s Guide
Learn how to evaluate hotspot and prepaid operations, from captive-portal access and voucher control to distributor reconciliation, audit evidence, and failure recovery.
Learn how to evaluate hotspot and prepaid operations, from captive-portal access and voucher control to distributor reconciliation, audit evidence, and failure recovery.
A hotspot and prepaid operation fails when access, card inventory, payments, and support records are managed as separate queues. Buyers should evaluate the complete path from captive-portal login to session evidence, recharge, distributor settlement, and recovery when a dependency is unavailable.
Define the access and AAA control path
The captive portal should collect a voucher or subscriber credential, pass it to AAA, and apply an explicit policy for validity, speed, time, volume, or package. Confirm how the system handles NAS identification, concurrent sessions, expiry, failed logins, and a user who changes package while already online. For hotspot and PPPoE environments, FreeRADIUS policy management, radacct session records, post-authentication logs, and Change of Authorization (CoA) provide useful control and evidence points.
Test the failure path as carefully as the success path. Define what happens during a RADIUS timeout, a captive-portal outage, a duplicate or already-used card, an interrupted recharge, or a delayed CoA. A safe design should avoid silently granting access, record the rejected action, and give support a clear retry or escalation procedure. Validate RouterOS, RADIUS, product versions, network configuration, contracts, and local regulations before production use.
Access control
Test authentication, policy assignment, session limits, expiry, and package changes on each relevant NAS.
Card control
Protect batch ownership, denomination data, exports, printed stock, and distributor handoffs from creation through redemption.
Evidence control
Retain authentication, recharge, payment, session, adjustment, and settlement records with operator context.
Recovery control
Define ownership, retry rules, customer communication, and escalation steps for failed authentication, recharge, payment, or access changes.
Generate and distribute vouchers safely
Voucher generation is more than producing random codes. The team needs configurable batches and denominations, a defined activation state, an inventory owner, and a controlled delivery method. Printable cards may suit retail outlets, while CSV downloads can support controlled imports or printing. Either method needs restricted access, an export register, duplicate detection, and a process for lost, exposed, returned, or unsold stock.
Distributors should receive only the inventory and visibility required for their role. Record issued quantities, redeemed cards, payments received, adjustments, and outstanding balances. Reconcile those records on a fixed schedule rather than waiting for a complaint. Bill-payment history and a distributor portal can reduce manual handoffs, but the operator still needs approval rules and exception ownership.
Where ISPbills fits the workflow
ISPbills connects subscriber, billing, support, network, payment, messaging, reporting, and access-control workflows in one operational system. Its FreeRADIUS capabilities include NAS and policy management, radacct session records, post-authentication logs, PPPoE and Hotspot authentication, and CoA support.
For prepaid operations, ISPbills supports configurable recharge-card batches and denominations, printable or CSV card downloads, a distributor portal, bill-payment history, and Hotspot recharge or package changes through cards. This can simplify the handoff from card inventory and payment review to access-policy action. Verify the required capabilities, integrations, permissions, reporting detail, version compatibility, and plan availability with the current product and pricing information; do not assume every feature is included in every plan.
Evaluate reconciliation and recovery
Run a scripted pilot with one NAS, one distributor, and several denominations. Trace a card from batch creation to delivery, redemption, session authorization, recharge or package change, and settlement. Then deliberately submit a duplicate code, interrupt a payment, stop RADIUS, and create a mismatch between redeemed cards and distributor funds.
Research basis: ISPbills product documentation; MikroTik RouterOS documentation; FreeRADIUS documentation. Validate implementation details against the software releases, contracts, configurations, and local regulations governing your network.