Most CKYC guidance is written for large banks with centralised technology teams. Housing Finance Companies, gold loan NBFCs, MFIs, and Tier-2 lenders operate in a fundamentally different environment - high branch counts, rural customer bases, Form 60 dependency, and limited IT infrastructure. This guide addresses their specific CKYCRR 2.0 challenges directly.

Why Tier-2 CKYC Is a Different Problem

The standard CKYC compliance framework is written with a large scheduled bank in mind - centralised operations, urban customer base, high PAN penetration, stable mobile numbers on record, and a technology team that can build and maintain API integrations. For Housing Finance Companies, gold loan NBFCs, microfinance institutions, and Tier-2 lenders, almost none of these assumptions hold.

These institutions serve India's priority lending segments: affordable housing borrowers in peri-urban areas, rural gold pledgers, self-help group members, and first-time formal credit customers. Their CKYC challenges are structural, not merely operational. No amount of staff training solves the problem of a customer whose Aadhaar is not linked to a mobile number. No API integration resolves a Form 60 customer who obtains a PAN three months after disbursal. These require documented workflows, not just technology.

Housing Finance Companies: Property Docs, Co-Lending and VCIP

Challenge 1: Dual Documentation Workflow

HFC KYC includes the standard NBFC identity verification procedure plus property-linked documentation - title deeds, encumbrance certificates, and property valuation reports. None of the property documents go into the CKYC submission. But branch staff are trained to collect all documents together, and separating the CKYC documents from the property documents into two distinct submission workflows requires specific process design and training.

Under CKYCRR 2.0, the CKYC submission must happen within 10 working days of completing KYC - regardless of where the property documentation process stands. An HFC that waits for property verification to complete before submitting CKYC will routinely breach this deadline.

Challenge 2: Co-Lending CKYC Requirements

Co-lending partnerships between HFCs and banks are now widespread in the affordable housing segment. The bank co-lender cannot access the customer's CKYC record from CERSAI without the OTP consent flow - and if the customer's mobile number on CERSAI is outdated, this blocks co-lending onboarding entirely. Any delay or rejection in the HFC's CKYC submission cascades directly into a delay in co-lending disbursement.

Challenge 3: VCIP and Digital Onboarding

Video Customer Identification Process (VCIP) is an RBI-approved method for remote onboarding that HFCs increasingly use for urban and semi-urban customers who cannot visit a branch. VCIP-completed KYC is valid for CKYC upload to CERSAI - the record created through VCIP can be submitted via the CKYC Create API with verification method noted in the verifier detail fields. VCIP session recordings must be retained separately from the CKYC record for audit purposes.

Gold Loan NBFCs: Speed, Rural OTP and RBI Compliance Overhaul

Challenge 1: OTP Consent for Rural Customers

The CKYCRR 2.0 Download API requires OTP consent from the customer's registered mobile before the full CKYC record can be retrieved. For gold loan customers in rural and semi-urban markets, the mobile number registered on CERSAI from a previous KYC submission may be outdated or no longer in use. Gold loan NBFCs need a documented decision workflow for OTP delivery failures - one that does not leave branch staff deciding on the spot what to do while the customer's gold sits on the counter.

Challenge 2: RBI Gold Loan Compliance Overhaul (April 2026)

RBI's April 2026 gold loan compliance overhaul adds KYC verification requirements on top of CKYCRR 2.0 obligations. All NBFCs offering loans against gold or silver must comply regardless of portfolio size - with no exceptions based on ticket size or business model. Operations teams must manage both regulatory frameworks simultaneously without creating a bottleneck at the disbursement stage.

Challenge 3: High Volume, Short Tenure, API Rate Limits

A large gold loan NBFC may process thousands of new pledges daily across hundreds of branches. Under CKYCRR 2.0 real-time API submissions, each onboarding event triggers a Search, then a Download or Create. At scale, this is an engineering problem as much as a compliance problem - the API integration must handle concurrent submissions and manage rate limits. CERSAI's API supports up to 20 requests per second per IP, requiring queue management at high-volume branches.

MFIs and JLG KYC: Individual Records in Group Lending

JLG KYC: The Individual Obligation in a Group Context

A Joint Liability Group typically consists of 5 to 10 members who mutually guarantee each other's loans. Under CKYC requirements, every individual member requires a separate CKYC record - there is no group-level submission. Each member's KYC must be verified, uploaded to CERSAI, and a KIN obtained individually before the group loan can be disbursed. For a group of 8 members, this means 8 Search API calls, up to 8 Create submissions, and 8 status polls to confirm KIN assignment.

Field officers managing group meetings cannot wait for asynchronous CKYC processing to complete on-site. The group onboarding workflow must be designed to batch the CKYC submissions centrally after the field visit and hold disbursement until all KINs are confirmed.

SHG Members and Aadhaar Without Mobile Linkage

Self-Help Group members in rural areas often have Aadhaar cards but no Aadhaar-linked mobile number. Under CKYCRR 2.0, downloading an existing CKYC record requires an OTP to the customer's registered mobile. For SHG members without a linked mobile, the Download path is blocked. The Create path is the only option - and for members who already have a CKYC record under a different phone number, this creates a probable-match scenario requiring resolution before a new KIN is assigned.

The Form 60 Challenge Across All Tier-2 Segments

PAN penetration in rural India remains significantly lower than in urban markets. Across all Tier-2 segments, a substantial proportion of customers will not have a PAN at onboarding. The CKYC framework accommodates this through Form 60, but the operational handling creates three specific challenges.

Challenge 1: The Exact String Requirement

In the CKYC API, the PAN_Card field must contain the exact string Form60 when a customer has no PAN - not "NA", not blank, not "Form 60" with a space, not lowercase "form60". Any variation causes a data validation rejection. This is a training and data entry standardisation problem affecting every branch that handles Form 60 customers. See our full rejection guide for the complete list of data validation failure causes.

Challenge 2: The PAN Obtained After Disbursal Scenario

A customer who submits Form 60 at onboarding and subsequently obtains a PAN creates a partial match scenario at their next interaction. Their CKYC record on CERSAI was created without a PAN. Their current data now includes one. The Search API returns the old record, the Download produces a partial match on the PAN field, and the CKYC Update API must be triggered. Under the November 2024 RBI amendment, institutions must submit customer data changes to CERSAI within 7 days - making proactive PAN tracking a compliance requirement, not just a data quality initiative.

Challenge 3: Form 60 and Periodic Re-KYC

When a Form 60 customer comes up for periodic re-KYC, the institution must verify whether the customer has since obtained a PAN. If they have, the re-KYC submission must include the PAN and trigger an Update to CERSAI. This adds a PAN verification step to the re-KYC workflow for every Form 60 customer - a step most institutions have not built into their re-KYC processes.

Document Quality in Rural Onboarding

Document quality rejections are the most common CKYC rejection category across all institution types - but the causes and fixes are structurally different in rural versus urban onboarding.

Branch-Level Readiness for CKYCRR 2.0

The most underestimated CKYCRR 2.0 readiness requirement for Tier-2 lenders is branch staff readiness. The shift from batch uploads to real-time API submissions changes what branch staff must do and when - and for most Tier-2 lenders, branch staff are the primary interface with the CKYC process.

For a lender with 200 branches and 5 staff per branch, this is a training programme for 1,000 people - not a central operations team update. It requires simplified interfaces, job aids in regional languages, and a helpdesk for branch escalations. Most Tier-2 lenders have not yet begun this readiness work.

Sector Comparison: CKYC Complexity by Lender Type

Frequently Asked Questions