Verify every user, on the channel that reaches them.

Send one-time passwords by SMS, WhatsApp, Telegram or voice — or verify silently through the mobile network. If one channel fails, the next one sends.

SPECIFICATION
CHANNELS
SMS · WhatsApp · Telegram · Voice
API
POST /api/v1/otp · /otp/verify
FALLBACK
Second route, one retry
THROTTLE
5 codes per number per day
BILLING
Each send at its own route’s price
[01] Codes on every phone

SMS OTP

One-time passwords by SMS reach every phone, with no app needed. Send the code and check it with two API calls; your registered Sender ID shows as the sender.

Why use it
Works on every phone
Your brand name as the sender
Delivery receipt for every code
Fallback to WhatsApp if it doesn’t arrive
Talk to sales about SMS OTP →
[02] Codes inside WhatsApp

WhatsApp OTP

One-time passwords delivered in WhatsApp, from your verified business profile. Charged only when delivered, with read status.

Why use it
Arrives in the app people already open
Charged only when delivered
Verified business profile
Fallback to SMS if needed
Talk to sales about WhatsApp OTP →
[03] Codes inside Telegram

Telegram OTP

One-time passwords delivered in Telegram to users who have it. Useful as a low-cost first channel with SMS as the fallback.

Why use it
Low-cost delivery
Reaches Telegram users instantly
Combine with SMS fallback
Same verify call as other channels
Talk to sales about Telegram OTP →
[04] Codes read out in a call

Voice OTP

The code is read out in an automated call — for landlines, basic phones or users who can’t receive texts. Often used as the last fallback.

Why use it
Works on landlines
Accessible for users who don’t read texts
A reliable last fallback
Same verify call as other channels
Talk to sales about voice OTP →
[05] Seamless authentication

Mobile Network Verification

Confirms the user’s phone number directly with the mobile network, in the background — no code to receive or type. The user taps Continue and is verified in a moment.

Why use it
Nothing for the user to type
Fewer drop-offs at sign-up
Resistant to code interception
Falls back to an OTP when unavailable
Talk to sales about network verification →
[06] Fallback across channels

Hybrid Authentication

Combine channels: try one first, and if it fails or isn’t delivered in time, send the same code once on a second route. You switch the fallback on or off per gateway, and choose the wait time.

Why use it
Higher success than any single channel
You choose the order and the wait
Each send charged at its own route’s price
One verify call, whichever channel delivered
Talk to sales about hybrid authentication →

Plan your authentication setup with us.

Routes, sender registration and pricing — agreed before you send.

Contact sales