Mobile
Verification via the Mobile involves the process use of mobile devices, such as smartphones, as a means to confirm a user's identity and grant them access to the application using the ezto verify's mobile app.
Every application execution requires an Onboarding and Verification workflow. The onboarding workflow (can be any) will be used for a new user. You can configure it as "None" for a user who has already been onboarded. Please note that selecting the "None" option for the onboarding workflow will automatically redirect the user to the verification workflow, irrespective of the users availability.
Access Application
1 Navigate to Workspace, and click on Applications.
2 Choose the application you wish to execute the flow with configuration as Mobile.
3 Click on the Configuration tab, and select Mobile in the Verification Way.
4 You will be displayed with default settings, i.e, Link Expiry and Notification Type , you can select your preferred Notification Type from the drop-down and based on the chosen, the configurations will vary.
There is currently two methods of Notification Type available for "Mobile" Verification Way.
- Push
- QR
If this method is selected as the Notification Type, the verification will be sent as a push notification to the registered mobile device.
Push notifications are supported by both Firebase and HMS.
Push settings
(*) Indicates an action to be mandatory.
| Name | Description |
|---|---|
| *Mobile App Integration Type | Choose how you want to integrate verification. Select "SDK" if you intend to integrate with your own app, or choose "ezto verify app" if you prefer to use our official app from app stores. |
| *Push Notification Title | Specify the title for the push notification that will be displayed on the app side. |
| *Push Notification Body | Provide the content for the push notification message. |
| Enable Proximity (BETA) | Turn this on to verify the proximity of devices. This feature is currently supported only for the Web to Device flow. |
| Encryption | Enable this option to encrypt the payload sent to the mobile SDK for secure data transmission. |
If this method is selected as the Notification Type, the verification will be sent as a QR code to the registered mobile device.
QR settings
(*) Indicates an action to be mandatory.
| Name | Description |
|---|---|
| *Mobile App Integration Type | Choose how you want to integrate verification. Select "SDK" if you intend to integrate with your own app, or choose "ezto verify app" if you prefer to use our official app from app stores. |
| Enable Proximity (BETA) | Turn this on to verify the proximity of devices. This feature is currently supported only for the Web to Device flow. |
| Encryption | Enable this option to encrypt the payload sent to the mobile SDK for secure data transmission. |
5 After configuring the required Verification Way, ensure to SAVE the configurations.
6 Then, configure the Result Notification Way. This is necessary to proceed further in order to obtain the desired result or response. To know in detail, see here.
How it works,
- Make sure your required workflow is set before starting with the execution process in order to get the expected result.
- To initiate the execution process, go to the How to use? tab within the Application. You'll see the steps laid out for you to follow, or can simply test the flow using the test mode.
1 Launch Postman or your preferred API tool and execute the flow by configuring the suitable Method, URL, and Body settings.
2 Upon initiating the API call, a verification request will be sent to your configured Verification Way settings.
3 Based on the request, execute the flow in an incognito browser and follow the prompts to complete the verification process.
4 After completing the verification process, view the exact response type for the configured Result Notification Type, refer here.
Note that, the results will be different based on the configured Result Notification Type.
5 To view a sample response for Mobile Verification Way, refer to our API Builder.