FAQs

How do we handle Aadhaar verification failures?

The workflow fails due to a Know Your Customer (KYC) failure. You can see the reason in the node's Instance results and in the Sessions dashboard in AdminX, along with the individual match indicators (name, date of birth, PIN code, face) that show which check didn't match.

What is the face-match threshold, and is it configurable?

The face match threshold is 0.7. A face_match_confidence score above 0.7 is accepted. Users and admins can't configure this threshold today because it is part of the workflow that runs on the root tenant.

Where does the liveness check get configured?

Liveness for the selfie capture step is configured at the root tenant level, not per workflow or per admin.

What happens if a user doesn't have a DigiLocker account?

The user can create one during the redirect. On the DigiLocker screen, they select Try another way, which takes them to DigiLocker's account-creation flow.

What happens if a user presents someone else's face during the selfie step?

The node still completes because it matches the name, date of birth, and PIN code independently of the face. Only the face match fails: face_match_result returns false with a face_match_confidence below the 0.7 threshold; the other match indicators (name, date of birth, address/PIN) can still return true and the overall outcome is Verification Failed.