KYC Lite Flow

Current Flow Version - v1.2

Available Since - 1 Mar 2026

Overview

KYC Lite is an optimized onboarding solution designed for organizations that require a high degree of identity assurance without the latency or procedural complexity of national registry queries. It seamlessly integrates KTP Scan and Face Verification into a single user journey. By automating the extraction of ID data, ensuring the physical presence of the user at the moment of capture, and biometrically comparing the user's live face against the KTP portrait, this solution provides a high-confidence "consistency check." It effectively guarantees that the presenter of the ID card is the legitimate owner of that document, operating entirely within your platform's environment without requiring external government database dependencies.

Common Use Case

E-Commerce Marketplace Vendor Verification
While casual buyers might only need OTP-based logins, verifying the identity of vendors (sellers) on an e-commerce marketplace is crucial to mitigating fraud and scams. Implementing Biometric Onboarding ensures that the business owner opening the merchant account is who they claim to be based on their KTP. This provides a layer of trust and accountability on the platform while capturing accurate seller data, without adding the heavy friction of the full vKYC process.
Visitor Management & Secure Entry
For commercial real estate, corporate offices, or high-security facilities, traditional sign-in sheets are insecure and prone to error. Digital Visitor Management Systems can utilize Biometric Onboarding at kiosk check-ins. The visitor scans their KTP and performs a live liveness check. This guarantees accurate data capture for security logs and biometrically verifies that the individual entering the premises matches the identity document presented.

High Level Flow

Web SDK (H5) Flow

    sequenceDiagram
    autonumber
    actor User    
    participant PWA as Partner Web App
    participant PBE as Partner Backend

    box rgb(240, 240, 240) IAB
        participant WA as IAB Web App<br>(Mobile/Tablet/Desktop)
        participant WA_Mobile as IAB Web App<br>(Mobile)
        participant BE as IAB Backend
    end

    rect rgb(230, 245, 255)
        Note over PWA, BE: Initialization
        PWA->>PBE: Get launch URL
        PBE->>BE: Get launch URL for user with required params
        BE-->>PBE: Launch URL
        PBE-->>PWA: Launch URL
    end


    rect rgb(235, 230, 255)
        Note over PWA, BE: Capture image and Submission processing
        PWA->>WA: Invoke flow
    alt Device Have Camera
        rect rgb(2255, 245, 230)
            note over WA: Capture image(s)
            WA->>BE: Start submission processing
            note over BE: Submission Processing
            note over WA: Status Polling
            WA->>WA: Do next action:<br>- RETRY (From Capture Image)<br>- STATUS (Show IAB status screen)<br>- EXIT (Completed)
        end

    else Device doesn't have any camera
        rect rgb(254, 249, 235)
            note over WA: Display QR code on the screen
            User->>WA_Mobile: Scan QR code and open FR flow
            note over WA_Mobile: Capture image(s)
            WA_Mobile->>BE: Start submission processing
            note over BE: Submission Processing
            note over WA_Mobile: Status Polling
            WA_Mobile->>WA_Mobile: Do next action:<br>- RETRY (From Capture Image)<br>- STATUS (Show IAB status screen)<br>- EXIT (Completed)

            WA->>WA: Do next action:<br>- STATUS (Show IAB status screen)<br>- EXIT (Completed)
            User->>WA: Clicks CTA on success/error screen (when nextAction is STATUS)
            WA->>PWA: Sends callback to partner with status=COMPLETED/ERROR and error_code
        end
    end

    rect rgb(230, 245, 255)
        Note over PWA, BE: Get Result Details
        BE->>PBE: Submission Processing Compete Callback
        PWA->>PBE: Call "Get Submission Details" API <br/>(correlationId aka partner session id)
        PBE->>BE: Call "Get Submission Details" API (correlationId, partner token)
        BE-->>PBE: return submission details
        PBE-->>PWA: Continue processing
    end

    Note over PWA: Show/process result
    end

Detailed Steps:

Partner BE calls the Generate Partner Token API on IAB BE to generate partner token, with client-id and pass-key provided by IAB.
- This API returns a partner token along with its validity in response. Partner BE can use the same partner token for making multiple requests as long as the token is valid.
- Once the token gets expired, partner BE can generate a new token using the same API.
- This token needs to be passed in all subsequent API calls to IAB BE for authentication and authorisation.
Partner BE calls the Initiate Flow API on IAB BE to generate the launch URL which will open the IAB flow. This API exposes several configuration parameters which allows the partner to customise the flow as per their requirements for which you can refer to the Web SDK Guide mentioned under the Integration Contracts section.
The IAB supports two modes: launching the flow directly on the device, or displaying a QR code (Smart QR Mode) for the user to continue on a mobile device.
- Smart QR mode is disabled (Default): The user proceeds directly to the flow.
- Smart QR mode is enabled: the IAB FE detects whether the user's device has a camera.
  - Device has a camera:
    - The user proceeds to the onboarding screen of the corresponding flow.
    - The IAB FE captures the user's image(s) and uploads them to the IAB BE for processing.
  - Device does not have a camera:
    - The IAB FE displays a QR code on the screen.
    - The user scans the QR code with a mobile device and completes the flow in their mobile browser.
    - The IAB FE captures the user's image(s) from the mobile device and uploads them to the IAB BE for processing.
For processing the image(s), partner needs to expose an API which IAB BE will call to get the reference Image. The image(s) captured by IAB FE will be compared against this reference image.
IAB web app will poll IAB BE until the processing is done and show loader to the user in the meantime.
Once the processing is done, IAB BE will return the relevant next action to IAB FE.

Partner can set custom success / failure page when the process is done
If not set, IAB will use default success / failure page for IAB Web SDK.

To get the result of the submission, the Partner BE will call the Get Submission Details API on the IAB BE with the following relevant inputs:
- x-partner-session-id
- x-partner-user-id
- x-partner-user-id-type
- x-onekyc-token (partner token)
IAB BE will return the submission result to partner BE.

Integration Contracts

Document Name	Link
BE API Guide	BE API Guide
Web SDK Guide	Web SDK Guide

Updated 8 days ago