Accept OTT Vouchers on Your Hotspot

Summary Let guests pay for Wi-Fi by redeeming an OTT prepaid voucher — the OTT Lesotho rail used across Southern Africa. Instead of a card checkout, the guest enters the 12‑digit PIN from a voucher they already own and MKController redeems it in real time, then releases internet access. OTT uses five credentials from your OTT reseller account (API base URL, API Username, API Password, API Key, and Vendor ID).

OTT is not a checkout — there is nothing for the guest to pay with on the portal. The guest already bought an OTT voucher through OTT’s retail network and simply redeems it on your hotspot:

• The guest picks a plan, then enters the voucher PIN and their mobile number.
• MKController validates the PIN, charges the plan price against the voucher, and connects the guest immediately (this is an on‑session flow, like a card — no waiting, no QR code).
• If the voucher is worth more than the plan, OTT keeps the leftover in the buyer’s OTT Vault and sends it to their mobile by SMS — that is why the mobile number is required.

OTT uses five fields, all from your OTT reseller account (not your OTT portal login):

Field in MKController	What it is	Example
API base URL	The OTT API endpoint	https://api.ottlesotho.com (production)
API Username	API user for Basic authentication	provided by OTT
API Password	API password for Basic authentication	provided by OTT
API Key	Key used to sign each request	provided by OTT
Vendor ID	Your OTT vendor identifier	defaults to 11 if left blank

The API Username / Password are not your OTT web‑portal login — they are separate API credentials issued by OTT. Ask your OTT account manager if you don’t have them.

1. Contact your OTT (OTT Lesotho) account manager or reseller support.
2. Request your API credentials: base URL, API Username, API Password, API Key, and Vendor ID.
3. Confirm which environment the credentials are for:
   • Sandbox / test: https://test-api.ottlesotho.com
   • Production: https://api.ottlesotho.com

Keep in mind:

• Use the exact base URL. It must start with https:// and, for testing, be test-api.ottlesotho.com (not test.ottlesotho.com). A wrong host is the most common cause of a connection error.
• IP allow‑list. If OTT restricts API access by IP, it must permit MKController’s servers — otherwise every request is rejected.
• Test vouchers. To try the flow end‑to‑end you need a real voucher PIN. In sandbox, ask OTT for provisioned test PINs — the sample PIN from the API docs is not a real voucher and will always be rejected.

1. Open Integrations → Payments.
2. Select the Payment gateways tab.
3. Find OTT and click Configure.
4. Fill in the five fields: API base URL, API Username, API Password, API Key, and Vendor ID (leave Vendor ID blank to use the default 11).
5. Click Test connection to check the credentials against OTT.
6. Click Validate and connect.

MKController verifies the credentials with OTT and enables the OTT Voucher method, shown as a chip on the OTT card.

1. Under Integrations → Payments, open the Payment methods tab.
2. Turn on OTT Voucher.

1. Open the voucher → Integrations tab.
2. Under Online payment, switch on OTT Voucher.
3. Save.

On the captive portal for that voucher, the guest now sees an OTT Voucher option. After choosing a plan they:

1. Enter the 12‑digit OTT voucher PIN.
2. Confirm their mobile number (pre‑filled if they already gave it).
3. Tap Redeem — access is upgraded to the plan they bought.

OTT charges in your OTT account’s currency (for OTT Lesotho, that is LSL). There is no conversion — the plan price is redeemed against the voucher as‑is. Make sure the plan price currency matches the currency of the vouchers your guests hold, and the portal reminds the guest to check this before redeeming.

• Redeem a real, low‑value OTT voucher from a device on the hotspot to confirm the full flow.
• Track redemptions in the voucher’s Real time screen — gateway and paid/pending status show per session.
• A voucher worth more than the plan leaves the remainder in the buyer’s OTT Vault (delivered by SMS) — confirm the guest received it.

MKController field	Where to get it
API base URL	OTT account manager (prod api.ottlesotho.com, sandbox test-api.ottlesotho.com)
API Username	OTT account manager (API credential, not portal login)
API Password	OTT account manager (API credential, not portal login)
API Key	OTT account manager
Vendor ID	OTT account manager (defaults to 11)

• “Invalid code.” The PIN is wrong, already used, expired, or not a real voucher. In sandbox, confirm you are using a provisioned test PIN from OTT — the docs’ sample PIN is not valid.
• “The voucher is worth less than the plan.” OTT vouchers are fixed‑value; the guest needs a voucher whose value is at least the plan price. Offer a cheaper plan or a higher‑value voucher.
• “Enter a valid mobile number.” The mobile is required — OTT sends any leftover balance there by SMS. Make sure the guest fills it in on the OTT screen.
• Connection error / test fails. Re‑check the API base URL (must be https:// and, for testing, test-api.ottlesotho.com), the API Username/Password (the API pair, not your portal login), and whether an IP restriction at OTT is blocking MKController’s servers.
• Rotate credentials? Ask OTT to issue new API credentials, then click Reconfigure on the OTT card and enter the new values.

---

Explore next: Configure Payment Gateways · Create Plans · How Guests Connect & Pay

Need a hand? Talk to our team on WhatsApp or start your free MKController account.