What is CKYC verification?
CKYC verification checks whether a customer already has a KYC record filed in India's central KYC records infrastructure, and retrieves the record where one exists.
Financial-sector businesses file the KYC records they collect into a shared registry, and an accepted record carries a unique fourteen-digit KYC identifier. When that customer approaches a different institution later, the second one can look for the existing record instead of starting from a blank form.
How the CKYC search and download work together
The workflow has two halves, and both belong in one integration. The search asks whether a record exists for the person in front of you and returns the identifier with the limited details you need to confirm the match. The download retrieves the stored record, and it needs the customer's authorization.
Through an API both halves sit inside your own journey. A branch application, a mobile journey or an operations dashboard can run the search while the customer is still in session. The flow continues to the download only where the customer authorizes it.
What a CKYC search starts from
A search usually starts from an identifier your flow has already collected. That can be a KYC identifier the customer supplies, or another permitted input such as PAN or a registered mobile number, depending on what the service contract supports.
The download then needs the customer's authorization. It may take the form of a one-time password sent to the mobile number registered against the record. Without it, no record is retrieved and your flow falls back to collecting KYC directly.
What a downloaded CKYC record can contain
A retrieved record can carry the identity and address details filed when KYC was originally completed. It can also carry the customer's photograph, references to the documents used, and the date it was last updated. The exact fields available vary by data source and by record.
A record can also be older than the customer's present circumstances, with an address since changed or a document since replaced. Compare it with what the customer tells you.
Who reuses a filed CKYC record
- Lending and NBFCs learn at application whether a borrower already has a filed record. Onboarding then moves toward underwriting instead of pausing for documents.
- Insurance reuses an existing record when a proposer buys a policy, without asking again for proofs already given elsewhere.
- Wealth, broking and fund distribution remove the most repeated paperwork, because investor onboarding is where a centrally held record does the most work.
- Fintech and payment service providers check for a record before starting a fresh KYC journey. They take the slower path only where it is needed.
- Housing finance retrieves stored details for applicants and co-applicants onboarded elsewhere, where the file waits on the slowest participant.
Planning the CKYC step in your onboarding journey
A search earns its place only where the result can still change what happens next. Put it early enough that a found record shortens the path and an empty one opens document collection without a second wait.
Plan for three outcomes. A record is found, nothing is found, or what comes back does not describe the customer in front of you. Flows tend to forget the third, and it needs a named owner.
Keep the authorization in the customer file. Who authorized the retrieval, when, and against which record is what evidences that the download was permitted. That is easier to capture in the moment than to reconstruct later.
Authorization and consent for a CKYC download
A stored KYC record is personal data held on behalf of the customer. Retrieving it is an authorized act. Search and download only for a customer your business is onboarding or servicing, and only with the authorization the workflow requires.
Access depends on your organization's eligibility and on the selected service contract. Retention, access control and how you use the record stay your organization's responsibility under applicable data protection and record-keeping rules.