Configure KYC Flow in Gateway Console
🧩 Enable KYC Flow in Gateway Console
This guide explains how to enable and position the KYC challenge within the REL-ID authentication flow using the Gateway Management Console.
🔐 When Is KYC Triggered?
KYC is triggered during first-time activation or optionally in post-login workflows, depending on how you configure the challenge stack. You can enable or disable KYC based on policy.
🧭 Steps to Enable KYC Flow
🧷 Enable for First-Time Activation
- Login to REL-ID Gateway Management Console
- Navigate to Authentication Management
- Choose your relevant Policy or User Group
- Edit the Activation Flow (often named “First time activation”)
- Click + Add Challenge
- Select
RELID-IDV-KYC
- Place it before:
RELID-IDV-BiometricOptIn
- Or any other biometric setup steps
- Save the flow
- Restart the Blaze Server
The KYC challenge will now be executed right after document scan and face match.
🔄 Enable for Post Login (Optional)
If you wish to trigger KYC again during login (e.g., re-KYC every 6 months):
- Go to the Authentication Management section
- Edit the “Post Login” challenge stack
- Add the
RELID-IDV-KYC
challenge where needed - Configure any conditional logic or orchestration (if required)
- Save and Restart the Blaze Server
🔁 Recommended Challenge Order
Order | Challenge Name | Purpose |
---|---|---|
1 | RELID-IDV-DocScan | Capture ID document |
2 | RELID-IDV-SelfieCapture | Capture selfie |
3 | RELID-IDV-KYC | Send data to backend |
4 | RELID-IDV-BiometricOptIn | Enable biometric for future use |
🛡️ Tips
- You can create different activation flows for different user segments (e.g., low-risk vs high-risk users).
- KYC challenge can be used even without biometric opt-in, if the use case is just to validate identity.
- KYC can also be configured to work without user interaction, for example in silent background re-verification flows.
Updated 3 months ago