Does a code prove someone’s legal identity?

No. A one-time code primarily proves access to the selected destination at that time. Higher-assurance actions can need additional identity checks and authorization.

Can the customer choose email instead of SMS?

The hosted flow provides supported text, voice and email choices. Actual channel availability depends on the service and sender configuration.

Is Verify the same as AI order verification?

Verify can provide possession evidence as part of a larger workflow. Order access can also require order-specific checks and permissions. The application must decide what the verified result authorizes.

Where are the integration instructions?

The developer documentation covers Verify setup and supported API requests. Begin with a test flow, confirm the response handling and then connect it to the protected action.

How is Verify priced?

Verify has separate usage pricing shown in the workspace. Channel and sender costs can vary, so use the current price card rather than assuming the support subscription covers all verification traffic.

MESSAGE VERIFY

A simple code.A more confident next step.

Verify possession of a phone number or email address before moving a customer through a sensitive workflow. Give people supported alternatives and keep the check inside your application’s rules.

Start with Verify Explore Verify

Verify is a separate usage-based product. Channel availability, sender setup and delivery fees apply.

Text, voice and email optionsScoped API accessServer-side verification

01 / The verification flow

Prove access before you proceed.

A typed email address or phone number is a claim. A completed verification gives your application evidence that the person can receive a code at that destination.

Start a verification

Your application requests the supported verification method for the intended destination. Use the appropriate service configuration and keep the API credential on your server.

Give the customer a clear choice

The hosted screen offers text message, voice call and email options. Explain what the code is for and let the person use a supported alternative when one channel is unavailable.

Check the result on the server

Validate the submitted code through the verification flow. Your application should inspect the verified result before proceeding, rather than trusting a browser message or an unchecked form field.

02 / Your application rules

Verification is evidence. You decide what it unlocks.

The right security decision depends on the action. Receiving a code does not make a person the owner of every record with a similar name.

Bind the check to the task

Use verification for the specific session, destination and action you intended. An old result from a different flow should not become a universal pass for future requests.

Add a second check when needed

Sensitive order access may also require matching order details such as an order number and billing postal code. Combine the appropriate checks instead of using an email address alone.

Keep permissions separate

A verified destination does not grant administrative access or permission to read another customer’s information. Your backend must still enforce account ownership and authorization.

See verified AI order support

THE EVERYDAY DETAILS

A small step with important details.

Make verification understandable for customers and controllable for the people running the product.

Channel options

Offer supported text, voice and email verification paths. Configure sender and channel availability before presenting an option to customers.

Service configuration

Use service-level settings for the application’s verification behavior. Keep separate uses understandable so a change for one flow does not surprise another.

Attempt controls

Use the supported expiry, retry and fraud-control settings. Handle an invalid or expired code clearly without giving away whether unrelated customer accounts exist.

Delivery and status

Inspect the verification outcome and available events. A request to send a code and a successfully completed verification are different states.

Developer integration

Use the REST API and scoped credentials from your server. Check errors and status before allowing the next action, including when a delivery provider is unavailable.

Plugin workflows

Supported plugin flows can use Verify for customer checks and subscriber confirmation. Configure the specific integration rather than assuming every platform has identical verification support.

MAKE IT YOURS

Connect the check to a real decision.

Configure your service

Choose the intended use, supported channels and sender identity. Review delivery availability and the workspace’s current usage pricing.

Connect server and customer flow

Create the verification from your backend and present a clear code-entry or hosted flow. Keep credentials and authorization decisions off the client.

Test success and failure

Try a correct code, an incorrect code, expiry and retry. Confirm that a failed verification cannot accidentally unlock the protected action.

Better together.

SMS

Send useful updates and handle the replies.

Message AI

Give your team an assistant that knows your business.

Integrations

Connect the tools your business already uses.

BEFORE YOU START

A few useful answers.

Check the right thing.
Then move forward.