In brief: CKYC is India’s central KYC records registry, operated by CERSAI. Regulated entities upload customers’ KYC records to CKYC, and other institutions can retrieve them with the customer’s KYC identifier instead of repeating the whole process.
CKYC (Central KYC) is one of those compliance requirements that gets mentioned constantly and explained rarely. Here’s what it actually requires, in plain terms.
What CKYC/CERSAI is
CKYC is a centralized repository of KYC records for the financial sector, maintained by CERSAI (Central Registry of Securitisation Asset Reconstruction and Security Interest of India) on behalf of financial sector regulators. The idea: once a customer’s KYC is done and uploaded to CKYC by any one regulated entity, other regulated entities can pull that record via a CKYC number instead of re-collecting the same documents from the customer again.
The upload requirement
Under RBI’s KYC Master Direction, regulated entities — banks, NBFCs, and other financial institutions covered by the Direction — are required to upload the KYC records of new individual customers to CKYC within 3 working days of account opening. This isn’t a “when convenient” guideline; it’s a compliance deadline tied directly to account opening, and it applies to every new individual customer relationship, not a sample.
Who must comply
Any RBI-regulated entity conducting customer due diligence under the KYC Master Direction — this covers banks and most NBFCs carrying out KYC on individual customers. The upload obligation sits with the entity that onboarded the customer, not with the customer.
How API-based KYC simplifies CERSAI-ready records
The 3-day window is tight if KYC data is scattered across manual forms, scanned documents, and separate verification steps that all need to be reconciled before upload. When PAN, Aadhaar, and address verification all run through structured, real-time APIs from the start, the resulting KYC record is already in a clean, complete, CERSAI-ready format the moment onboarding finishes — there’s no separate data-assembly step standing between “customer onboarded” and “record uploaded.”
This article references the 3-working-day CERSAI upload window under RBI’s KYC Master Direction. Regulatory windows like this are periodically amended — verify the current requirement against the latest RBI circular before relying on this figure for compliance purposes.
How CKYC works in day-to-day onboarding
CKYC was designed to stop customers repeating the same KYC for every bank, insurer, broker and fund they deal with. When a regulated entity completes KYC, it uploads the customer’s record to the CKYC registry and the customer receives a KYC identifier. Another regulated entity can then use that identifier to download the record, subject to the applicable rules, and onboard the customer with less effort.
The two sides of CKYC
Uploading. Regulated entities must upload KYC records for new customers within the timelines set by the rules, and update them when customer details change. Downloading. When a customer already has a KYC identifier, an institution can retrieve their record from CKYC, typically with the customer’s consent, and use it as part of its own KYC process.
Why record quality matters
Because CKYC records are reused, mistakes travel. A misspelt name, an outdated address or a poor-quality document image uploaded by one institution becomes a problem for every institution that downloads the record later. The best protection is strong verification before upload: confirm identity and address against source records, use consistent name formats, and attach clear document images.
How API-based verification helps
- PAN verification confirms the tax identity and the name on record.
- Aadhaar-based routes, such as DigiLocker or offline verification, confirm identity and address from issuer data.
- Face match and liveness confirm the person matches their documents.
Using these checks before creating a CKYC record means the record starts accurate, which makes the later upload smoother and reduces rejections.
Handling CKYC rejections
Uploads can be rejected for missing fields, format problems or image quality. Track rejections by reason, fix the root cause in your capture flow, and resubmit promptly. A rising rejection rate is usually a sign that a capture step or a field mapping needs attention.
Using downloaded records responsibly
A downloaded CKYC record is a strong starting point, but it reflects the information at the time it was last updated. Check whether key details, such as address and contact information, are still current, and update the record if they have changed. Your own obligations to know your customer remain, even when you start from a CKYC record.
Operational checklist
- Verify identity and address against source records before creating the record.
- Map your data fields carefully to the CKYC format.
- Upload within the required timelines and track status.
- Handle rejections quickly and fix their causes.
- Update records when customers change their details.
- Keep evidence of every upload, download and update.
The benefit for customers
For customers, CKYC means fewer repeated forms and document uploads across financial products. For institutions, it means faster onboarding of customers who already have a KYC identifier. Both depend on the quality of the records in the registry, which is why careful verification before upload matters. More information is available from the Central KYC Registry.
