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
-
Configured by Admin
- Admin sets up a silent KYC challenge (
IDVActivatedCustomerKYC) in the Pre-Login Challenge Set within Gateway Manager.
- Admin sets up a silent KYC challenge (
-
Triggered Automatically
- When the app launches and initiates device activation or login flow, the SDK receives the configured challenge.
-
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.
-
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 ID | Description |
|---|---|
IDVActivatedCustomerKYC | For verifying self-activated users |
IDVAgentKYCforUser | For field agent-initiated KYC |
📝 Summary
| Attribute | Value |
|---|---|
| Trigger | Before login (pre-auth) |
| Interaction | None or minimal |
| SDK Role | Detect & silently execute |
| Admin Role | Configure in Gateway Manager |
Workflow
- User completes document scan
- User completes Selfie capture
- SDK calls
onIDVKYCProgresswhen 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. - 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]Updated 6 months ago
What’s Next
