Testing +268 Verification Flows Without a SIM in Mbabane

Why is a +268 sign-up so hard to test from abroad?

Eswatini is a small market, and that is exactly the problem for distributed teams. Your product may already serve customers in Manzini or Mbabane through a Southern African rollout, yet nobody on the QA bench owns a local SIM, roaming is unreliable for automation, and asking a colleague in the region to forward codes by chat does not scale past a handful of runs.

The usual result is that the +268 path in the phone-number field never gets exercised end to end. Validation rules, country pickers and SMS templates for the kingdom ship untested, and the first real user becomes the test case. OTP Route closes that gap by giving the test a real Eswatini verification number for one code, then handing the code back to your code.

Which services can receive codes on an Eswatini route?

The OTP Gateway currently lists more than 900 services for Eswatini. Popular ones in today's snapshot include WhatsApp, Facebook, Google (Gmail & YouTube), Instagram, TikTok, Signal, Microsoft & Outlook, LinkedIn, Uber, Amazon, imo, Netflix and ChatGPT (OpenAI).

Availability on any given route moves during the day as carrier partners add and retire capacity, so treat that list as a starting point. The live answer always comes from GET /api/v1/services and GET /api/v1/countries, and the dashboard shows the same picture before you commit funds.

How does the Eswatini OTP API flow work in code?

Create a Bearer key (prefix or_live_) in the Developer console, then call the base URL https://otproute.com/api/v1. A typical test step looks like this:

1. Call GET /api/v1/prices?country=sz&service=whatsapp to read the live price for that pairing.
2. Send POST /api/v1/activations with a JSON body naming the service and sz as the country. The response carries the activation id and the +268 number.
3. Enter that number in the sign-up form your test is driving.
4. Wait for the activation.sms_received webhook, or poll GET /api/v1/activations/{id} until the code appears.
5. If the scenario is abandoned, call POST /api/v1/activations/{id}/cancel so the wallet is credited at once.

Webhook requests carry an X-OTPRoute-Signature header. Recompute the HMAC-SHA256 over the timestamp and raw body with your endpoint secret, reject stale timestamps, and key every event on the activation id so retries stay harmless. The webhook capture guide walks through a full handler, and the API reference lists every endpoint.

What should engineers know about Eswatini phone numbers?

Eswatini uses the country code +268 with eight-digit national numbers and no trunk prefix, so there is no leading zero to strip. That makes normalisation simpler than in many markets: store the value in E.164 as +268 followed by the eight digits, and reject inputs with a different digit count before they reach your SMS provider.

The official languages are siSwati and English. International platforms normally send verification texts for this market in English, which keeps code-extraction regexes predictable, but your own templates may be localised, so assert on the digits rather than on surrounding wording. Teams usually test here when a Southern African launch includes the kingdom alongside South Africa, or when regional operations staff need business accounts tied to a local number.

What if the +268 code never shows up?

Small routes can be quieter than large ones, so plan for the occasional empty activation:

• Let the 20-minute window run. Some services queue messages before sending them.
• Check acceptance. Certain platforms decline virtual numbers on some routes; that is why an unused activation is refunded in full.
• Retry later or switch route. Try again after a pause, or test the same flow on a neighbouring route such as South Africa.
• Avoid tight loops. Re-ordering immediately after a failure rarely helps and burns test time.

The failed-delivery checklist has more diagnostics.

Can I keep a long-term Eswatini number?

Not through self-service. OTP Route offers Dedicated Virtual Numbers only in the United States and Canada, from $1.95/month, with inbound SMS, outbound SMS and browser calling. There is no self-serve long-term +268 line. If your operations team needs one, email [email protected] and the team will check what local rules allow; availability is not assured. For repeat logins on a staging account, a US or Canadian dedicated line is often the practical substitute.

How is OTP routing for Eswatini billed?

Spending for +268 tests comes out of a single prepaid USD balance; nothing is billed monthly and there are no tiers to compare. Card payments and USDT/USDC stablecoins both fund it, and each top-up triggers an emailed PDF invoice for your finance records. You are only charged when a code is delivered. For integration work, ask support to switch a development account to sandbox, which returns simulated numbers and codes so your CI suite can run without touching wallet funds. Full details sit on the pricing page. Please follow each service's terms; the OTP Route Acceptable Use Policy applies to every activation.

Frequently asked questions

Can I test my app's Eswatini sign-up without a local SIM?

Yes. Order an activation for country sz, enter the +268 number in your form, and read the code from the dashboard, a poll or a webhook.

Do Eswatini numbers have a leading zero to remove?

No. Eswatini has no trunk prefix, so the E.164 form is simply +268 followed by the eight-digit national number.

What does an Eswatini verification number cost?

Codes start from $0.20 per code; the exact figure for each service is returned by GET /api/v1/prices and shown in the dashboard before you order.

What language will the OTP text be in?

Most international services send English for this market, though wording varies by platform. Parse the numeric code rather than matching fixed sentences.

Is the money lost if the SMS fails?

No. If no code arrives inside 20 minutes, or you cancel first, the full amount returns to your wallet automatically.

Which route should I try if Eswatini is quiet?

Many teams fall back to South Africa or Mozambique for regional coverage while the +268 route recovers.

Can I run these tests in CI without spending funds?

Yes. A development account can be moved to sandbox on request, returning simulated numbers and codes for end-to-end pipeline tests.

Service names are trademarks of their respective owners. OTP Route is not affiliated with them. Use numbers lawfully, follow each service's terms and our Acceptable Use Policy.