Regulatory Alignment: How Onboarding Head AI Keeps V-KYC / CIP Compliant with Fed / OCC

The Regulatory Landscape That V-KYC / CIP Operates In

Video-based Customer Identification Process (V-CIP), commonly known as V-KYC / CIP, was introduced by the Fed / OCC through an amendment to the KYC / CIP SR letter in January 2020. Since then, it has been subject to several rounds of clarification and modification — through the SR letter on KYC / CIP (Amendment) 2021, the digital lending guidelines of 2022 which added requirements for consent documentation in the lending context, and subsequent FAQs and clarificatory bulletins that carry operational force even though they are not formally titled as amendments.

The operational requirements that emerge from this body of regulation are precise and demanding. The V-KYC / CIP agent must hold a specific qualification. The session must be recorded in its entirety with a specific retention period. The customer's live photograph must be matched against the SSN / government ID image using a certified facial recognition system. The geolocation of the customer must be captured. The connection must meet a minimum quality standard. The consent for recording must be obtained and documented before the session begins. The KYC / CIP records must be stored in the US. And the entire process must be auditable to a regulator on demand.

Each of these requirements is a compliance checkpoint. Each has been clarified, modified, or supplemented since the original framework. Keeping a V-KYC / CIP process current against all of them — continuously, without waiting for the next inspection to reveal a gap — is the operational challenge the Onboarding Head AI is built to solve.

The V-KYC / CIP Compliance Checklist the AI Maintains

The Onboarding Head AI maintains a continuously updated V-KYC / CIP compliance checklist mapped against the live text of the KYC / CIP SR letter and all subsequent amendments. Every requirement is checked against the institution's current V-KYC / CIP implementation — in the vendor system, in the process documentation, and in the audit trail records. Status is updated automatically when a new bulletin is issued or when the institution's implementation changes.

How Each Fed / OCC Amendment Gets Absorbed Into the V-KYC / CIP Process

The regulatory change lifecycle for V-KYC / CIP compliance is identical to the broader bulletin absorption pipeline — but with two important additions specific to onboarding. First, every V-KYC / CIP-related regulatory change is assessed for its impact on the borrower experience before it is operationalised. A new requirement that would add a step to the V-KYC / CIP flow is accompanied by a UX impact assessment and a drop-off risk estimate. This prevents the common pattern of compliance changes being implemented without product review, creating unexpected conversion decline.

Second, regulatory changes to V-KYC / CIP requirements trigger an automatic vendor compliance check — verifying whether the current KYC / CIP vendor's system supports the new requirement. If a bulletin requires a new type of document to be captured or a new consent disclosure to be made before the session, the Onboarding Head AI checks the vendor API documentation and, if the vendor system does not yet support the requirement, raises a vendor escalation before the compliance deadline rather than after.

Before and After: The V-KYC / CIP Compliance Gap That Used to Exist