KYC / CDD Verification Agent AI

Invoked when: applicant submits Emirates ID / Iqama and consent for identity verification during onboarding

• –Verifies the Emirates ID / Iqama via UAE PASS and ICA (UAE) or ABSHER (Saudi) — confirming the ID is valid and matches applicant name and date of birth. Liveness detection confirms physical presence. A successful authentication confirms the Emirates ID / Iqama 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 Emirates ID / Iqama was authenticated — that is the role of liveness detection in the Fraud Detection Agent AI.
• –Validates Emirates ID / Iqama against ICA or ABSHER records and cross-checks against submitted documents.
• –Cross-checks name and date of birth across Emirates ID / Iqama, salary certificates, and employer records.
• –Does not store unnecessary biometric data beyond what UAE PDPL and CBUAE requirements permit. Only verification outcomes are retained.

Invoked when: SSN or customer identifier is available — prior CIP record check runs before requesting fresh KYC / CDD documents

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

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

• –Reads the structured output from the Video KYC / CDD Moderator AI — session pass/refer verdict, compliance checklist outcome, face match result, liveness check outcome, and any moderator notes — and integrates it with the Emirates ID / Iqama verification results and prior KYC match results to produce a complete KYC / CDD file status.
• –Checks that the VKYC session outcome satisfies the CBUAE / SAMA 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 / CDD 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 / CDD category. Flags these as open items before the KYC / CDD file can be considered complete.