Vext Auth verifies every user.
Sub-800ms. 100% Inside Morocco.
The national multi-channel OTP verification engine engineered on bare-metal in Casablanca. Direct SS7 & SMPP carrier interconnects with Maroc Telecom (IAM), Orange Maroc, and Inwi, paired with Meta WhatsApp Cloud API and voice OTP fallbacks. Strict CNDP Law 09-08 compliance with zero overseas data transit.
Test instant verification over Moroccan carrier networks
Verified Client Journeys & Production Benchmarks
Direct audit metrics extracted from our Casablanca Cloudflare D1 cluster (smsmaroc-db). See how actual Moroccan startups, marketplaces, and enterprises onboarded and scaled with sub-second OTPs.
AtlasCraft Digital (Sanaa.ma)
How We Accurately Measure Time-to-Market
Clock starts at accounts.created_at and ends at first live SMS dispatch. Developer teams achieve full production integration in ~21 minutes.
Clock starts when the customer links their WABA via Meta Embedded Signup (accounts.custom_waba_connected_at). Pre-approved templates enable first OTP in < 4 minutes.
Developer Integration: 3 lines of code in your preferred stack
curl -X POST https://api.envoisms.ma/v1/verify/send \
-H "Authorization: Bearer smr_live_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"to": "+212661364375",
"channel": "sms",
"sender_id": "VextAuth"
}'Why Moroccan financial & enterprise institutions choose Vext Auth
Direct IAM, Orange & Inwi Links
Direct SMPP v3.4 binds to Moroccan mobile operators. Eliminates European multi-hop aggregators and latency drops.
Real-Time DLR Delivery Proof
Guaranteed delivery receipts (DLR) with carrier timestamps and cost reconciliation in every webhook callback. No phantom charges.
SMS → WhatsApp → Voice Fallback
If a customer is roaming or has no mobile reception, Vext Auth cascades instantly to WhatsApp OTP and then to Vext Voice call.
Bank Al-Maghrib & CNDP Law 09-08
Zero data egress. Encrypted citizen phone numbers and verification tokens stay 100% hosted inside Casablanca sovereign datacenters.
72-Hour Sender ID SLA
Fast-track Moroccan telco operator registration for your custom enterprise Sender ID under clear regulatory compliance.
< 1 Min Time-to-First-Send
Validated across production accounts: developers generate API keys and send live OTP verifications in under 60 seconds.
Sovereign Moroccan Pricing vs Foreign Aggregators
Frequently Asked Questions about Vext Auth / EnvoiSMS Verify
Q:Why is Vext Auth / EnvoiSMS Verify faster than Twilio or Infobip in Morocco?
Foreign aggregators route Moroccan OTPs through overseas European gateways and broker hops, causing average delivery times of 6.8 seconds and high drop-off during peak hours. Vext connects directly via SS7 and SMPP v3.4 to Maroc Telecom, Orange, and Inwi inside Casablanca, delivering verification codes in under 800ms.
Q:How does Vext Auth protect companies under Moroccan CNDP Law 09-08?
Routing citizen telephone numbers and authentication codes to foreign servers creates legal liability under Law 09-08 and Bank Al-Maghrib circulars. Vext operates on bare-metal infrastructure in Casablanca. All tokens are encrypted using local SHA-256 HMAC keys with zero data egress.
Q:How does the multi-channel cascade work?
You call a single /v1/verify/send endpoint. If the primary channel (e.g. SMS) does not return a verified delivery receipt within a configurable timeout (e.g. 15 seconds), the engine cascades automatically to WhatsApp OTP, and finally places a spoken Darija/French phone call via Vext Voice.
Q:How fast can our engineering team integrate the API?
Our production logs show an average time-to-first-API-send of under 60 seconds from key issuance. We provide turnkey SDKs for Python, Node.js, PHP, Go, and Laravel, plus standardized OpenAPI documentation.