Skip to main content
← Back to Blog
Hotspot10 min readApril 7, 2026
HotspotWiFi ZoneCaptive PortalMikroTikISP Revenue

How to Set Up a Hotspot WiFi Zone for Your ISP: Complete Setup Guide

Hotspot WiFi zones are one of the fastest ways for ISPs to expand revenue. From cafes and airports to parks and transit hubs, a captive portal lets you monetize public WiFi while keeping full control over authentication, bandwidth, and billing. This guide covers everything — hardware, configuration, monetization, and scaling.

What Is an ISP Hotspot Zone?

An ISP hotspot zone is a public or semi-public WiFi access point that uses a captive portalto control who connects and how they're billed. A hotspot zone forces every device through a login page before granting internet access, giving operators full control over authentication, usage limits, and revenue collection.

Hotspot zones are deployed in high-traffic public spaces:

Hospitality

Hotels, resorts, and guest houses offer WiFi as an amenity or a paid upgrade tied to room packages.

Transit & Public

Airports, bus stations, parks, and city centers provide sponsored or paid connectivity to travelers.

Commercial

Cafes, restaurants, shopping malls, and co-working spaces use hotspots to attract and retain customers.

For ISP operators, hotspot zones represent a recurring revenue channel beyond home broadband — generating income through packages, vouchers, or advertising.

How Hotspot Authentication Works

The hotspot authentication flow separates a managed WiFi zone from a simple open network. Every connection passes through a controlled sequence:

  1. 1.A customer connects to the open SSID broadcast by the hotspot access point — no password required.
  2. 2.The MikroTik hotspot server intercepts all HTTP/HTTPS requests and redirects to a captive portal login page.
  3. 3.The customer authenticates via OTP, a prepaid recharge card code, or by purchasing a package from the portal.
  4. 4.MikroTik sends the credentials to RADIUS for validation. RADIUS checks the username, password, and package status.
  5. 5.On success, RADIUS returns an Access-Accept with session attributes — bandwidth limit, time quota, data cap — and MikroTik grants internet access.
  6. 6.Throughout the session, MikroTik sends accounting updates to RADIUS, tracking usage and connection status in real time.

The walled garden is critical to this flow — it defines which destinations (captive portal, payment gateways, OTP services) are accessible beforelogin. Without it, customers can't reach the login page or complete payments.

Hardware Requirements for a Hotspot Zone

Deploying a reliable hotspot zone requires the right hardware stack. MikroTik-based setups are cost-effective and widely supported by ISP billing platforms:

MikroTik Router

Runs the hotspot server, manages the captive portal, and communicates with RADIUS. Examples: RB750Gr3, RB4011, CCR1036.

Access Points

Broadcast the SSID and handle wireless client connections. Examples: MikroTik cAP ac, Ubiquiti UAP-AC-PRO.

PoE Switch

Powers access points over Ethernet, eliminating separate adapters. Examples: MikroTik CRS328-24P, Netgear GS108PP.

Cabling & RADIUS

Cat6 Ethernet between switch and APs. RADIUS server (FreeRADIUS on Linux or ISPbills managed) handles all authentication.

For a small cafe, a single MikroTik router with one or two access points is sufficient. For larger venues, you'll need multiple APs connected through PoE switches, all managed by a central MikroTik router. ISPbills provides a fully managed RADIUS instance so you don't have to maintain the server yourself.

MikroTik Hotspot Server Configuration

The MikroTik hotspot server powers your captive portal — intercepting traffic, presenting the login page, and enforcing session rules based on RADIUS responses. Key configuration areas:

  • Hotspot Server Profile — Define the login page URL, redirect behavior, cookie lifetime, and idle timeout that control the captive portal experience.
  • RADIUS Integration — Point the hotspot server to your FreeRADIUS instance with the shared secret, authentication port (1812), and accounting port (1813).
  • Walled Garden — Whitelist domains and IPs accessible before login: the portal domain, payment gateways, OTP services, and branding assets.
  • Login Page Customization — Brand the portal with your ISP logo, colors, and package selection UI using custom HTML/CSS templates.
  • IP Pool & DNS — Assign a dedicated DHCP pool for hotspot clients and configure DNS redirection to trigger the captive portal reliably.

A common pitfall is an incomplete walled garden — if payment or OTP endpoints aren't whitelisted, customers get stuck on the login page. Always test the full flow from a fresh device.

Monetization Models for Hotspot WiFi Zones

One of the biggest advantages of a captive portal hotspot is the flexibility to monetize access in multiple ways. Most successful operators combine several models:

Free Tier with Caps

Offer 15–30 minutes of free WiFi or 50–100 MB to attract users. After the limit, prompt them to purchase a paid package.

Paid Time Packages

Sell hourly, daily, or weekly access passes — common for airports and transit hubs where customers need short-term connectivity.

Voucher / Recharge Cards

Physical or digital voucher codes purchased from a counter. Each code activates a specific package with defined time and data limits.

OTP Self-Registration

Customers enter their phone number, receive an OTP, and register automatically. They get a trial package and can purchase upgrades from the portal.

The most effective approach is a freemium model: give users a free trial, then upsell to a paid package — maximizing registrations while converting a meaningful percentage into paying customers.

Customer Self-Registration & Device Management

A frictionless self-registration flow is essential for hotspot zones. Unlike home broadband where an operator manually creates each account, hotspot customers need to onboard themselves in seconds:

  1. 1.The customer connects to the hotspot SSID and is redirected to the captive portal.
  2. 2.They enter their phone number on the registration page. The system sends an OTP via SMS.
  3. 3.After verifying the OTP, the system automatically creates a hotspot account linked to their phone number and MAC address.
  4. 4.The customer is assigned a free trial package (e.g., 30 minutes or 100 MB) and immediately gets internet access.
  5. 5.When the trial expires, the portal prompts them to purchase a full package — hourly, daily, or weekly — via mobile payment or voucher code.

Once registered, managing hotspot customers involves:

  • MAC-Based Authentication — After initial login, the system can remember the customer's device MAC address for seamless reconnection without re-entering credentials.
  • Device Limits — Restrict each account to one or two simultaneous devices to prevent credential sharing and bandwidth abuse.
  • Session Tracking — Monitor active sessions in real time: who is connected, how long they've been online, how much data they've used, and which access point they're on.
  • Usage Reports — Generate per-customer and per-zone reports showing total connections, data consumed, revenue generated, and peak usage hours.

Scaling to Multiple Hotspot Zones

A single hotspot zone proves the concept — but the real value comes when you scale across multiple locations with centralized management and zone-level analytics:

  • Zone-Based Pricing — Different venues warrant different pricing. Configure zone-specific packages and pricing tiers from your billing dashboard.
  • Centralized RADIUS — All zones authenticate against a single RADIUS server, ensuring consistent policies and a unified customer database.
  • Bandwidth Management — Use MikroTik queue trees to allocate bandwidth per zone and per user, ensuring fair distribution across all connected clients.
  • Fair Usage Policies (FUP) — Define data caps and speed throttling rules. After a threshold, reduce speed for the remainder of the session.
  • Roaming Across Zones — Registered customers connect at any zone without re-registering. Their account, balance, and active package carry over seamlessly.

Scaling without centralized software quickly becomes unmanageable — which is where an integrated ISP billing platform becomes essential.

How ISPbills Handles Hotspot Management

ISPbills provides end-to-end hotspot management as part of its ISP billing and CRM platform. Instead of stitching together separate tools, ISPbills handles everything from a single dashboard:

Auto Registration & Recharge Cards

Self-registered OTP customers get automatic accounts and RADIUS credentials. Generate batches of recharge card codes with specific packages — activated instantly when entered.

Hotspot Billing & Packages

Create time-based and data-based packages (1 hour, 1 day, 1 week, 1 GB). Set pricing, speed limits, and validity. Customers purchase directly from the captive portal.

Session Logs & Reports

View detailed logs of every session: login/logout time, data transferred, MAC address, IP assigned, and which zone the customer connected to.

Multi-Zone Dashboard

Monitor all hotspot zones from a single view: active users, revenue per zone, top-selling packages, and real-time session counts with zone-specific FUP rules.

By integrating hotspot management into the same platform that handles PPPoE subscribers and invoicing, ISPbills eliminates the need for separate hotspot billing software. Every customer, session, and transaction is tracked in one place.

Ready to Transform Your ISP Business?

Join hundreds of ISPs across Bangladesh and South Asia who trust ISPbills to manage their operations. Start your free trial today — no credit card required.