Reverse SMS verification without sending a code

Confirm that a user controls a phone number by asking them to send a unique code from that phone to your receiving line.

View plans

The user sends an SMS from their own phone

Unique, time-limited codes

Status checks and webhook updates

Available through the included API

How reverse verification works

Your application creates a verification and receives a temporary code and destination number. The user sends the code from the phone being verified. GOnumera matches the sender, code and application to confirm the result.

Your system does not send an outgoing SMS for this attempt. The user’s carrier may charge for the message they send.

For sign-ups and sensitive actions

Use it in registration, access recovery and workflows that need evidence of phone access.

Show the destination number, exact code and time remaining clearly. Provide an alternative when a carrier delays or rejects a message.

A separate verification for every application

Applications use their own credentials. Codes expire, attempts are limited and results can be delivered to the application’s webhook.

Verification confirms temporary control of a phone number. It does not replace identity or risk checks required by your business.

Frequently asked questions

Who sends the SMS?

The user sends it from the phone they want to verify to the destination shown in your application.

Do I need a separate line for every project?

Not necessarily. One assigned line can serve multiple applications with separate credentials and verification sessions.

How does my system get the result?

Check verification status through the API or receive an event at your application’s webhook.