English
Sudanese Verification Numbers: Testing +249 Sign-Up Flows
OTP Route can receive Sudan (+249) verification codes on one-time numbers from its OTP Gateway, showing the code in the dashboard and delivering it to your backend by API polling or signed webhooks. Pricing starts from $0.20 per code, and if no SMS arrives within the 20-minute window, the money returns to your wallet. It is a practical way to check Arabic and English verification paths for Sudanese users.
What makes Sudanese numbers different to handle?
Sudan's country code is +249 and the domestic trunk prefix is 0. Mobile numbers have nine digits after the country code, so a local user may enter 0 plus nine digits while your database should hold +249 plus nine. Normalize on input: strip separators, remove the trunk 0 when a country code is present, and reject strings of the wrong length before they reach an SMS step. Keep the display formatter apart from the stored value so support staff see a readable number without altering the canonical one.
Will the code arrive in Arabic or English?
Both happen. Arabic and English are official languages, and senders choose a template from the account's language setting or their own defaults. Arabic SMS travels in Unicode (UCS-2) encoding, which fits fewer characters per segment, so a long Arabic template can be split into several parts. Some templates may also print the code in Eastern Arabic digits. A sturdy parser maps ٠١٢٣٤٥٦٧٨٩ to 0-9 before searching for the code and ignores the right-to-left wording around it.
Who tests sign-ups with a +249 number?
Product teams serving Sudanese customers, both at home and in the sizable communities abroad, need to know that their sign-up form accepts the prefix and that the SMS step completes. Remittance, messaging, education and support apps are common examples. Localization QA is another driver: an Arabic interface with a right-to-left layout can hide a phone-field bug that never shows up in English, and a Sudan verification number is the simplest way to reproduce it. The SaaS onboarding page outlines how teams structure these checks.
Which services are on the Sudan route?
The Sudan route covers more than 800 services. The current snapshot of popular ones includes WhatsApp, Telegram, imo, Facebook, Instagram, Google (Gmail & YouTube), TikTok, X (Twitter), Viber, Signal, Snapchat, Microsoft & Outlook and Claude. Coverage moves through the day as routes open and close, which is why OTP routing decisions belong in code: ask GET /api/v1/services and the prices endpoint first, then place the order.
How does the Sudan OTP API flow work?
Use sd as the country id. Call GET /api/v1/prices?country=sd&service=telegram to confirm the route and its price, then POST /api/v1/activations with the service and sd. Type the returned +249 number for testing into the app. When the text lands, OTP Route sends activation.sms_received to your webhook with an X-OTPRoute-Signature header; recompute the HMAC-SHA256 over the timestamp and raw body, compare, and discard old timestamps. If you would rather not expose an endpoint, poll GET /api/v1/activations/{id} from the same SMS verification API. More detail sits in securing OTP webhooks.
In the dashboard the same job takes a few clicks: open the OTP Gateway, choose the service, choose Sudan, accept the displayed price, copy the number and wait for the code to appear next to it.
What should I do when a Sudanese code is late?
Each activation stays open for 20 minutes. If the window closes with no SMS, or you cancel through POST /api/v1/activations/{id}/cancel, the full amount returns to your wallet. Some services refuse virtual numbers, so rule that out first. After that, wait out the current window, retry later or switch to another route for the same service, and avoid ordering again in a tight loop. When a test is not tied to the Sudanese market, a nearby route such as Egypt can stand in.
Long-term numbers, wallet and sandbox
OTP Route does not offer a self-serve long-term Sudanese number. Dedicated Virtual Numbers, from $1.95/month, are sold for the United States and Canada only; teams that need a +249 line can email [email protected], though the answer depends on local rules and nothing is assured. Everything else runs on a prepaid USD wallet with no plan or monthly fee, topped up by card or USDT/USDC, with PDF invoices by email. Sandbox mode, offered on request for development accounts, returns simulated numbers and codes for end-to-end tests, so a Khartoum-facing release can be rehearsed in staging before any real order is placed. When the build is ready, compare live rates on the pricing page and order only the routes your test plan names.
Frequently asked questions
Can I check my app's Sudanese sign-up flow without a local SIM card?
Yes. Order a +249 number from the OTP Gateway, enter it in your app, and read the code in the dashboard or through your webhook.
What is the API country id for Sudan?
It is sd. Service ids, such as whatsapp or imo, come from GET /api/v1/services.
Is South Sudan covered by the same route?
No. South Sudan has its own country code, +211, and a separate entry in the country list.
Am I charged if a Sudanese code never comes?
No. When the 20-minute window ends without an SMS, or you cancel, the full amount is credited back to your wallet automatically.
How should my parser treat Arabic verification messages?
Convert Eastern Arabic digits to ASCII first, then look for the run of digits that forms the code. Avoid matching on surrounding words, since they vary by template and language.
Can I fund the wallet with stablecoins?
Yes. The wallet takes card payments and USDT/USDC, and each top-up produces a PDF invoice by email.
Which uses are off limits?
Mass account creation, working around a service's restrictions, or anything against a service's terms. OTP Route is for testing and operating your own legitimate products and accounts.
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.