KYC Verification Agent AI

Invoked when: applicant submits Aadhaar and PAN details during onboarding and provides OTP consent for Aadhaar authentication

• –Authenticates the Aadhaar number via the UIDAI OTP API — the applicant receives an OTP on their registered mobile, enters it in the journey, and the agent verifies the OTP with UIDAI. A successful authentication confirms the Aadhaar number is valid and belongs to the person who received the OTP on the registered mobile number. It does not verify that the person using the device is the person whose Aadhaar was authenticated — that is the role of liveness detection in the Fraud Detection Agent AI.
• –Validates the PAN against NSDL records: confirms the PAN is active (not deactivated or surrender-marked), retrieves the name as per PAN records, and checks whether the PAN is linked to the submitted Aadhaar number — which is a mandatory requirement under the Income Tax Act and a strong identity corroboration signal when the linkage is confirmed.
• –Cross-checks the name on the Aadhaar demographic data against the name on the PAN record and against the name on any other submitted document — salary slip, bank statement, or company registration. Minor name variations (initials vs full name, spelling transliterations) are classified as minor discrepancies requiring human review; material name mismatches (different names entirely) are classified as a verification failure.
• –Does not store Aadhaar biometric data. It uses the OTP-based authentication pathway, which does not involve fingerprint or iris data. The only Aadhaar data accessed is the demographic fields (name, date of birth, gender, address) returned by UIDAI on a successful OTP authentication — and only the verification outcome, not the full demographic data, is retained in the KYC record.

Invoked when: PAN number is available — CKYC check runs before requesting fresh KYC documents

• –Queries the CKYC registry with the applicant's PAN to check whether a CKYC record already exists from a prior interaction with another financial institution. If a CKYC record exists, it retrieves the KYC status (KYC-compliant / KYC-non-compliant), the KYC date, and the institution that performed the original KYC — reducing the need to collect and verify documents that have already been verified by another RE.
• –Compares the key demographic fields in the CKYC record (name, date of birth, address) against the applicant's current submission to detect material discrepancies — an address change since the original CKYC, a name change, or a date-of-birth mismatch. Minor discrepancies are flagged for the KYC officer to assess; material discrepancies require fresh verification regardless of CKYC status.
• –Determines whether the existing CKYC record satisfies LendingIQ's KYC requirements for the applicable customer category and product — because different products may require different KYC levels (simplified / normal / enhanced) and an existing CKYC record at a lower level does not satisfy a higher-level requirement.
• –If no CKYC record exists, the agent proceeds to fresh document collection and triggers the full verification suite. At the end of a successful fresh KYC, it produces the CKYC registration payload for the human KYC officer to submit to the CKYC registry — the submission itself is a human-authorised act.

Invoked when: Video KYC Moderator AI has completed a VKYC session and the outcome needs to be integrated into the overall KYC verification report

• –Reads the structured output from the Video KYC Moderator AI — session pass/refer verdict, compliance checklist outcome, face match result, liveness check outcome, and any moderator notes — and integrates it with the Aadhaar/PAN verification results and CKYC match results to produce a complete KYC file status.
• –Checks that the VKYC session outcome satisfies the RBI V-CIP (Video based Customer Identification Process) requirements for the applicable customer category: that the OVD presented during the session matches the OVD on file, that the customer's face was visible throughout, that the session was conducted in a single sitting without interruption, and that the date and time watermark from the VKYC system confirms the session was live.
• –Identifies any remaining KYC gaps that the VKYC session did not address — for example, a VKYC session that verified identity but did not collect the address proof separately required for the applicable KYC category. Flags these as open items before the KYC file can be considered complete.