On this page
Central KYC Registry Basics
The Central KYC Registry (CKYCR) is the shared system a bank, NBFC, insurer, or mutual fund distributor checks before asking a customer to submit KYC documents again.
What is CKYC?
CKYC refers to the Central KYC Records Registry (CKYCR), a central repository of KYC records for customers of the Indian financial sector, operated by CERSAI. When a reporting entity completes KYC for a new customer, it uploads the record to the registry; the customer is then assigned a 14-digit CKYC Identifier, often called a KIN.
The point of the registry is to stop the same customer being put through full document collection by every institution they deal with. Another regulated entity can retrieve the existing record with the customer’s consent instead of starting from scratch.
How the flow works
- The entity completes due diligence and files the KYC record, with images of the supporting documents, to the registry.
- The registry de-duplicates against existing records and issues or matches a CKYC identifier.
- A different entity later searches the registry using the identifier or permitted search parameters, and downloads the record with the customer’s authorisation.
- When any detail changes, the entity that holds the relationship is expected to update the central record so downstream users are not working from stale data.
What CKYC does not do
A downloaded CKYC record is identity evidence, not a substitute for the rest of a compliance programme. It does not perform risk categorisation, sanctions or PEP screening, or ongoing monitoring for you. It also says nothing about product-specific facts — whether the bank account being credited actually belongs to the customer, whether the employment claim is real, or whether the address is current. Those remain separate checks.
Where it helps most
CKYC is at its most valuable for institutions onboarding customers who already hold financial products elsewhere: mutual fund distributors, insurers, NBFCs and banks acquiring existing bank customers. For first-time customers with no registry record, the entity still has to run full verification — and then contribute the record back.
Working with the Central KYC Registry day to day
The Central KYC Registry is meant to make KYC simpler for customers and institutions alike, but getting that benefit takes some care. This section covers how regulated entities use the Central KYC Registry in practice: searching for existing records, downloading them, uploading new ones and keeping them current.
Searching for an existing record
When a new customer arrives, check whether they already have a record in the Central KYC Registry. Customers may know their KYC identifier from a previous institution; if not, a search using their details can find it, subject to the applicable rules and consent. An existing record can shorten onboarding significantly.
Downloading and using a record
A downloaded record shows the KYC information held at the time it was last updated. Check whether key details, such as address and contact information, are still current, and collect updates where they are not. Remember that your own obligations to identify the customer remain: the Central KYC Registry is a starting point, not a replacement for your judgement.
Uploading new records
For customers without a record, complete KYC and upload the record within the timelines set by the rules. Accuracy matters because other institutions will rely on it. Verify identity and address against source records first, use consistent name formats, and attach clear document images.
Updating records
When customers change their details, update their record in the Central KYC Registry so the next institution sees current information. Build updates into your normal change-of-details process rather than treating them as a separate task.
Handling rejections
Uploads can be rejected for missing fields, format problems or poor images. Track rejections by reason, fix their causes in your capture flow and resubmit promptly. A rising rejection rate usually points to a specific step that needs attention.
Data quality checklist
- Verify PAN and identity against source records before creating the record.
- Capture names exactly as they appear on official documents.
- Use clear, complete document images.
- Map your fields carefully to the registry format.
- Reconcile your records with the registry periodically.
Benefits for customers
For customers, the Central KYC Registry means fewer repeated forms when they open accounts with banks, insurers, brokers and funds. That benefit only materialises if records are accurate and current, which is why every institution’s care at upload matters to everyone else.
Benefits for institutions
For institutions, the Central KYC Registry can reduce onboarding time and cost for customers who already have a record, and it provides a consistent format for KYC information. Institutions that invest in good source verification upstream see fewer rejections and more reliable downloads.
Governance
Assign clear ownership for Central KYC Registry processes: who uploads, who handles rejections, who manages updates and who reviews reconciliation reports. Clear ownership keeps the process running smoothly as volumes grow.
Keeping up with the rules
The rules governing the Central KYC Registry, including timelines and data requirements, are set by regulators and can change. Review your processes whenever they are updated, using the official sources. More information is available from the Central KYC Registry and in the RBI’s Master Direction on KYC.
Related terms
Verify it with Veriqos Technologies
Pair a registry record with live checks on the details that change:
- Bank Account Verification API — Instantly confirm the authenticity of any bank account with Veriqos Technologies’ Bank Account Verification API — account number, holder name, and status in real time.
- UAN Verification API — Veriqos Technologies’ UAN Verification API lets you confirm employee details in real time using trusted EPFO records — for onboarding, banking, or employment verification.
- Electricity Bill Verification API — Validate electricity bill details quickly and accurately with Veriqos Technologies’ Electricity Bill Verification API — for loan processing, account opening, or utility registrations.
See how these checks are applied in Banks & NBFCs, Insurance Providers.
← Back to the verification glossary
This entry explains how the check works in practice. It is general information, not legal or compliance advice — confirm current requirements against the applicable regulation.
Who Has to Upload to the Central KYC Registry
Any reporting entity that completes KYC for a customer, banks, NBFCs, insurers, and mutual fund distributors among them, is expected to file that record with the registry, not just query it. That two-way obligation is what keeps the Central KYC Registry useful: it only stays current if every entity that updates a customer’s details also pushes that update back, not only the entity that first onboarded them.
KIN Number vs Aadhaar or PAN
A KIN identifies a KYC record inside the Central KYC Registry specifically, it is not a replacement for Aadhaar or PAN, and does not carry the same regulatory weight as either. It is best thought of as a pointer: given a KIN, an authorised entity can retrieve the underlying KYC record, but the KIN itself proves nothing about identity on its own.
Further reading: CKYC Explained: What CERSAI Upload Actually Requires.
Automating the CKYC upload for NBFCs
NBFCs handling the 3-working-day CKYC upload requirement manually often struggle with the deadline when KYC data is scattered across forms and scans. A CKYC upload API that structures PAN, Aadhaar, and address verification data at the point of onboarding removes that reconciliation step, so the record is already CERSAI-ready the moment onboarding finishes — see CKYC Explained for the full requirement.
