Phone-Verif

Phone Verif is a WhatsApp-first phone verification API for products that need to confirm number ownership without relying on traditional SMS OTP codes. Instead of sending a verification code for users to enter, the service asks the user to send a WhatsApp message from their own number, then returns the validated phone number to your application.

The approach is designed to reduce verification friction while avoiding common problems associated with SMS delivery and code-based verification. The integration is intentionally small, making it suitable for backend services, mobile apps, kiosks, and hosted verification pages.

Key Features

WhatsApp-First Phone Verification

Phone Verif reverses the traditional OTP workflow.

Rather than sending a code to the user, the user sends the verification message from their own WhatsApp number. Your application then receives the validated phone number as proof of ownership.

This removes the need for users to:

• Wait for an SMS
• Receive and type an OTP
• Handle mistyped verification codes
• Forward or expose a verification code

Two-Endpoint API

The core integration uses two main endpoints:

• One endpoint to open a verification session
• One endpoint to check the verification result

This keeps the implementation compact enough for different product environments, from backend integrations and mobile apps to kiosks and hosted pages.

QR Codes & WhatsApp Deep Links

Give users multiple ways to begin verification.

Phone Verif provides:

• QR codes for desktop-oriented flows
• WhatsApp deep links for mobile users

This allows the verification experience to adapt to the device or interface where your product is being used.

Signed Webhooks

Receive verification status updates directly in your backend through signed webhooks.

This allows your application to react to verification events without repeatedly checking the service manually.

Hosted Verification Flow

You can use a hosted verification page instead of building the frontend experience yourself.

This provides a ready-made entry point for products that want to integrate phone verification without creating a dedicated verification interface.

Stable User ID Mapping

Verified phone numbers can resolve to a repeatable identity for returning users.

This provides a stable way to associate verified numbers with users across repeat verification flows.

Test Mode

Run through the complete verification experience without spending a credit.

Test mode provides a way for developers to integrate and validate the workflow before using it with real verification attempts.

Success-Only Billing

Phone Verif only charges for successful verification attempts.

Failed attempts do not consume credits, which makes the cost of verification more closely tied to successful outcomes.

Built For Developers & Product Teams

Phone Verif is designed for products that need reliable phone ownership verification without building around SMS OTP delivery.

It can fit:

• Backend applications integrating verification directly into an existing authentication flow
• Mobile apps using WhatsApp deep links
• Kiosks using QR-based verification
• Hosted products using the provided verification page
• Authentication systems implementing passwordless login or 2FA

Common Use Cases

• Phone number verification: Confirm that a user controls a specific WhatsApp number.
• Passwordless login: Use verified phone ownership as part of an authentication flow.
• Two-factor authentication: Add phone-based verification without relying on SMS codes.
• Mobile onboarding: Let users verify through a WhatsApp action rather than entering an OTP.
• Kiosk verification: Display a QR code for users to complete verification from their phone.
• Desktop verification: Use QR codes or deep links to connect a desktop session with a user's WhatsApp number.
• Hosted verification: Use the hosted flow when you do not want to build the frontend yourself.
• Developer testing: Validate the complete integration using test mode before consuming credits.

Why It Matters

SMS OTP verification adds several points of friction to an otherwise simple task. Messages can fail to arrive, codes can be mistyped, and code-based authentication creates an additional surface for phishing and forwarding.

Phone Verif takes a different approach by making the user's own WhatsApp message the verification action. The application starts a session, presents a QR code or deep link, and receives the validated number through the API or webhook.

For teams whose users already rely heavily on WhatsApp, this can make phone verification feel more like a direct proof of ownership than a traditional code exchange. The small API surface, hosted flow, signed webhooks, test mode, and success-only billing also keep the implementation focused on the verification itself.

Verify Phone Ownership Without SMS OTPs

Use WhatsApp messages, QR codes, or deep links to verify phone ownership with a compact API integration. Phone Verif provides the verification session, result handling, signed webhooks, hosted flow, and stable identity mapping needed to add phone verification, passwordless login, or 2FA without building around traditional SMS codes.