Why RBI Is Pushing Digital KYC for Cooperative and Small Finance Banks
The Reserve Bank of India has made digital transformation of the cooperative banking sector a strategic priority. India has over 1,500 urban cooperative banks (UCBs) and 96,000 rural cooperative credit institutions serving millions of customers in tier-2, tier-3, and rural areas. Additionally, 12 small finance banks (SFBs) licensed since 2015 were specifically created to serve the underbanked population with technology-driven banking services. The RBI's vision, articulated through multiple circulars and the Report of the Expert Committee on Urban Co-operative Banks (Malegam Committee), is clear: these institutions must modernize their operations, including customer onboarding, to remain viable and compliant.
The regulatory pressure has intensified significantly since 2020. The RBI's Master Direction on KYC, updated in January 2023 via circular RBI/2023-24/03, explicitly extends V-CIP provisions to all regulated entities including cooperative banks. The Banking Regulation (Amendment) Act, 2020, brought cooperative banks under stricter RBI supervision, aligning their compliance obligations more closely with commercial banks. The RBI's supervisory action framework now treats KYC deficiencies in cooperative banks with the same seriousness as in commercial banks, and several UCBs have faced penalties and business restrictions for inadequate KYC processes.
Beyond compliance pressure, there is a competitive imperative. Small finance banks and cooperative banks compete for the same customer segments as digital-first neobanks, large commercial banks with mobile apps, and fintech lending platforms -- all of which offer instant or same-day account opening through digital KYC. A cooperative bank that still requires a branch visit for account opening is at a severe competitive disadvantage when a fintech competitor can onboard the same customer in 10 minutes via Video KYC on their smartphone. The RBI's push for digital KYC is not merely regulatory -- it is designed to ensure the long-term competitiveness and relevance of smaller banking institutions.
Regulatory Framework: V-CIP Applicability for Scheduled vs Non-Scheduled Banks
Understanding the regulatory framework is essential because the V-CIP requirements differ slightly between scheduled and non-scheduled cooperative banks. Scheduled cooperative banks (those included in the Second Schedule of the RBI Act) are subject to the full Master Direction on KYC and can implement V-CIP following the same guidelines as scheduled commercial banks. This includes the requirement for end-to-end encryption, live video with simultaneous audio, real-time face matching against OVDs, geo-tagging, and tamper-proof recording storage. As of 2026, approximately 54 scheduled UCBs fall into this category.
Non-scheduled cooperative banks, which form the vast majority (over 1,400 UCBs), are regulated under the same KYC Master Direction but have historically had more flexibility in implementation timelines. However, the RBI's circular dated April 2024 (RBI/2024-25/18) explicitly clarified that all UCBs, regardless of scheduled status, must be capable of conducting V-CIP by March 2026 if they wish to onboard customers remotely. Non-scheduled UCBs that do not implement V-CIP capability are restricted to in-branch KYC only, limiting their growth potential in an increasingly digital market.
Small finance banks have no ambiguity in their V-CIP obligations. As scheduled commercial banks with a specific mandate for financial inclusion, SFBs are expected to offer V-CIP as a standard onboarding channel. The RBI's licensing conditions for SFBs emphasize technology-led operations, and all 12 SFBs have implemented or are implementing Video KYC. The key regulatory consideration for SFBs is that their V-CIP implementation must be robust enough to serve their target demographic -- unbanked and underbanked customers who may have limited digital literacy and unreliable internet connectivity. The RBI evaluates SFB compliance not just on technical implementation but on actual accessibility and adoption metrics.
Challenges Unique to Smaller Banks (Budget, IT Infrastructure, Rural Reach)
Cooperative banks and small finance banks face a distinct set of challenges when implementing Video KYC that larger commercial banks do not encounter. The most immediate challenge is budget. The average urban cooperative bank has a net worth of INR 50 to 200 crore, with annual IT budgets ranging from INR 50 lakh to INR 3 crore. Compare this to a large private bank spending INR 500 to 2,000 crore annually on technology. For a UCB, a Video KYC platform implementation that costs INR 15 to 30 lakh (including integration, training, and first-year licensing) represents a significant portion of the annual IT budget and requires board-level approval and careful cost justification.
IT infrastructure is the second major challenge. Many cooperative banks operate on legacy core banking systems (CBS) that were implemented 10 to 15 years ago with limited API capabilities. Integrating a modern Video KYC platform with these legacy systems requires middleware development, custom API bridges, and extensive testing. Some cooperative banks still use manual or semi-automated account opening processes where customer data is entered into the CBS through desktop applications rather than APIs. The Video KYC platform must either integrate with these legacy workflows or the bank must simultaneously upgrade its CBS -- adding cost and complexity.
Staffing is a third challenge that is often underestimated. Cooperative banks typically have smaller, less specialized teams than commercial banks. The same employee who handles customer service at the branch may also need to serve as a Video KYC agent. There is rarely a dedicated compliance team to oversee V-CIP implementation, and IT departments (often 2 to 5 people) must manage the Video KYC platform alongside all other technology systems. Training these multi-role staff members to conduct compliant, efficient Video KYC sessions requires a platform that is intuitive enough to use without extensive technical training.
Rural reach is the fourth and perhaps most distinctive challenge. Cooperative banks and SFBs serve many customers in areas where internet connectivity is unreliable, smartphones are basic, and digital literacy is low. A Video KYC implementation that works perfectly in urban Pune or Ahmedabad may fail entirely in a taluka-level town where 4G speeds average 2 to 3 Mbps and customers use entry-level smartphones with 2 GB RAM. The platform must be optimized for low-bandwidth environments and designed for users who may be conducting their first-ever video call.
On-Premise vs Cloud Deployment: What Makes Sense for Small Banks
The deployment model decision is critical for smaller banks and involves balancing cost, compliance, and operational capability. Cloud deployment (SaaS) is the most cost-effective option for the majority of cooperative banks and SFBs. With cloud deployment, the Video KYC provider hosts the platform on secure cloud infrastructure (typically AWS Mumbai or Azure Central India regions), manages server scaling, security patches, and uptime, and the bank accesses the platform through a web browser. The bank pays a per-session fee with no upfront infrastructure investment, making the financial model predictable and aligned with actual usage.
However, some cooperative banks face regulatory or governance constraints that make cloud deployment problematic. Certain state cooperative bank registrars and apex bodies have issued guidelines requiring member banks to store customer data on infrastructure within their direct control. The RBI's outsourcing guidelines (circular DBOD.No.BP.40/21.04.158/2006-07 and subsequent updates) require that regulated entities maintain oversight of outsourced technology services, including the ability to audit the service provider's infrastructure. For cooperative banks without the expertise to conduct cloud infrastructure audits, the compliance documentation burden of cloud deployment can be significant.
On-premise deployment gives the bank complete control over data storage and processing but requires substantial infrastructure investment: dedicated servers (minimum two for redundancy), SSL certificates, a static IP address with adequate bandwidth, and IT staff capable of maintaining the platform. For a cooperative bank, the on-premise setup cost ranges from INR 8 to 20 lakh for hardware plus annual maintenance and licensing fees. This model makes financial sense only for banks processing more than 3,000 to 5,000 Video KYC sessions per year, where the amortized per-session cost of the infrastructure falls below the cloud per-session fee.
A hybrid model offers an increasingly popular middle ground. In this approach, the video calling and real-time processing happen on the provider's cloud infrastructure (leveraging their CDN, media servers, and AI processing), but all customer data, recordings, and audit logs are automatically transferred to the bank's on-premise storage at the end of each session. The cloud components handle the technically demanding real-time functions that would be difficult for a small bank to manage on-premise, while the bank retains physical custody of all customer data. This hybrid approach typically costs 15 to 25 percent more than pure cloud but 40 to 60 percent less than full on-premise deployment.
Minimum Infrastructure and Staffing Requirements
For cooperative banks and SFBs planning a Video KYC implementation, the minimum infrastructure requirements are more modest than many assume. On the agent side, each Video KYC workstation requires a desktop or laptop computer with a modern browser (Chrome 90+, Firefox 88+, or Edge 90+), a webcam with at least 720p resolution (built-in laptop cameras are usually sufficient), a headset with noise-cancelling microphone, and a broadband internet connection with at least 5 Mbps upload speed per concurrent agent. For a bank planning to run two to three concurrent Video KYC sessions, the total agent-side infrastructure investment is typically INR 1 to 2 lakh for equipment and INR 5,000 to 10,000 per month for dedicated internet bandwidth.
Customer-side requirements are set by the platform and must be communicated clearly. The minimum customer device should be a smartphone with Android 8+ or iOS 13+, a front-facing camera with at least 5 MP resolution, and a mobile data connection of 1 Mbps or faster. These requirements are met by virtually all smartphones sold in India since 2018, covering the vast majority of the banking customer base. However, it is important to note that customers in rural areas may use shared devices or older handsets that do not meet these minimums -- the bank should maintain a branch-assisted Video KYC option where staff can conduct the V-CIP session using the bank's equipment with the customer physically present.
Staffing requirements depend on expected volume. As a general guideline, one full-time Video KYC agent can handle 40 to 60 sessions per day (assuming 6 to 8 minutes per session including documentation). A cooperative bank onboarding 200 to 500 customers per month through Video KYC needs one dedicated agent during business hours, with a backup agent trained to cover leave and peak periods. The RBI requires that V-CIP agents be "officials of the Regulated Entity" -- meaning the bank cannot outsource the agent role to a third-party BPO. However, the agent does not need to be a senior officer; any trained employee of the bank can serve as a V-CIP agent after completing the required training and certification. A compliance officer (who can be an existing compliance team member) should oversee the V-CIP process, conduct periodic quality reviews, and serve as the escalation point for flagged sessions.
Step-by-Step Implementation Roadmap
A realistic implementation timeline for a cooperative bank or small finance bank spans 8 to 14 weeks from vendor selection to go-live. Week 1-2: Vendor evaluation and selection. Prepare a Request for Proposal covering platform features, deployment options, pricing, compliance certifications, and references from similar-sized institutions. Evaluate at least three Video KYC providers on technical capability, regulatory compliance, ease of integration, and total cost of ownership. Obtain board approval for the selected vendor and budget allocation.
Week 3-5: Technical integration and setup. The vendor configures the platform according to the bank's branding and workflow requirements. API integration with the core banking system begins -- for banks with modern CBS platforms (Finacle, FIS, Oracle FLEXCUBE), standard REST APIs typically require 5 to 10 days of development and testing. For legacy CBS platforms, the vendor may need to develop custom middleware, extending this phase by 1 to 2 weeks. Agent workstations are set up and tested for video and audio quality. SSL certificates, domain configuration, and security testing are completed.
Week 6-8: Agent training and compliance documentation. Conduct a minimum 5-day training program covering V-CIP regulatory requirements (RBI Master Direction on KYC, PMLA Rules 2005 as amended), platform operation (session management, document verification, liveness checks), fraud detection indicators (document tampering, impersonation attempts, deepfake red flags), and customer communication skills. Prepare and submit the V-CIP policy document to the bank's board, including the process flow, escalation matrix, audit trail management, and data retention policy. Update the bank's KYC policy to include V-CIP as an approved CDD method.
Week 9-12: Pilot testing and go-live. Run a controlled pilot with 50 to 100 sessions using internal staff or friendly customers to identify issues with the workflow, network performance, and agent readiness. Address any compliance gaps identified during the pilot. Obtain sign-off from the compliance officer and, if required, external auditors. Launch Video KYC for a limited customer segment (for example, existing customers requesting additional products) before expanding to new account openings. Establish a weekly review cadence for the first three months to monitor completion rates, failure reasons, customer feedback, and compliance metrics. Gradually scale volume based on agent capacity and operational stability.
How BaseKYC Serves Smaller Banking Institutions
BaseKYC was designed with the understanding that not every financial institution has the IT budget and infrastructure of a large private bank. For cooperative banks and small finance banks, BaseKYC offers several features specifically tailored to their needs. The platform's flexible deployment options -- cloud, on-premise, and hybrid -- allow each institution to choose the model that best fits their regulatory constraints and technical capabilities. The on-premise deployment option includes a lightweight server package that runs on standard hardware without requiring specialized IT expertise to maintain.
Pricing is structured to be accessible for lower-volume institutions. Unlike providers that require minimum monthly commitments of 5,000 or 10,000 sessions, BaseKYC offers plans starting from as few as 200 sessions per month with no long-term contract lock-in. This pay-as-you-grow model allows a cooperative bank to start with a modest Video KYC pilot and scale up based on actual demand without overpaying for unused capacity. The platform includes all features -- OCR, liveness detection, face matching, co-browsing, and reporting -- in the base price, with no hidden per-feature charges that could make the total cost unpredictable.
Integration with legacy CBS platforms is a particular strength. BaseKYC's integration team has experience connecting with older versions of Finacle, BaNCS, Oracle FLEXCUBE, and several cooperative-bank-specific CBS platforms. For banks that cannot support API integration, BaseKYC offers a standalone mode where the Video KYC platform operates independently and exports completed verification records in standard formats (CSV, XML) that can be manually imported into the CBS. While not as seamless as API integration, this standalone mode allows banks to begin Video KYC operations immediately while planning a future API integration.
The platform's low-bandwidth optimization is critical for banks serving rural customers. BaseKYC's adaptive video engine maintains session stability on connections as slow as 500 Kbps by automatically adjusting video resolution, frame rate, and compression. The customer-facing interface is designed for simplicity, with large buttons, clear visual instructions in multiple Indian languages, and a step-by-step guided flow that requires minimal digital literacy. For banks that want to offer assisted Video KYC from branch premises, BaseKYC supports a branch-assisted mode where the bank's device serves as the customer-side endpoint while the agent connects from a central location -- enabling banks with dozens of small branches to centralize their V-CIP operations with just one or two dedicated agents.