Testing +596 phone verification for Martinique users

Why does Martinique break phone validation that only expects France?

Martinique is part of France and of the European Union, yet it has its own country calling code, +596, rather than +33. That combination produces a classic bug: a French product limits its phone field to +33, or a country picker hides Martinique under France, and customers on the island cannot finish signing up.

Local numbers follow the French ten-digit pattern with a trunk 0. Mobile numbers are usually written 0696 or 0697 followed by six digits, and landlines 0596. In E.164 the zero goes and the code is added, giving +596 696 xx xx xx for a mobile. Note the landline quirk: +596 596… repeats the digits, which some home-grown validators wrongly flag as a typo.

• Store +596 plus nine digits; add spacing only on screen.
• Strip the trunk zero when a user types 0696… with the island selected.
• Test that +596, Guadeloupe (+590) and French Guiana (+594) are each accepted as separate codes.

Who needs a +596 number for testing?

French is the official language and Martinican Creole is widely spoken, but verification texts from global apps nearly always come in French or English, depending on the account's locale. That makes Martinique a useful check for teams that already localise for France:

• French and EU launches that must treat overseas residents as domestic customers.
• Caribbean operations for travel, delivery and hospitality products used on the island.
• Regression suites covering phone parsing, SMS templates and recovery flows for less common calling codes.

The QA testing guide describes how to slot such checks into an existing pipeline.

What services can send a code to a Martinican number?

More than 600 services are available on the Martinique route. The current snapshot of popular ones includes WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, Microsoft & Outlook, Amazon, Discord, Snapchat, Airbnb, Uber and Netflix.

Availability shifts during the day, so read it from the API at the moment you need it rather than hard-coding it into a test plan.

How do I receive Martinique SMS OTP codes through the API?

Create a Bearer key (prefix or_live_) in the Developer console and point your client at https://otproute.com/api/v1. Martinique's country id is mq.

1. Check GET /api/v1/prices?country=mq&service=<id> for the live price and stock of the pair.
2. Order through POST /api/v1/activations with {"service": "airbnb", "country": "mq"} or whichever service you are testing.
3. Type the returned +596 number into your own app and trigger the code.
4. Receive it on a webhook subscribed to activation.sms_received, or poll GET /api/v1/activations/{id} every few seconds.
5. If the test ends early, release the activation with POST /api/v1/activations/{id}/cancel.

Verify every webhook before trusting it: the X-OTPRoute-Signature header holds t=<unix>,v1=<hex>, where v1 is HMAC-SHA256 of <t>.<raw body> keyed with the endpoint secret. Reject old timestamps and make the handler idempotent on the activation id. Full reference: developer docs.

Is there a dashboard path for non-developers?

Support agents and growth teams can run the same OTP routing from the browser. Sign up with email or Google, fund the wallet, select Martinique and the service, check the price shown, and confirm. The +596 number appears on screen, and the code is added to the same card once the SMS lands. The window is 20 minutes; with no SMS, or after a cancel, the money goes straight back to your balance.

What if a +596 verification code is late or missing?

Smaller routes can be quieter, so plan for it:

• Wait out the full window before deciding the attempt failed.
• Remember that a service may refuse virtual numbers; you are not charged when that happens.
• Retry after a pause, or use a nearby route such as Guadeloupe if your scenario permits.
• Avoid hammering the order endpoint; space retries out instead.

The failed-delivery checklist has more ideas. Follow each service's terms; the OTP Route Acceptable Use Policy applies.

Can I get a permanent Martinique number, and how do I pay?

Self-serve long-term numbers are not offered for Martinique. Dedicated lines exist only for the United States and Canada, from $1.95/month; for a Martinican line, write to [email protected], knowing that local rules decide what is possible.

Payment is one prepaid USD wallet with no subscription. Top up by card or with USDT/USDC, receive a PDF invoice for every top-up, and ask for sandbox mode on a development account if you want simulated numbers and codes while you wire up the integration.

Frequently asked questions

Is a Martinique number the same as a French +33 number?

No. Martinique uses its own calling code, +596, even though it is part of France, so your forms must accept it separately.

What does a Martinican mobile number look like in E.164?

Drop the leading zero and add the code: a number written 0696 xx xx xx becomes +596 696 xx xx xx.

Which country id do I send for Martinique?

Send mq as the country value in price queries and activation requests.

Can I check my booking app's Martinique sign-up without a local SIM?

Yes. Order a +596 number for that service from the OTP Gateway and read the code in the dashboard or via the API.

Do I pay for a +596 activation that never receives an SMS?

No. Expired and cancelled activations are refunded to the wallet in full; you pay only when the code arrives.

Does OTP Route sell long-term Martinique lines?

Not self-serve. Long-term dedicated numbers are a US and Canada product; email [email protected] to ask about Martinique.

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.