Phone number verification without SMS OTP

# Verify phone number ownership.
Without sending an SMS.

Your user sends one pre-filled WhatsApp message from their phone. You receive the verified number — no code to send, type or forward.

[Try the live demo](https://phone-verif.com/demo) [Read the docs](https://phone-verif.com/integration-guide)

[Get an API key — 100 free credits](https://phone-verif.com/auth) [Evaluate my use case](mailto:contact@phone-verif.com?subject=Evaluate%20my%20use%20case)

- No SMS sent or paid by you
- Nothing for the user to type
- Billed only on successful verifications

verification sessionpending

Scan with your phone for a real demo

0.0%

Full-flow conversion

Phone capture included

0.0s

Median time to verified

No number or code typed

0€

SMS spend, forever

The message is sent from the user

0+

Countries covered

Anywhere WhatsApp works

Measured on real production traffic, end to end ([methodology](https://phone-verif.com/articles/verification-data-sms-vs-whatsapp))

How it works

## Three steps. Zero friction.

Classic OTP pushes a secret to the user and hopes it comes back. Phone-Verif pulls the verified phone number from the user. 
The proof is a message sent from the user’s own WhatsApp account, not a code that has to travel back.

what your server sees

$ curl "https://api.phone-verif.com/start-verification" \

-H "x-api-key: pv_live_9f2…"

{

"session_id": "b7e1-44c0",

"qr_code": "https://api.phone-verif.com/qr/b7e1…",

"whatsapp": { "deeplink": "https://wa.me/338…" }

}

No WhatsApp on the user’s phone? Offer Telegram through the API, or keep your SMS provider as a fallback for those sessions.

Why it’s different

## The OTP, reversed.

Twilio-era verification sends a secret to your user and bills you whether it arrives or not. We think it should work the other way around: the user sends, you receive, and you are only billed on success.

the incumbent pattern

### Push a code

1. User types their phone numbertypos, wrong-country formats
2. You pay a carrier to send a codebilled per attempt, delivered or not
3. The code crosses the SS7 networkinterception, SIM swap, AIT pump fraud
4. User waits, app-switches, memorizesthe drop-off moment
5. User types six digits backmistype → resend → repeat billing
6. You compare strings and hopea forwarded code passes this test

the reverse pattern

### Pull a proof

1. User taps the link or scans the QRnumber captured automatically
2. User presses send in WhatsAppproof arrives, session flips to verified

A code can be phished, forwarded or pumped for fraud. With a message sent from the number itself, there is no code to hand over. You’re not checking that someone knows a secret, you’re watching the phone speak for itself.

from 0.01€ per *successful* verification.
Failed attempts cost nothing, credits never expire.

Steps to verified

SMS OTP

6

Phone Verif

2

Secrets in transit

SMS OTP

1

Phone Verif

0

Typing required from user

SMS OTP

~16 chars

Phone Verif

none

Limits: the user needs WhatsApp on the phone that owns the number. For other users, Telegram is available through the API and SMS remains a useful fallback.

[Estimate your own costs with the SMS vs Phone-Verif calculator](https://phone-verif.com/articles/sms-verification-cost-calculator)

[Why SMS OTP bills keep exploding — AIT fraud, explained](https://phone-verif.com/articles/sms-costs-ait-fraud)

Use cases

## One primitive, every flow.

Proven possession of a phone number is the atom of digital identity. Everything you build on top of it is a composition.

### Signup

Capture and verify the number in one gesture. No phone field on your form at all.

### Passwordless login

The phone is the credential. One tap replaces password + OTP entirely.

### Two-factor auth

A second factor that can’t be phished, because there’s no code to hand over.

### Account recovery

Prove the returning user still holds the number before you hand back the keys.

### Fraud prevention

Burner-resistant by design — each proof is bound to a live WhatsApp identity.

### Transaction confirmation

High-stakes actions confirmed from the device that owns the number.

Case study

## Thousands of students, verified over WhatsApp.

Emy, an AI-powered learning platform, onboards Brazilian students for a national financial-literacy olympiad — every account phone-verified, no passwords, no SMS.

> “If your users are on WhatsApp, it's a no-brainer. The integration is dead simple — two API endpoints — the UX is far superior to SMS codes, and you get verified phone numbers as a bonus for your CRM. We went from zero to production in a day.”

Pedro GayaLead Developer, Emy[Read the case study](https://phone-verif.com/articles/emy-whatsapp-verification-case-study)

63%

verification-to-registration conversion

against the 50% the team expected

1 day

from first API call to production

~100 lines of backend code in total

≈0

fraud attempts and login tickets

with cash prizes on the line

Developer workflow

## The entire API fits in your head.

Two endpoints: open a session, read the proof. No webhook contortions, no vendor SDK lock-in, no 40-page console. If you can call an HTTP API, you already know how this works.

terminal

```
# 1 — open a verification sessioncurl "https://api.phone-verif.com/start-verification" \  -H "x-api-key: pv_live_9f2…"# 2 — show the returned QR or deep link, then read the proofcurl "https://api.phone-verif.com/check-verification-status?session_id=b7e1-44c0" \  -H "x-api-key: pv_live_9f2…"# → { "status": "verified", "validated_phone_number": "+33612345647" }
```

Test mode included - run the full flow without spending a credit.

[Read the integration guide](https://phone-verif.com/integration-guide)

Building blocks

## Every surface, already built.

Web, mobile, kiosk, backend or no backend at all — each session exposes every surface at once. Start with one, adopt the rest without changing your integration.

### REST API

Two endpoints: one starts a session, one checks it. JSON in and out, key in a header. Everything below is built on this.

POST /start-verification

### Signed webhooks

Every status change is pushed to your backend the moment it happens, signed so you can verify it came from us. No polling loops.

X-Webhook-Signature: sha256=…

### Four flows, one integration

The same two endpoints run phone verification, passwordless login, 2FA and age verification. Switching use case is a query param, not a rewrite.

?flow=phone | login | 2fa | age

### QR code + deep link

Every session ships a ready-to-render QR image URL for desktop and a deep link that opens WhatsApp pre-filled on mobile.

<img src={session.qr_code} />

### Hosted flow

A verification page we run for you. Pass a callback URL, get the user redirected back verified. Works with zero backend.

?callback_url=…

### Stable user identity

Each verified number resolves to a stable user_id you can link to your own IDs — recognize returning users on every login after the first.

"is_new_user": false

Security & performance

## Less to intercept. Less to leak.

Most verification security is about protecting a secret in flight. Reverse verification removes the one-time code from the flow.

### No code to phish

Phishing an OTP requires an OTP. The proof message travels from your user to us — an attacker has nothing to ask their victim for.

### Possession, actually proven

The message originates from a WhatsApp account bound to the number over an end-to-end encrypted channel — not a string somebody typed into a form.

### No secrets at rest

There is no OTP table to breach. Sessions store status, timestamps and the validated number. API keys are stored as hashes, never in the clear.

### Minimal by design

We keep exactly what verification requires and nothing else — no contact upload, no address book access, no profile scraping.

FAQ

## The questions engineers actually ask.

More questions? [Full FAQ](https://phone-verif.com/faq) · [About us](https://phone-verif.com/about)

## Your first proof is
five minutes away.

Run the live demo against your own phone, grab a key, and delete the phone-number field from your signup form for good.

[Try the live demo](https://phone-verif.com/demo) [Get an API key](https://phone-verif.com/auth) [Evaluate my use case](mailto:contact@phone-verif.com?subject=Evaluate%20my%20use%20case)
