PaySpot Docs
Tenant onboarding docsBack to PaySpot

Onboarding Map

Choose the right PaySpot setup guide

Use this list during tenant onboarding. Start with the tenant's network platform, then decide whether customers need to buy from inside the captive portal before they are authenticated.

Controller export fallback

CSV Import

  • Omada OpenAPI is missing or unreliable.
  • The tenant already creates vouchers inside Omada.
  • You want the fastest first launch.

Required for captive checkout

Omada Access List

  • PaySpot must load before the user is authenticated.
  • Paystack checkout opens inside captive portal.
  • The portal page has a Buy Voucher button.

Captive entry screen

Custom Portal Page

  • The tenant wants a branded captive page.
  • Omada should send users to PaySpot.
  • External Web Portal or a Buy Voucher link is needed.

Advanced manual integration

Omada OpenAPI

  • The controller exposes northbound OpenAPI credentials.
  • A manual client ID and secret integration is required.
  • The guided TP-Link Cloud login is not suitable for this controller.

Account subscriptions

External RADIUS Account Access

  • Customers need accounts instead of one-time vouchers.
  • RADIUS enforces device/data/session limits.
  • A RADIUS adapter can call PaySpot APIs.

PaySpot-issued vouchers

RADIUS Voucher

  • PaySpot should generate voucher credentials.
  • RADIUS should enforce usage and accounting.
  • The hotspot accepts RADIUS username/password.

Guided local configuration

MikroTik Setup App

  • The tenant uses MikroTik HotSpot.
  • The phone can join the router's local network during setup.
  • PaySpot should install the portal and Starlink-safe RADIUS connection.

Recommended Omada Sequence

  1. 01 Choose Omada Cloud for the correct location in the onboarding wizard.
  2. 02 Sign in with the TP-Link ID for that location and complete MFA if requested.
  3. 03 Refresh the controller list, choose the exact controller, then bind the correct site.
  4. 04 Enable automatic refill for eligible plans after the connection is ready, if needed.
  5. 05 If users must buy while captive, configure the Omada Access List.
  6. 06 If the tenant wants a branded captive entry page, configure Custom Portal Page.