KYC Challenge

🧾 Silent KYC Challenge (Pre-login) – REL-ID IDV SDK

📌 Overview

A Silent KYC Challenge (Pre-login) is a background verification process configured on the REL-ID Gateway that automatically triggers before user login. It verifies a user's identity using already submitted KYC data—without requiring explicit user interaction.


🔐 Purpose

  • Frictionless onboarding
  • Preemptive KYC compliance
  • Minimize manual steps for returning users
  • Automatically validate existing KYC data

🧩 How It Works

  1. Configured by Admin

    • Admin sets up a silent KYC challenge (IDVActivatedCustomerKYC) in the Pre-Login Challenge Set within Gateway Manager.
  2. Triggered Automatically

    • When the app launches and initiates device activation or login flow, the SDK receives the configured challenge.
  3. Silent Verification

    • Uses previously uploaded selfie and documents for verification.
    • May silently prompt document revalidation in the background.
    • Invokes necessary callbacks if manual action is required.
  4. Outcome

    • On success: Proceeds to login/authentication or home screen.
    • On failure: Can trigger fallback flows (e.g., re-upload, support notification).

📌 Use Case Scenarios

  • Streamlined User Activation

🧠 Related Challenge IDs

Challenge IDDescription
IDVActivatedCustomerKYCFor verifying self-activated users
IDVAgentKYCforUserFor field agent-initiated KYC

📝 Summary

AttributeValue
TriggerBefore login (pre-auth)
InteractionNone or minimal
SDK RoleDetect & silently execute
Admin RoleConfigure in Gateway Manager

Workflow

  1. User completes document scan
  2. User completes Selfie capture
  3. SDK calls onIDVKYCProgress when The Kyc challenge in REL-ID Gateway Manager has been configured with challengeInfo with an identifier as “kyc_message” and a label which consists of an array of strings.Then the IDV SDK issues this callback to inform the app about the progress of the kyc challenge.
  4. SDK calls the next event in the IDV workflow, getIDVBiometricOptInConsent

flowchart TD
    A[📄 User completes document scan] --> B[🤳 User completes selfie capture]
    B --> C[📣 SDK triggers onIDVKYCProgress]
    C --> D[🧬 SDK triggers getIDVBiometricOptInConsent]