CKYC Registry Integration: Faster Onboarding, Lower Re-KYC
CKYC Registry Integration: Cutting Onboarding Time and Re-KYC Costs for Lenders
Last reviewed: November 2026
CKYC registry integration connects a lender's onboarding systems to the Central KYC Records Registry (CKYCR), so existing customers' KYC records can be retrieved with consent instead of collected again. CERSAI operates the registry, and RBI's KYC directions set how lenders must use it.
This guide is for COOs, CTOs and heads of operations at NBFCs and other lenders. It covers the rules your systems must enforce, how the integration flow works, where the cost savings come from and what to prepare for the revamped registry.
Key Takeaways
- NBFCs must upload KYC records within 10 days of starting a relationship and send updates within seven days.
- If a customer has a CKYC record, the lender must retrieve it online and can ask for documents again only in four situations.
- Since 29 December 2025, the entity that last uploaded or updated a record is responsible for verifying identity and address.
- CERSAI is rolling out CKYCRR 2.0, so integrations built now should be ready for API and process changes.
What Do RBI's Rules Require From Your Systems?
The rules sit in the Reserve Bank of India (Non-Banking Financial Companies – Know Your Customer) Directions, 2025, updated on 29 December 2025. Each rule needs a system control, not just a procedure note.
| Rule | Requirement | System Control |
|---|---|---|
| Retrieve first | Seek the KYC Identifier and retrieve records online | Search CKYCR before asking for documents |
| No repeat documents | Ask again only in four defined cases | Rules engine records which exception applied |
| Upload | Within 10 days of the relationship starting | Upload queue with ageing alerts |
| Updates | Within seven days, unless another period is notified | Change events trigger re-upload |
| Identifier | Share the KYC Identifier with the customer | Automatic message once CKYCR generates it |
| Notifications | Retrieve updated records when CKYCR notifies a change | Inbound update job refreshes your customer file |
| Legacy accounts | Upload at periodic updation or earlier | Backlog tracker by account cohort |
| OTP e-KYC accounts | Flag them when uploading | Account-type field mapped to CERSAI template |
Individual accounts opened on or after 1 April 2017 and legal entity accounts opened on or after 1 April 2021 fall under the upload duty. Older accounts follow the periodic updation cycle.
When Can You Ask for Documents Again?
RBI allows fresh documents only when information in CKYCR has changed, the record is incomplete or not compliant with current norms, downloaded documents have lapsed, or the lender needs to verify identity or address, carry out enhanced due diligence or build a risk profile. Everything else should flow from the downloaded record.
How Does the Integration Flow Work?
A well-built integration runs as a short, automated loop. The steps below describe the logic, whatever vendor or API version you use.
- Search. Look up the customer using the KYC Identifier or other permitted details.
- Consent and download. Download the record with the customer's explicit consent.
- Validate. Check completeness, document validity and match against the applicant.
- Decide. Accept the record, or trigger one of the four exceptions and collect only what is missing.
- Upload or update. Push new or changed records to CKYCR within the deadlines.
- Listen. Process CKYCR update notifications and refresh your records.
Digiqt's KYC document verification AI agent shows how the validation step can be automated when fresh documents are genuinely needed.
What Did the December 2025 Liability Change Mean?
RBI's amendment of 29 December 2025 settled a long-running worry about relying on another entity's record. The entity that last uploaded or updated a record is responsible for verifying identity and address.
A lender that downloads and relies on a current, compliant record need not re-verify those elements. It stays responsible for risk categorisation, ongoing due diligence, enhanced due diligence where needed, transaction monitoring and periodic updation.
The change cuts both ways. Every record your teams upload now carries your liability to the next lender, so upload quality matters as much as download speed.
How Should Upload Quality Be Controlled?
Build quality checks into the upload path rather than relying on later audits. A maker-checker step for manually captured records, image quality checks on document scans and automated matching of name, date of birth and address across documents catch most defects.
Flag accounts opened through OTP-based e-KYC, as RBI requires, and map every field to CERSAI's current template. Rejected uploads should return to a named owner with the reason, not sit in a failed-jobs folder.
Do your teams still collect fresh documents from customers who already have a CKYC record?
Talk to Our Lending Technology Specialists
Visit Digiqt to see how we build digital onboarding journeys with CKYC and KYC checks built in.
How Does CKYC Lower Onboarding Cost?
This is an illustrative scenario with assumed costs and hit rates. An NBFC onboards 20,000 customers a month, and fresh KYC costs ₹150 per customer in verification and staff time.
Assume 55% of applicants have complete, valid CKYC records, and the download route costs ₹40 each including checks. Without CKYC, KYC costs ₹30 lakh a month.
With CKYC, 11,000 downloads cost ₹4.4 lakh, and 9,000 fresh KYCs cost ₹13.5 lakh, a total of ₹17.9 lakh. The monthly saving is ₹12.1 lakh, before counting faster turnaround and fewer drop-offs.
Your real hit rate will depend on your customer mix. New-to-credit and rural borrowers are less likely to have usable records than salaried urban applicants.
Measure the saving on turnaround time too. A downloaded record removes document upload, review and rework steps, which is where many digital applicants abandon the journey.
Where Does Re-KYC Cost Fall?
Periodic updation is the larger, slower cost for established lenders. RBI sets minimum intervals by risk category.
| Risk Category | Updation Frequency | Lower-Cost Route Where Nothing Changed |
|---|---|---|
| High risk | At least every two years | Self-declaration, plus any enhanced checks policy requires |
| Medium risk | At least every eight years | Self-declaration through a registered channel |
| Low risk | At least every 10 years | Self-declaration through a registered channel |
RBI also allows Aadhaar OTP e-KYC in non-face-to-face mode for updation, where the Aadhaar-linked mobile number matches your records. CKYC notifications add a further saving, because updates made at another lender can refresh your file without contacting the customer.
Digiqt's KYC refresh prioritisation AI agent shows how a large re-KYC backlog can be sequenced by risk and due date.
What Should Operations Measure?
A CKYC integration should report its own performance every month. These measures show whether it is saving time and staying compliant.
| Metric | Definition | Why It Matters |
|---|---|---|
| Search hit rate | Applicants found in CKYCR ÷ applicants searched | Sets the ceiling on savings |
| Usable record rate | Records accepted without exceptions ÷ records downloaded | Shows real document savings |
| Exception mix | Fresh-document cases split by the four RBI reasons | Spots over-collection |
| Upload ageing | Records uploaded within 10 days ÷ new relationships | Direct compliance measure |
| Update timeliness | Changes sent within seven days ÷ changes made | Direct compliance measure |
| Notification lag | Time from CKYCR notice to your record update | Keeps customer files current |
Review the exception mix closely. A high share under "lender considers it necessary" often signals habit rather than risk.
Which Integration Mistakes Should Lenders Avoid?
Most problems come from treating CKYC as a back-office upload rather than a live service.
- Uploading late or in batches. The 10-day and seven-day clocks run per customer, not per month.
- Ignoring inbound notifications. Lenders must retrieve updated records when CKYCR signals a change.
- Poor upload quality. Under the December 2025 amendment, your uploads carry your verification responsibility.
- Re-collecting documents by default. Each fresh request should record which of the four exceptions applied.
What Is Changing Next?
The Union Budget of February 2025 announced a revamped Central KYC Registry, and CERSAI has been onboarding and testing regulated entities on CKYCRR 2.0 through 2026. Reported go-live dates have moved, so confirm timelines and technical changes directly with CERSAI.
A downloaded record proves a past verification, not that today's applicant is the same person. Keep fraud screening in the journey, as Digiqt's account opening fraud detection AI agent illustrates, alongside the CKYC lookup.
Build your integration behind an adapter layer so API changes stay contained. Pair it with drop-off tracking, as the onboarding drop-off recovery AI agent shows, to measure whether faster KYC really lifts conversion.
Is your onboarding stack ready to switch to CKYCRR 2.0 without rebuilding every journey?
Talk to Our Lending Technology Specialists
Visit Digiqt to see how we build onboarding, KYC and lending platforms for regulated lenders.
