1. Introduction
If you run a prepaid WiFi business, you probably know the routine. A customer pays, sends a screenshot, and waits while you or a staff member finds the right profile and activates the account by hand. Another customer disputes a payment from last week and nobody can say whether access was ever granted. Revenue leaks quietly through these gaps, and it gets worse as you add hotspots and subscribers.
Hotspot billing software for ISPs closes those gaps. It ties together the pieces that operators usually patch by hand: subscriber records, access rules, the login page, payment collection, vouchers, and reporting. When these pieces work together, a payment turns into working access without anyone touching a spreadsheet.
This article walks through what that software should do, function by function, in plain operator terms. Africa appears here only as topic geography, because the problems of manual billing, patchy power, and mobile money collection shape what operators across the continent need from their tools. For context on FLUXI: it is live in Uganda, and any other African market is roadmap work in progress, not live. Nothing below describes availability anywhere else. If you want a broader checklist before you read on, the hotspot billing software guide is a useful companion.
2. Core Functions of Hotspot Billing Software
Before looking at RADIUS or payments, it helps to understand the foundation. Good billing software keeps one record for each customer, one definition for each service you sell, and one trail from payment to access. If you want to see how this plays out for operators selling prepaid plans, read how ISPs manage prepaid customer access without constant manual work.
Hotspot billing software with prepaid access control follows a simple rule: access exists only while a valid purchase backs it. Everything in this section supports that rule.
2.1 Subscriber account creation and management
Subscriber account management starts with a clean record for every customer. A subscriber account holds identity details, contact information, the service they bought, their current status, and their payment history. For PPPoE customers, it also holds the credentials the router or access concentrator will check. For hotspot users, it may hold a phone number or a voucher-based identity instead.
Think about the operator who keeps customers in a notebook and a chat app. When someone calls to say their internet stopped, the operator searches old messages to learn what plan they paid for. With a proper subscriber account, the operator opens one screen and sees status, plan, last payment, and recent sessions. Suspending, reactivating, or changing a plan becomes a single action, and the network follows that action automatically.
2.2 Service definition and time based access control
A service definition describes what you sell. It names the plan, sets the access rules that come with it, and states how long access lasts. Time based access control then enforces that duration. A customer who buys a short pass gets access that ends on schedule, and a customer on a recurring plan keeps access until the billing period closes.
The value is consistency. Without defined services, every sale becomes a negotiation and every staff member applies different rules. With service definitions stored in the billing system, the same purchase always produces the same result, whether it happens at a busy kiosk or in the middle of the night.
2.3 Automated invoicing and payment tracking
Automated invoicing and payment tracking replace the monthly scramble of working out who owes what. For recurring customers, the system generates an invoice when a billing period closes, links incoming payments to that invoice, and marks it settled. For prepaid users, the invoice is created at the moment of purchase and closed when payment is confirmed.
Hotspot billing software with automated invoicing also shows you the other side: unpaid invoices, partially paid accounts, and customers approaching expiry. Instead of chasing people from memory, you work from a list. That alone recovers revenue many small operators do not realize they are losing.
3. RADIUS Authentication and Session Control
Most serious setups rely on RADIUS to decide who gets on the network and for how long. A hotspot billing system with RADIUS authentication gives you a central place to make that decision, so your access points and routers do not each carry their own copy of the rules. This section explains how hotspot billing software controls user sessions from the first login to the final disconnect.
3.1 Authentication workflow for hotspot users
RADIUS authentication works like a checkpoint. A user tries to connect, and the network device that receives the request asks the RADIUS server whether this person may enter. The server checks the credentials against the subscriber account or the voucher code and answers yes or no.
Picture a customer at a roadside hotspot entering a code from a scratch card. The access point does not know whether the code is valid. It forwards the request, the billing system looks up the code, confirms it is unused and unexpired, and tells the device to allow the session. The customer sees a working connection. The operator did nothing.
3.2 Authorization rules and access profiles
Authentication answers who the user is. RADIUS authorization rules answer what that user may do. The server returns attributes with its approval, and the network device applies them. These attributes carry the limits tied to the user’s plan.
An access profile bundles those rules under a name, such as a basic plan or a business plan. When you change a profile, every user attached to it follows the new rules at their next session. This is far safer than editing settings device by device, where one forgotten router can quietly give away a premium plan.
3.3 Accounting records and session termination
RADIUS accounting records track what happens during a session: when it started, how long it ran, how much data moved, and why it ended. This is the raw material for usage limits, billing disputes, and reporting.
Session control also needs a way to end access on purpose. Session termination is how the system disconnects a user whose time has run out, whose data allowance is spent, or whose account was suspended. Without it, expired users stay online until they disconnect themselves. A realistic example: an operator suspends a customer for non-payment, and the billing system immediately sends a disconnect request so the customer cannot continue on an already open session.
4. Captive Portal and User Access Experience
The captive portal is the face of your service. It is the page customers see before they get online, and it is where most support problems begin. Hotspot billing software with captive portal support should make login, payment, and recovery simple enough that customers rarely need to call you.
4.1 Login page flow and device onboarding
A captive portal login flow starts when a new device joins the network and tries to open any page. The network redirects that request to the portal. The user then logs in, redeems a voucher, registers, or pays, and the system releases the device onto the internet.
Device onboarding is the part that remembers who is who. When a returning customer’s device reconnects, the portal can recognize it and skip the login steps where your policy allows. Operators who skip this detail end up with customers who must re-enter details every time their phone sleeps, and those customers blame the network, not the portal.
4.2 Self registration and voucher redemption options
Self registration software lets new users create their own accounts from the portal, usually with a phone number, instead of waiting for staff. This cuts front desk work and lets small operators sell access without being present.
A voucher redemption system covers customers who buy access offline. They scratch or reveal a code, type it into the portal, and the system validates it against the batch it came from. Offering both paths matters. Some customers prefer paying on their phones, while others only trust a printed code bought from a nearby reseller.
4.3 Session status display and logout controls
Customers want to know what they have left. A good portal shows the remaining time or allowance, the plan in use, and the account status. It also gives a clear logout button, which matters on shared devices and in cafes where one person leaving should not leave access open for the next.
When users can check their own status, support calls drop. A customer who sees that their plan expired does not phone to ask why the internet stopped. They top up instead.
5. Payment Collection and Gateway Integration
Payments are where manual operations lose the most money. A payment gateway connects your billing system to the channels customers already use, and hotspot billing software with mobile money and card payments lets customers pay without sending proof to a person.
5.1 Mobile money and card payment workflows
A mobile money payment workflow usually goes like this. The customer picks a plan on the portal, enters a phone number, and receives a prompt on their handset to approve the payment. The gateway reports the result back to the billing system, which then activates access. A card payment workflow follows a similar path, with the customer entering card details on a secure payment page before the result returns.
Two operational truths shape a reliable design. First, the browser should never wait on the gateway callback. The portal shows a pending state and checks for completion, while the callback is handled in the background. A page that hangs on a slow callback leaves customers tapping and paying twice. Second, fulfillment must be idempotent at the database level. If the gateway sends the same confirmation more than once, the customer still receives access once and the invoice is closed once.
5.2 Automated reconciliation and receipt generation
Automated payment reconciliation matches every gateway confirmation to an invoice or voucher purchase. At the end of a trading period, you compare what the gateway says you collected with what the billing system says you sold. When the two agree, you can trust your numbers. When they differ, the exceptions list shows exactly where to look.
Receipt generation software then gives the customer proof of purchase automatically. This reduces disputes, because the customer holds a record that matches yours. Where a code is delivered, show it on screen first. An SMS can be queued as a convenience copy, but the on screen code must always be there, so a delayed message never leaves a paying customer stranded.
5.3 Handling failed and pending transactions
Not every payment completes cleanly. A failed transaction is one the gateway rejected or the customer cancelled. A pending transaction is one where the outcome is not yet known, often because the customer has not approved the prompt or the confirmation is delayed.
The system should treat these states differently. Failed transactions leave no access behind and allow a simple retry. Pending transactions hold the order open, keep checking the result, and activate access the moment confirmation arrives. Operators should also be able to see a list of pending items so a customer who says they paid can be answered with facts, not guesses.
6. Voucher and Prepaid Access Management
Vouchers remain a practical way to sell access where customers prefer cash or lack a card. Hotspot billing software with voucher management turns a messy paper process into a controlled one.
6.1 Voucher generation and batch controls
Voucher generation and batch controls let you create many voucher codes at once, tie them to a specific service, and label them as a batch. A batch might be created for a particular reseller, a promotion, or a specific location. Each voucher code should be unique and hard to guess.
Batch controls matter when something goes wrong. If a batch is lost or stolen, you disable that batch and leave the others untouched. Without batch labeling, you would have to cancel everything or accept the loss.
6.2 Distribution tracking and redemption monitoring
Voucher distribution tracking records which batch went to which reseller or site, and when. Redemption monitoring then shows which vouchers were used and which are still unsold or unused.
This closes a common gap in reseller businesses. A reseller who claims to have sold fewer vouchers than they actually did becomes visible, because redemptions tell a different story than the sales report. Reseller trust improves when both sides can check the same record.
6.3 Expiry handling and unused access policies
Voucher expiry handling decides what happens when a voucher ages out or a purchased plan ends. You set rules for how long an unredeemed voucher stays valid, whether purchased time starts at redemption or at first login, and what happens to leftover allowance.
Clear unused access policies protect both sides. Customers know what they paid for, and operators avoid liabilities from old vouchers sitting in drawers. Whatever rules you choose, publish them on the portal so there are no surprises at the point of complaint.
7. Network Integration and Equipment Compatibility
Billing software only works if the network obeys it. That means the software must talk to the equipment you already own. If you are still comparing options, the notes on choosing a billing platform for small ISPs can help you frame the decision.
7.1 Router and access point integration patterns
Router integration and access point integration usually follow the same pattern. The device is configured to send authentication and accounting requests to the RADIUS server and to redirect unauthenticated users to the captive portal. The billing system then acts as the single source of truth for who may connect.
Because many operators run mixed equipment, compatibility with standard protocols matters more than any single device model. Use generic router, access point, and network equipment terms when you plan your setup, and confirm standards support before you buy new hardware.
7.2 Support for hotspot and broadband access types
Many operators sell more than one kind of access. Hotspot users connect through a portal and may be anonymous or voucher based. Broadband access customers, such as PPPoE subscribers, authenticate with stored credentials and usually stay connected for long periods.
Billing software should handle both under the same roof. A single customer database, one payment system, and one set of reports save you from running separate tools for each access type. It also lets a customer move from a hotspot plan to a home plan without starting over.
7.3 Bandwidth shaping and usage limits
Hotspot billing software with bandwidth shaping and usage limits turns plan definitions into real network behavior. Bandwidth shaping controls how much capacity each user or profile may take, so one heavy user cannot starve everyone else. Usage limits cap the time or data a plan allows before access ends or slows.
The access profile carries these rules, the RADIUS server delivers them at login, and the network device enforces them. Operators who rely on manual limits on each device find that settings drift over time. Central rules stay consistent.
8. Operational Monitoring and Reporting
You cannot manage what you cannot see. Monitoring tells you what is happening now, and reporting tells you what happened and why. If you operate more than one location, this guide on how to manage customers across sites covers the extra considerations.
8.1 Real time session and transaction visibility
Hotspot billing software with real time session monitoring shows who is online, on which plan, and from which device or site. Real time session monitoring helps you spot problems while they are happening, such as a sudden drop in active users at one location.
Transaction visibility sits next to it. You see payments arriving, pending items waiting, and failures as they occur. An operator who sees a cluster of failed transactions can check the gateway connection before customers start complaining.
8.2 Usage reports and subscriber activity logs
A usage report summarizes consumption by user, plan, or site. It helps you decide where to add capacity, which plans are priced too low, and which customers are close to their limits. Reports on sales, collections, and expiries help you plan cash flow.
Subscriber activity logs record the detail behind those totals, such as logins, disconnects, plan changes, and payments. Each activity log entry becomes evidence when a customer disputes a charge or claims they were disconnected unfairly. Good logs settle arguments quickly.
8.3 Alerts for system fault and abnormal usage
System fault alerts tell you when something important breaks, such as the RADIUS service stopping, a gateway connection failing, or a device going silent. Alerts for abnormal usage flag behavior that looks wrong, such as one account consuming far more than its plan would normally allow.
The aim is to hear about problems from the system before you hear about them from customers. Send alerts to the people who can act on them, and keep the rules simple enough that the team does not learn to ignore them.
9. Security and Reliability Considerations
A billing system holds customer details and money flows, so it deserves the same care as any business-critical system. For a deeper look at designing for growth, see this scalable hotspot billing guide.
9.1 Data protection and access controls
Data protection starts with limiting what is stored and who can see it. Customer details, payment references, and credentials should be protected in storage and in transit. Never store more payment detail than you need, and let the gateway handle sensitive card data on its own secure pages.
Access controls decide which staff can do what. A front desk agent may need to look up accounts and sell vouchers, but not change pricing or export the whole customer base. Role based permissions, together with a record of administrative actions, keep honest staff protected and make misuse easier to trace.
9.2 Redundancy and offline resilience
Redundancy means a single failure does not take your whole service down. Offline resilience means the network can keep working when the internet link or the power supply is interrupted. These matter in places where outages are routine.
Plan for the reality that users who are already authenticated should not be thrown off by a short loss of the upstream link, and that the billing system should recover cleanly and reconcile what happened once it returns. Regular backups and a tested recovery process are part of reliability, not extras.
9.3 Fraud prevention and misuse detection
Fraud prevention covers the ways people try to get access they did not pay for: guessed voucher codes, repeated redemption attempts, shared credentials, and duplicated payment confirmations. Idempotent fulfillment protects against replayed confirmations, and unique, hard to guess codes protect vouchers.
Misuse detection looks for patterns after the fact or in real time. Examples include one voucher used from many devices, accounts logged in at distant locations at once, or a sudden burst of failed login attempts. Flagging these early lets you suspend an account before the loss grows.
10. FAQ
10.1 How does hotspot billing software connect to existing network equipment
It connects through standard protocols. Your router or access point is set to send authentication and accounting requests to the RADIUS server and to redirect new users to the captive portal. The billing system then controls access, applies plan rules, and records sessions without you managing each device by hand.
10.2 What payment methods can be supported through gateway integration
Through a payment gateway, the software can support mobile money payments and card payments, along with voucher purchases made offline and redeemed on the portal. The exact methods depend on the gateway you connect and the channels it offers, so confirm your needs before you commit.
10.3 How are vouchers created tracked and redeemed
Vouchers are generated in batches, tied to a service, and given unique codes. You track which batch went to which reseller or site, and the system records each redemption when a customer enters a code on the portal. Unused and expired vouchers are visible in reports.
10.4 How does RADIUS authentication manage user sessions
RADIUS authentication verifies the user when they connect, then returns authorization rules that set what they may do. During the session, accounting records track time and usage. When the plan ends or the account is suspended, the system triggers session termination so access stops.
10.5 What reports are available for subscriber and usage management
Expect reports on active sessions, usage by user or plan, sales and collections, pending and failed transactions, voucher redemptions, and expiries. Subscriber activity logs back these up with detailed records you can search when a dispute or fault needs investigation.
10.6 How is service continuity maintained during internet or power disruptions
Continuity comes from planning at several levels: redundant components where possible, backup power for key equipment, and designs that let existing sessions continue through short upstream interruptions. When the connection returns, the billing system reconciles pending payments and session records so nothing is lost or double counted.