Fallback Flow

1. Overview

The fallback mechanism is designed to address situations where some users are unable to complete the primary verification process. In practice, around 1% of users may encounter issues such as device malfunctions (e.g., an unavailable camera) or browser compatibility problems, which prevent them from completing the verification smoothly. To ensure the process is not interrupted, the system provides a fallback solution to maintain a seamless user experience and improve the overall completion rate.

2. Fallback Scenarios

1. Camera Issues

1.No camera available on the PC
2.Camera is not functioning properly

2. Browser Issues

1.Browser does not support WebAssembly (WASM)

2.getUserMedia API is not supported

3. Fallback Flow

1. Fallback Flow Description

When a user cannot proceed with KYC on the current device due to one of the above issues, the system automatically navigates to the fallback page (on the primary device).

The user can then switch to another device—such as a smartphone or a system browser—to complete the KYC process (secondary device flow).
After the secondary device completes KYC:

The primary device will automatically detect the completion and proceed with the remaining steps.
The secondary device will simply show a success message and will not redirect further.

2. Fallback Example

In the eKYC process, a camera issue was encountered, and the user was redirected to the fallback page.

After scanning the QR code with a mobile device, the primary device shows a “Processing” status.

Upon completion, the primary device displays the result and proceeds with the next steps.