Testing Hungarian (+36) phone verification: checklist, steps and fixes

Checklist: is your stack ready for a Hungary OTP API run?

Run through this list once per project, not once per test:

1. Account security. Sign up at /signup, then enable TOTP two-factor before generating any keys.
2. Keys per environment. Create or_live_ keys in the Developer console, one per pipeline or developer machine, so a leaked key can be revoked without stopping everyone else.
3. Ids in config, not in code. Hungary is hu; read service ids from GET /api/v1/services and keep the mapping in a config file.
4. Webhook target. Register an HTTPS endpoint (up to 5 per account) and store its secret in your secrets manager.
5. Budget guard. Have the suite call GET /api/v1/balance first and exit cleanly when funds are short.
6. Region-aware parsing. Make sure your phone input knows region HU, because Hungarians rarely type the country code on a domestic form.

The QA testing solution page shows how teams usually lay this out in a test framework.

Why does +36 number handling deserve its own test cases?

Hungary's country code is +36, and the domestic trunk prefix is 06. A Hungarian user will often enter a mobile number as 06 30 123 4567 or 06 20 ..., where 20, 30, 31, 50 and 70 are common mobile prefixes. Your form must convert that into +3630... by removing the 06, never by keeping it after the country code. Write explicit cases for:

• 06 30 ... in a national-format field;
• +36 30 ... and 0036 30 ..., since 00 is the international access prefix;
• spaces, slashes and hyphens, which appear in every combination in real input.

Hungarian is the official language, and many services send their code in Hungarian once the account locale is set to it. The letters ő and ű are not part of the GSM 7-bit alphabet, so a Hungarian message containing them is encoded as UCS-2 and each segment carries fewer characters. That matters if your own product sends Hungarian codes, and it is a good reason to read the received text in your test logs rather than only the extracted digits. Hungarian words also run long, so localization QA should check that the phone step and its error messages still fit on small screens.

Which Hungarian routes are available for a +36 number for testing?

OTP routing for hu currently spans more than 1,600 services. Commonly requested routes in the current snapshot are WhatsApp, Viber, Facebook, Instagram, Google (Gmail & YouTube), Uber, Airbnb, eBay, Amazon, LinkedIn, Netflix and ChatGPT (OpenAI).

These routes are a snapshot; inventory moves throughout the day, which is why the API returns availability with every price request. Query GET /api/v1/prices?country=hu&service=<id> immediately before you order instead of caching an old answer.

Steps: receive Hungary SMS OTP codes through the API

With the checklist done, a single test through the SMS verification API needs five calls at most, all against https://otproute.com/api/v1:

1. GET /api/v1/prices?country=hu&service=uber to confirm the route and record the price.
2. POST /api/v1/activations with {"service": "uber", "country": "hu"}. Keep the activation id; it is the key for everything that follows.
3. Push the returned +36 number into your app's verification screen.
4. Receive the code. A webhook delivers activation.sms_received; polling uses GET /api/v1/activations/{id}. Pick one per job so the two paths do not race.
5. On a test failure, POST /api/v1/activations/{id}/cancel to release the funds immediately.

Verify every webhook before trusting it: split X-OTPRoute-Signature into t and v1, compute HMAC-SHA256 over <t>.<raw body> with the endpoint secret, compare in constant time and reject timestamps that are too old. Treat activation.expired and activation.cancelled as terminal states so retries stop. A worked example is in the OTP API integration guide.

Steps for colleagues who never touch the API

Customer success or marketing staff can use the dashboard. Open the OTP Gateway, choose Hungary and the service, check the displayed price, confirm, and paste the +36 number into the app. The code appears on the order itself. If nothing arrives inside 20 minutes, the order expires and the wallet is credited in full, so a failed attempt costs nothing.

Troubleshooting a Hungarian verification number that stays silent

Work through these before opening a ticket:

• Was the number submitted as E.164? A stray 06 after +36 is the most common self-inflicted failure.
• Does the service accept virtual numbers? Some do not. The automatic refund covers this, and switching to another service route or a neighbouring country is usually the fastest way forward.
• Did you wait out the window? Cancelling after a short wait can discard a code that was on its way. Let the order run, then retry later.
• Is the script hammering one route? Space retries out with a backoff. Repeated instant orders seldom help and can trip a platform's own abuse checks.

The article on reducing failed OTP deliveries goes further.

Long-term lines, wallet and responsible use in Hungary

There is no self-serve long-term number for Hungary. If an operations or support team needs one, write to [email protected] with the use case; availability depends on local rules and cannot be promised. Self-serve Dedicated Virtual Numbers exist only for US and Canadian lines, starting from $1.95/month.

OTP Route bills from one prepaid USD wallet: no monthly fee, no plan, top-ups by card or USDT/USDC, and a PDF invoice by email for each top-up. A sandbox mode with simulated numbers and codes can be enabled on request for integration tests. Use numbers only to test or operate your own products and legitimate accounts, respect each service's terms, and remember that OTP Route's Acceptable Use Policy applies.

Frequently asked questions

Can my QA team receive a Hungarian SMS code without a Hungarian SIM?

Yes. Order a +36 number for the relevant service through the OTP Gateway and collect the code in the dashboard or through the API.

What country id does the API use for Hungary?

Use hu, for example in POST /api/v1/activations with a body such as {"service": "uber", "country": "hu"}.

How do I convert a number written as 06 30 123 4567?

Drop the 06 trunk prefix and add +36, giving +36301234567. Store that E.164 form and only format it for display.

Do I pay if a Hungarian route does not deliver a code?

No. If no SMS arrives within 20 minutes, or you cancel, the full amount returns to your wallet automatically.

Why does a Hungarian code message sometimes look different from an English one?

Hungarian texts may include ő or ű, which push the message into UCS-2 encoding. The digits are the same; only the message text and its length change.

Can I buy a Hungarian number that I keep for months?

Not as a self-serve product. Dedicated Numbers are US and Canada only; for Hungary you can email [email protected] to ask, with no promise it can be arranged.

How many services does OTP Route support for Hungary?

More than 1,600 at the time of writing. Call GET /api/v1/countries or check the dashboard for the current list.

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.