Face Verification Flow - User Experience

GTF can provide support to ensure UI customizations align with the product design and theme of the client.

Native/Flutter

Step

Screen

Landing Page

Native Landing Screen

Face Scanning

Native Face Scanning Screen 1. Native Face Scanning Screen 2

Native Face Scanning Screen 3

Liveness

Native Liveness Screen

Upload and Verification to BE

Native Upload and Verification Screen

Face Verification Status screen

Success: Native Success Status
Failure: Native Failure Status

H5 (Web)

Face Verification Flow

The Face Verification flow can be launched in any of the following ways:

  • Directly in mobile/desktop browser from partner web application
  • Directly in mobile browser by scanning QR code
  • Within partner native app webview
  • Within iframe of partner web application in desktop browser

Step

Screen

Landing Page

H5 Landing Page Screen

Face Scanning

H5 Face Scanning 1H5 Face Scanning 2

Liveness

H5 Liveness

Upload and Verification to BE

H5 Upload verification

Face Verification Status screen (Success)

Face Verification Status screen (Failure)



QR Redirection Flow

When the QR flow is launched, the user can scan the QR code on the screen to launch the Face Verification flow in the mobile browser.

After the user completes Face Verification in the mobile browser, the status will be displayed on the primary device. On clicking the CTA to exit the flow, IAB will send a callback to the partner application. Alternatively, the partner may choose to have event-based redirection in which case the user will be auto-redirected to the partner upon completion without showing the IAB status screen.

StepScreen
Landing PageQR Landing
Submission processedQR Processing 1. QR Processing 2
QR code has expiredQR Expired
Error screenQR Error
No updateQR No Update