Adviser Hub CloudEnterprise Wealth Tech
Compliance

KYC Software in India: Video KYC, CKYC and Aadhaar Rules for Regulated Entities

Video KYC, CKYCR uploads, Aadhaar access, DPDP and data-localization rules decide which vendors an Indian bank, NBFC, broker or insurer can use. This guide shows how to scope a compliant stack and gives indicative cost and timeline ranges.

By the Adviser Hub Cloud editorial team · November 2026 · 12 min read

Match Each Product Line to Its Regulator: RBI, SEBI or IRDAI

When you scope KYC software, India gives you a question to answer before you look at vendors. Which regulator's KYC rules govern each product line you onboard customers for? A bank with an insurance distribution arm and a broking subsidiary can answer to three rulebooks at once. They overlap heavily, but they differ in exactly the details that decide what the software must do.

All three rest on the same legal base: the Prevention of Money Laundering Act, 2002 and the PML (Maintenance of Records) Rules, 2005. Together they require customer due diligence, beneficial ownership checks, record retention (generally five years after the relationship ends) and reporting to FIU-IND. Each regulator then adds its own layer:

  • RBI-regulated entities (banks, NBFCs, payment aggregators, prepaid instrument issuers, housing finance companies) follow the Master Direction on KYC. It's the most prescriptive of the three on video-based onboarding (V-CIP), periodic updation and CKYCR uploads.
  • SEBI intermediaries (stockbrokers, depository participants, mutual fund distributors, portfolio managers) follow SEBI's KYC and AML circulars, plus the KYC Registration Agency (KRA) system.
  • IRDAI-regulated insurers and intermediaries follow IRDAI's AML/CFT master guidelines. KYC is now mandatory for new life and general insurance policies, and video-based KYC is permitted.

If you hold an RBI license, scope to the RBI Master Direction first. It's usually the strictest, and a platform that survives an RBI inspection typically handles SEBI and IRDAI flows with configuration changes rather than a rebuild. It doesn't work the other way round. A broker-grade video tool built for in-person verification (IPV) may not meet V-CIP's infrastructure and audit requirements.

Advertisement

What RBI V-CIP Requirements Mean for a Video KYC Platform

V-CIP (Video-based Customer Identification Process) is where most bank onboarding stacks pass or fail inspection. The RBI Master Direction treats V-CIP as equivalent to face-to-face onboarding, but only when specific conditions are met. Check every vendor claim against them:

  • A live official, not a bot. A trained official of the regulated entity must run the interaction in real time. Fully automated "video KYC" isn't V-CIP. Automation can still help the official with face match, OCR and liveness scores.
  • Customer location. The customer must be physically in India, and the session must be geo-tagged. The platform should block or flag sessions where IP and device location disagree.
  • Identity evidence. Aadhaar authentication or offline verification, or officially valid documents (OVDs) fetched through DigiLocker, plus PAN verified against the issuing authority's database. A physical card held up to the camera isn't enough on its own.
  • Liveness and face match. The official confirms the live customer matches the verified document photo, and the platform should run liveness checks that catch deepfakes and replayed video.
  • Infrastructure ownership. V-CIP infrastructure must be housed in the regulated entity's own premises, with connections originating from its own secured network domain. Any technology outsourcing must follow RBI's IT outsourcing rules. This clause alone rules out many pure-SaaS setups.
  • Recordings and audit trail. Sessions must be recorded with date and time stamps and stored securely. Accounts opened through V-CIP can be made operational only after a concurrent audit.
  • Security testing. Vulnerability assessment, penetration testing and a security audit are required before go-live, with periodic retesting after.

Operations teams most often underestimate the concurrent audit. You need a separate auditor queue, maker-checker controls and the ability to reject and reinitiate a session inside the platform. Without them, audits end up in spreadsheets within weeks.

Aadhaar Access: e-KYC, Offline Verification and the Licensing Gate

Aadhaar is India's fastest identity rail and its most legally restricted one. Which software options you have depends on the access your entity holds.

OTP, biometric and face e-KYC

Full Aadhaar e-KYC, where UIDAI returns demographic data and a photo after authentication, is open only to entities permitted under the Aadhaar Act and PMLA. Banking companies are covered directly. Most other entities, including many NBFCs, need specific notification or approval, and they usually connect as a sub-AUA or sub-KUA through a licensed KUA rather than holding a UIDAI license. Approval can take many months, so don't set a launch date that depends on it until you have it in writing.

Offline verification

Aadhaar paperless offline e-KYC (the digitally signed XML), secure QR code verification and DigiLocker documents are more widely available, with customer consent. Most NBFCs, fintech lenders and brokers rely on them. They're cheaper and need no UIDAI license. The trade-off is completion rate: customers have to download files or remember share codes, and some drop off.

Storage rules your vendor must enforce

  • Full Aadhaar numbers, where stored at all, go in an Aadhaar Data Vault with encryption and tightly controlled access.
  • Screens, logs and downstream systems show masked numbers (last four digits only).
  • Biometric data is never stored.
  • Consent is captured explicitly, in a language the customer understands, and logged.

Ask vendors to show where the Aadhaar number appears in logs, analytics pipelines and support tools, not just the main database. Those secondary systems are where exposure usually happens.

CKYCR Integration and the KRA Layer for Brokers

The Central KYC Records Registry, run by CERSAI, is a shared KYC repository for RBI, SEBI, IRDAI and PFRDA entities. Each customer gets a 14-digit KYC identifier. With the customer's consent, you can download their verified record instead of collecting documents again. Your own due diligence and risk categorization obligations don't go away.

A competent CKYCR integration handles four jobs:

  1. Search and download at onboarding, with consent capture and a fallback to fresh KYC when the record is missing, outdated or inconsistent.
  2. Upload of new customer records within the regulatory window (ten days from the start of the relationship under the current RBI direction; confirm the deadline for your regulator), in CERSAI's file and image formats.
  3. Updates when customers change address or other details.
  4. Legal entity records. Many vendors handle these poorly, so test them specifically if you onboard companies, trusts or partnerships.

Upload rejections are the hidden cost. Image resolution, file size and field-format errors can bounce a meaningful share of records, and someone has to fix and resubmit each one. Ask every vendor for its rejection-handling workflow and a sample error report.

SEBI intermediaries also work with SEBI-registered KRAs such as CVL, NDML, CAMS, KFintech and NSE's DotEx. KRAs validate key attributes like PAN, name, address, mobile and email against official sources, and records that fail validation limit which intermediaries can rely on them. A broker's stack needs fetch, upload and status-tracking integrations with the KRAs, and ideally CKYCR too.

Data Protection, Localization and Outsourcing Rules That Narrow Your Vendor List

Many capable global identity vendors drop off Indian shortlists over regulation, not features. Check four sets of rules before you book demos.

  • Digital Personal Data Protection Act, 2023 and the DPDP Rules. The Rules were notified in late 2025, and most obligations phase in over roughly 18 months. Expect plain-language consent notices, purpose limitation, retention and erasure schedules (reconciled with PMLA retention duties), breach notification to the Data Protection Board and affected individuals, and processor contracts that bind your vendor. Your institution is the data fiduciary and stays accountable; the KYC vendor is usually a processor.
  • Localization. RBI's 2018 directive requires payment system data to be stored only in India, and RBI's digital lending rules expect borrower data on servers in India. Many banks apply an India-only rule to all KYC data as internal policy. Get written answers on where primary storage, backups, disaster recovery, logs and any model-training data physically sit.
  • RBI IT outsourcing rules. These require due diligence on providers, audit and inspection access for RBI and your auditors, exit and transition plans, and a board-approved outsourcing policy. Your contract needs explicit audit-right and data-return clauses.
  • CERT-In directions. Cyber incidents must be reported to CERT-In within six hours of being noticed, and ICT system logs kept for 180 days within India. The vendor's incident process has to deliver what you need well inside that window.

For most banks and larger NBFCs, the realistic shortlist is India-headquartered identity vendors, or global vendors with Indian data centers and an established local delivery team. Sanctions and PEP data is different. Lists from providers such as LSEG World-Check, Dow Jones and ComplyAdvantage are widely used in India; the question there is where the customer data you send for screening gets processed.

Per-Verification Costs and a Worked Monthly Budget

Indian KYC pricing is mostly per call, with platform and setup fees on top. The figures below are typical 2026 market ranges that vary with volume commitments, contract length and bundling. USD figures are approximate conversions. Confirm current pricing with each vendor.

ComponentTypical price per call (INR)Approx. USDMain cost driver
PAN verification1–5$0.01–0.06Volume tier
Aadhaar offline XML / QR / DigiLocker fetch3–15$0.03–0.18Bundling with OCR and face match
Aadhaar OTP e-KYC via KUA5–20$0.06–0.23KUA fees passed through
CKYCR search and download3–12$0.03–0.14Registry fees plus vendor margin
Face match and liveness2–10$0.02–0.12Passive vs. active liveness, deepfake checks
Bank account verification (penny drop)1–5$0.01–0.06Bank rails used
V-CIP platform fee per completed session25–120$0.30–1.40On-premise vs. private cloud, recording storage
Sanctions / PEP screening per customer2–25$0.02–0.30Data provider, ongoing monitoring

Fixed costs sit on top. Setup and integration commonly run $10,000–$75,000. An on-premise V-CIP license with installation can reach $50,000–$250,000 or more for large banks. Annual platform minimums of $15,000–$100,000 are common.

Worked example (hypothetical)

Say a mid-sized NBFC onboards 20,000 customers a month. Sixty percent finish a digital journey (PAN, Aadhaar offline verification, CKYCR and face match) at a combined INR 20 or so: about INR 2.4 lakh. The other 40% need V-CIP at roughly INR 80 per session in platform fees: about INR 6.4 lakh. Assume each agent completes around 1,000 sessions a month. Those 8,000 sessions then need eight agents plus two supervisors and auditors, roughly INR 3–4.5 lakh in staff costs.

The monthly total lands around INR 12–13.5 lakh (roughly $13,500–15,000), or INR 60–67 per onboarded customer. That's before sanctions screening, setup amortization and platform minimums.

The takeaway: V-CIP staffing usually outweighs the API bill. Negotiate for features that raise agent throughput, such as pre-filled data, automated face match and smart queuing, before you fight over a rupee on PAN checks.

Realistic Rollout Timelines From Contract to First Live Account

Timelines slip on approvals and security testing, not code. Plan around the slowest dependency. The durations below are typical ranges, not commitments.

WorkstreamTypical durationWhat usually delays it
API-based digital KYC (PAN, offline Aadhaar, face match)4–8 weeksConsent journey design, internal infosec review
CKYCR onboarding and integration6–10 weeksCERSAI registration, upload format testing
KRA integrations (SEBI intermediaries)4–8 weeksTesting with each KRA
V-CIP go-live3–6 monthsOn-premise infrastructure, VAPT and security audit, agent training
Aadhaar e-KYC access via KUA (non-bank)6–12 monthsRegulatory approval, KUA agreement, UIDAI audits
AML monitoring and FIU-IND reporting integration3–9 monthsData quality, scenario tuning, core system feeds

Phase it. Launch digital KYC with offline Aadhaar and CKYCR first. Add V-CIP once security testing is signed off, and keep a branch or assisted-onboarding fallback until V-CIP clears its first internal audit cycle. Put the board approval, outsourcing risk assessment and DPDP impact review in the plan from week one and run them alongside the build. Left until the end, they become your critical path.

Red Flags in Vendor Demos and a Shortlisting Checklist

Onboarding data feeds your AML system for screening, risk scoring, transaction monitoring and FIU-IND reports such as STRs and CTRs. Judge vendors on how cleanly that handoff works, not only on onboarding conversion.

Red flags

  • "Fully automated video KYC" sold as V-CIP, with no live official.
  • No on-premise or entity-controlled deployment option for V-CIP.
  • Full Aadhaar numbers visible in logs, exports or support screens.
  • Vague answers on where backups, disaster recovery or analytics data sit.
  • No concurrent-audit workflow.
  • Contracts without RBI inspection rights, data return or exit assistance.
  • Liveness never tested against deepfake or injection attacks, or a vendor unwilling to explain how it was tested.

Shortlisting checklist

  1. Map each product line to its regulator and list the mandatory KYC methods.
  2. Confirm your Aadhaar access level: e-KYC through a KUA, or offline only.
  3. Get written data-residency answers covering primary storage, backup, disaster recovery, logs and subprocessors.
  4. Ask for CKYCR and KRA upload rejection rates from the vendor's own monitoring, and walk through the fix workflow.
  5. Pilot on 500–2,000 real customers. Measure completion rate, agent minutes per session and audit rejection rate.
  6. Check that onboarding data maps cleanly to your AML system's customer risk model and periodic updation schedule.
  7. Have your compliance head and external legal counsel review the outsourcing and DPDP processor terms before signing.

Decision rule for any KYC software India shortlist: when two vendors are close on price, pick the one whose V-CIP deployment and audit workflow your internal auditors approve on first review. Re-engineering after an inspection finding costs far more than any per-call saving.

Frequently asked questions

Can an NBFC use Aadhaar e-KYC directly, or only offline verification?

Banking companies can use Aadhaar authentication directly. Most NBFCs need specific notification or approval and usually access e-KYC as a sub-AUA or sub-KUA through a licensed KUA. Without that approval, NBFCs can use Aadhaar offline XML, secure QR verification or DigiLocker documents with customer consent. Confirm your entity's current status with legal counsel before designing journeys around OTP or biometric e-KYC.

Can V-CIP run entirely on a vendor's public cloud?

Generally not as a plain public-cloud SaaS service. The RBI Master Direction requires V-CIP infrastructure to be housed in the regulated entity's own premises, with connections originating from its own secured network domain. Technology outsourcing is allowed if it follows RBI's IT outsourcing rules. Many banks use on-premise or entity-controlled private deployments. Ask the vendor to document exactly how its architecture meets the requirement, and have your compliance team sign off.

Does a CKYCR download replace our own KYC checks?

No. A CKYCR record reduces document collection, but you remain responsible for due diligence: risk categorization, beneficial ownership, screening and periodic updation. If the downloaded record is outdated or doesn't match what the customer provides, run fresh KYC and upload the updated record to the registry.

How much should we budget per onboarded customer in India?

As a typical 2026 market range, purely digital journeys often cost INR 10–40 per customer in API fees. Journeys that need V-CIP commonly reach INR 60–150 once agent staffing is included. Setup fees and annual platform minimums come on top, and pricing varies by volume and contract, so confirm with vendors.

How does the DPDP Act change our contracts with KYC vendors?

Under the DPDP Act and its Rules, your institution is generally the data fiduciary and the KYC vendor a processor, so accountability stays with you. Contracts should cover purpose limits, security safeguards, breach notification timelines, retention and deletion that respect PMLA record-keeping duties, and data return at exit. Because obligations phase in over roughly 18 months from late 2025, have a qualified legal professional review the final terms.

Do SEBI-regulated brokers need both KRA and CKYCR integrations?

Brokers and other SEBI intermediaries work primarily through KRAs for fetching, uploading and tracking KYC status. CKYCR integration is also expected in many cases and helps when customers already hold a KYC identifier from a bank or insurer. Check the latest SEBI circulars with your compliance team, and pick a vendor that supports both rather than building one later.

Written by the Adviser Hub Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.