Step 3: Use IDV Method

šŸŽÆ Purpose

Executes the selected Identity Verification method to confirm the user's identity before allowing them to proceed to credential re-establishment.


šŸ”„ IDV Method Execution Process

šŸŽÆ Method-Specific Processing

Based on the method selected in Step 2, the system guides users through the appropriate identity verification process.


šŸ“Š IDV Method Implementations

1ļøāƒ£ Access Code Validation Execution

  • Process: Send OTP to registered email or SMS, user enters code
  • User Interface: Code entry screen with resend capability
  • Validation: Code verified against generated value and time window
  • Retry: Multiple attempts allowed within security limits

2ļøāƒ£ Mobile Push Verification Execution

  • Process: Send push notification to REL-ID mobile app
  • User Action: User approves or denies verification request on mobile device
  • Response: Mobile app sends cryptographic response to server
  • Validation: Response verified for authenticity and user approval

3ļøāƒ£ Security Q&A Execution

  • Process: Present user's pre-configured security questions
  • User Interface: Question and answer interface
  • Validation: Answers compared against stored responses
  • Security: Case-insensitive matching with multiple attempt limits

4ļøāƒ£ Server-Side Biometric Authentication

  • Process: Capture biometric sample from user
  • Comparison: Compare against server-stored biometric template
  • Validation: Biometric matching algorithm confirms identity
  • Security: High-security biometric verification process

5ļøāƒ£ Web IDV Execution

  • Process: Full document-based identity verification
  • Integration: Redirect to REL-ID IDV Web Server
  • Verification: Document capture, analysis, and comparison
  • Validation: KYC API compares provided data against stored information

šŸ–„ļø Method-Specific User Interfaces

šŸ“± Security Q&A Interface Example

šŸ”” Mobile Push Verification Interface


šŸ”„ Execution Flow Logic

āœ… Successful Verification Flow

āŒ Failed Verification Flow


šŸ”„ Retry and Alternative Logic

šŸ”„ Retry Capabilities

  • Same Method Retry: Users can retry the same IDV method if it fails
  • Attempt Limits: Each method has configurable retry limits
  • Alternative Selection: Users can return to method selection if multiple methods available
  • Support Escalation: Clear path to support when all methods fail

šŸ“Š Retry Scenarios

IDV MethodRetry CapabilityAlternative Action
Access CodeMultiple code entriesResend code option
Mobile PushRe-send push notificationTry different method
Security Q&ARe-answer questionsAdministrative reset
BiometricRe-capture biometricAlternative method
Web IDVRe-submit documentsManual verification

šŸ›”ļø Security Validation

šŸ”’ Verification Security

  • Method Integrity: Each method properly validated according to its security model
  • Attempt Limiting: Prevents brute force attacks on verification methods
  • Time Constraints: Appropriate time limits for each verification type
  • Audit Logging: All verification attempts properly logged

šŸ“Š Security Measures by Method

MethodSecurity MeasuresAttack Prevention
Access CodeTime limits, attempt limits, single useCode guessing, replay attacks
Mobile PushCryptographic validation, device bindingDevice spoofing, man-in-middle
Security Q&ACase-insensitive matching, attempt limitsBrute force, social engineering
BiometricTemplate matching, liveness detectionSpoofing, replay attacks
Web IDVDocument validation, data comparisonDocument fraud, identity theft

šŸŽÆ User Experience Features

šŸ“± User-Friendly Elements

  • Clear Instructions: Each method includes clear step-by-step guidance
  • Progress Indication: Users understand where they are in the process
  • Error Messages: Helpful error messages with guidance for resolution
  • Support Options: Contact information available for assistance

šŸ”„ Flexible Recovery

  • Method Switching: Users can change methods if current method fails
  • Multiple Attempts: Reasonable retry capabilities for transient failures
  • Alternative Paths: Various routes to successful identity verification
  • Support Integration: Clear escalation to human assistance

āš ļø Important Execution Notes

šŸ”§ Technical Requirements

  • Service Dependencies: Some methods depend on external services (SMS, email, KYC)
  • Device Requirements: Biometric and mobile methods require specific device capabilities
  • Configuration Dependencies: All methods require proper system configuration
  • Network Requirements: Some methods require reliable network connectivity

šŸŽÆ Success Criteria

  • Identity Confirmed: User identity successfully verified through chosen method
  • Security Standards: Verification meets organisational security requirements
  • Audit Trail: Complete record of verification process maintained
  • User Satisfaction: Process completed with minimal user friction