Skip to main content
Captive portal onboarding is the inline registration experience that runs as part of the Portal access flow. Rather than visiting a separate URL, guests encounter the registration form automatically when their browser is redirected by the WiFi controller.

​
How It Fits the Platform

Captive portal combines onboarding and access in a single step:
  1. Guest connects to the open SSID
  2. Controller redirects HTTP traffic to the Wiacom portal
  3. Guest completes the inline registration form
  4. Wiacom authenticates via RADIUS and grants access
This is distinct from Guest Connect, where guests proactively visit a URL or scan a QR code before connecting.

​
Registration Options

The captive portal form is fully configurable:

​
SDK and App Integration

For organisations that embed WiFi onboarding inside a mobile app or third-party system, Wiacom provides an SDK and API that replicates the captive portal flow programmatically:
  • SDK — integrate the Wiacom onboarding flow inside your iOS or Android app
  • API — create or validate a guest identity from any external system; Wiacom returns an authorization token that grants access on the controller
This allows onboarding to happen inside your app, a loyalty program, a booking engine, or any other system — with the same RADIUS-based access grant that the captive portal uses.
Contact the Wiacom team to access the SDK documentation or API credentials for programmatic onboarding integration.

​
Supported Vendors

Captive portal onboarding is available on all vendors that support external splash page redirect. See the WiFi Vendors section for vendor-specific configuration.