OTPLess

The Verify Phone process typically involves verifying a user's phone number through OTPLess verification.

Prerequisites

• Download the ezto verify mobile app before proceeding with the flow.

How to setup,

1 Go to Workspace > Workflows, and click on the flow created for Verify Phone. If you need understanding in creating a workflow, refer to the step-by-step guide here.

2 Hover over the plus (+) symbol and select Workflow. From the list, click Verify Phone to add it.

3 Click on the newly added workflow, then select the General tab to customize your preferences.

Manage General

Name	Description
Enable	This toggle is enabled by default. When enabled, the particular workflow module begins its execution. Conversely, if disabled, the workflow module remains inactive and won't proceed.
Rule	This determines the criteria for triggering the particular workflow module. When the selected rule is evaluated, and is satisfied, the workflow proceeds as provided. If not, the workflow will not be executed. Note: If no rules are set, the workflow defaults to its standard action without any rule. For more information about the rules, refer here.

4 Then, click on the Configs tab to set the necessary configurations. When configuring the Verification Type, by default OTP is set, but there are two types available: OTP and OTP_LESS.

5 Choose OTP_Less for Verification Type.

Manage Configs

Name	Description
OTP Less Fallback	OTPLess is supported exclusively in the India region. When OTPLess fails, if the fallback method is enabled, it will switch to OTP verification, and the provider supported for this fallback is Twilio.

5 After you've configured everything needed, click on the SAVE button.

6 Proceed to attach the workflow to the relevant application for execution. Refer to instructions on how to attach a workflow to an application here.

Expected result

Based on the provided configuration, the information that will be fetched for Verify Phone with OTPLess includes the following parameters:

Name	Description
remote_addr	This refers to the remote address from which the request originated. In this case, it is the IP address of the remote device.
device_match	It indicates whether there is a match with the device information provided.
phone_verified	This denotes whether the phone verification is completed. The value will be "True" if the verification is successfully completed and "False" if it is not.
phone_verified_at	This provides a timestamp, in Unix epoch format, indicating the exact time when the phone number verification was completed. This allows you to know precisely when the verification event occurred.
phone_number	Refers to the phone number being validated or verified.

The response received will include the accurate information mentioned above. Note that, the response values can vary depending on the specific workflow modules.

How it works,

1 Launch Postman or your preferred API tool and execute the flow by configuring the suitable Method, URL, and Body settings. If you're seeking guidance on how to perform these actions, see here.

2 Upon initiating the API call, a verification request will be sent to your configured Verification Way (Mobile) settings.

3 Based on the request, execute the flow in an incognito browser and follow the prompts to complete the verification process.

4 Begin by scanning the QR code with the ezto verify mobile app.

This depends on what you have configured for the mobile notification way, i.e, QR code or Push integration. To know the difference between QR code or Push, refer here.

5 Once you scan the QR code, proceed by providing the phone number.

Ensure that you provide the number associated with your mobile device.

6 If you're connected to an external network, you will be asked to switch to your mobile network to ensure the provided number matches the one on the device being used for verification.

7 The OTPLess verification process will take a few seconds to validate.

8 If the provided number is successfully validated against the one present in the device, the verification process will be completed.

7 The response can differ depending on the chosen Verification Way and Notification Way configurations. To know more, see here.

8 Here is a sample response for Verify Phone with OTPLess:

{
    "workflow": "verification",
    "user_id": "mark@gmail.com",
    "request_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx",
    "remote_addr": "000.000.000.000",
    "device_match": "true/false",
    "phone_verified": "true/false",
    "phone_verified_at": "1719569072",
    "phone_number": "9183xxxxxxxx",
}