Post Login User KYC

🧾 Overview: Post-Login User KYC – REL-ID IDV SDK

📌 What is Post-Login KYC?

Post-login User KYC refers to identity verification initiated after the user has successfully logged into the application. It allows delayed or staged KYC collection and is typically used when:

• KYC was skipped during onboarding
• Regulatory refresh is needed
• Users trigger features that require verified identity

🎯 Benefits

• ✅ Progressive onboarding experience
• ✅ Complies with regulatory refresh cycles
• ✅ Unlocks gated features post-verification
• ✅ Reduces drop-off at initial sign-up

🔁 Typical Workflow

1. User Logs In

   • Standard authentication is completed.

2. KYC Requirement Check -- ??? How will user know they have to do KYC

   • App/server checks if KYC is required (based on policy, user state, or last KYC timestamp).

3. Trigger KYC Process

   • SDK APIs initiated based on the user flow:
     • initiateActivatedCustomerKYC() — for self-submission
     • initiateAgentKYCforUser() — for agent-led submission

4. Document & Selfie Capture

   • SDK optionally calls getIDVDocumentScanProcessStartConfirmation() if document is not yet captured.
   • SDK optionally calls getIDVSelfieProcessStartConfirmation if selfie is not stored on server.
   • SDK optionally calls getIDVBiometricOptInConsent to get consent from user to store selfie on server.

5. Result Handling

   • Capture outcome from:`
     • onIDVActivatedCustomerKYCResponse— for self-submission
     • onIDVAgentKYCResponse— for agent-led submission

🔧 APIs and Events

📲 Integration Scenarios

• Trigger from:
  • User dashboard
  • Access control checks (e.g. before fund transfer)
  • Scheduled KYC refresh workflows

🧠 Use Cases

• Banks verifying users before issuing services
• Telecom companies validating prepaid customers
• Loan applications verifying income/address proofs
• Periodic re-validation of user profiles (re-KYC)

📝 Notes

• Ensure the KYC module and relevant challenge categories are properly configured in the REL-ID Gateway Manager.
• Handle both success and failure states with appropriate fallbacks.