Video KYC development · India
Video KYC development for Indian banks — V-CIP flows built to RBI's Master Direction.
Appsarmy builds V-CIP video KYC systems for Indian banks and NBFCs. The RBI Master Direction puts the session inside your own secured network domain, which is precisely why a hosted widget cannot carry it — so this is an integration engagement, not a product sale. Aadhaar and DigiLocker identity pulls, geo-tagged recordings, in-India storage, and the audit gates built into delivery. It is a specialist corner of our fintech app development practice. For the Gulf, see video KYC development in the UAE.
The parts of a V-CIP system that have to be built, not bought.
A video KYC product can supply you with face matching, liveness detection, and a video pipeline. What it cannot supply is a session that terminates inside your own network domain, an identity pull against your own Aadhaar entitlements, and a write path into your core and CKYCR. That is the work.
The V-CIP session, in your domain
The customer-facing video journey and the officer console, deployed so the V-CIP connection originates from your own secured network domain as the Master Direction requires. End-to-end encryption from the customer's device to the hosting point, and consent recorded in an auditable, alteration-proof form.
Why that rules out a widgetIdentity pulls and document handling
OTP-based Aadhaar e-KYC, offline Aadhaar XML and Secure QR with the three-working-day window enforced in code, CKYCR retrieval by KYC Identifier, and DigiLocker OVD e-documents. Aadhaar number redaction, PAN capture and verification against the issuing authority, and rejection of printed e-documents.
Core integration, in detailFace match & liveness
Liveness and spoof detection with high-accuracy face matching against the Aadhaar or OVD photograph — designed so the check does not exclude persons with special needs, since the direction requires that.
Geo-fencing & IP controls
Blocking connections from IP addresses outside India and from spoofed addresses, with live GPS coordinates and a date-time stamp written into the recording itself.
Officer console & SOP
The console your trained officials actually work in: question randomisation, the negative-list and prior-rejection check, single-file recording discipline, and a rejection path when prompting occurs.
Evidence & retention
Recordings, activity logs, and officer credentials stored in systems located in India, date-time stamped for historical search, and wired into your record-management rules rather than bolted beside them.
The session has to end inside your estate.
This is the clause that decides build versus buy. The Master Direction requires V-CIP infrastructure to be housed in the regulated entity's own premises, with the connection originating from its own secured network domain. Where the deployment is on cloud, the entity must own the data, and all data including the video has to move to entity-owned or leased servers immediately after the process — nothing retained by the provider. A SaaS video KYC widget running the session on a vendor domain does not meet that, however good its face matching is. Components can be licensed; the session cannot be outsourced.
Where V-CIP work actually lands.
Most V-CIP programmes are not greenfield. They are a bank with a partial stack, a conversion deadline, or an existing vendor that cannot satisfy the domain clause. These are the shapes the work takes.
Full V-CIP onboarding journey
Customer app or web journey, officer console, identity pulls, recording pipeline, and the account-opening write path — delivered as one system with the domain and residency constraints designed in from the first sprint rather than retrofitted.
OTP e-KYC account conversion
An account opened through non-face-to-face Aadhaar OTP e-KYC cannot stay operational beyond a year without full identification. We build the conversion campaign path: cohort selection, invitation, V-CIP completion, and the status change in the core.
Re-KYC and periodic updation
V-CIP for KYC updation and periodic updation of existing customers, including the current-address capture when it differs from the OVD and the confirmation of the customer's economic and financial profile during the session.
Bringing an existing vendor in-domain
Where a bank already licenses face match and liveness components, re-architecting so the session terminates inside the entity's network and no video is retained by the provider — keeping the models, moving the boundary.
Assisted V-CIP with a BC network
Assisted V-CIP is permitted only where a Business Correspondent helps at the customer end, with BC details maintained and the bank ultimately responsible. We build the BC-side tooling and the audit trail that responsibility implies.
The app layer around it
V-CIP rarely ships alone. It arrives inside a banking app, which is the work we do on Flutter and native mobile and, where the core is Oracle's, on OBDX.
The audit gates are scoped before the screens.
Clause-to-control map
Every V-CIP requirement mapped to the component that satisfies it and the evidence that proves it. This document is what your auditor and your supervisor will actually read, so it is written first, not last.
Domain & residency design
Where the session terminates, where video lands, what moves off provider infrastructure and when. Decided before any vendor component is chosen, because it constrains which components are usable at all.
Identity route selection
Which of the four permitted identity routes your flow uses, in what priority, with what fallback — and how the three-working-day offline Aadhaar window is enforced rather than trusted.
Build
Short cycles with a working build each sprint: journey, console, pipeline, integration. The negative-list check, question randomisation and single-file recording discipline are features, not polish.
VAPT & CERT-In audit
Vulnerability assessment, penetration testing and security audit by CERT-In empanelled auditors before rollout, with critical gaps closed first — plus the functional, performance and maintenance testing of the application and its APIs.
Concurrent audit wiring
Accounts opened through V-CIP become operational only after concurrent audit, so that gate is built into the workflow with the evidence the auditor needs already assembled per account.
What a V-CIP stack is made of.
Integration specialists, not an identity vendor.
We build the layer products can't
Identity vendors sell models and SDKs; they cannot sell you a session that terminates in your own domain or a write path into your core. That boundary work is the whole engagement, and it is the part the Master Direction is strictest about.
Core banking is our ground
Our fintech work is integration-led: core banking integration, OBDX mobile on a live FLEXCUBE deployment, and banking apps built to an audit bar. V-CIP ends in the core, which is where most of its difficulty lives.
Vision we run on-premise
Face match and liveness are inference workloads with a residency constraint, which is the same problem we write about in on-premise model deployment and computer vision. Keeping them inside the estate is routine for us.
We are explicit about the limits
We do not hold Aadhaar authentication licences, and we do not operate your V-CIP sessions — RBI requires your own trained officials to do that. We build what they operate, and we would rather say so on this page than in a kick-off meeting.
Work with us the way that fits.
V-CIP readiness assessment
A fixed engagement that maps your current stack against the Master Direction clause by clause and returns a gap list, an architecture, and a build plan you can fund.
Fixed-scope V-CIP build
A defined system — journey, console, identity pulls, integration — with written scope, clear price, and the audit gates sequenced into the plan.
Hire banking integration engineers
Augment your team or your existing vendor with senior engineers who know core integration, on-prem inference, and what an auditor asks for.
Video KYC and V-CIP questions.
Can a bank just buy a video KYC product instead of building one?
Only partly. The Master Direction requires V-CIP infrastructure housed in the regulated entity's own premises, with the connection originating from its own secured network domain. On cloud, the entity must own the data and all data including video must move to entity-owned or leased servers immediately, with nothing retained by the provider. Components can be licensed; the session has to terminate inside your estate.
What does RBI require in the recording itself?
Live GPS coordinates and a date-time stamp, with quality good enough to identify the customer beyond doubt. Pauses or reconnections must not create multiple video files, and a dropped call needs a fresh session. All data and recordings are stored in systems located in India, date-time stamped for historical search, with the activity log and the officer's credentials preserved.
Which identity documents can a V-CIP flow use?
One of four routes: OTP-based Aadhaar e-KYC, offline Aadhaar verification, CKYCR records via the KYC Identifier, or OVD e-documents including through DigiLocker. The Aadhaar number is redacted. Offline Aadhaar XML or Secure QR must be no older than three working days. PAN is captured except for e-PAN and verified against the issuing authority; a printed e-document, e-PAN included, is not valid.
Do you hold Aadhaar authentication licences?
No. Aadhaar authentication and e-KYC access run through your own entitlements or a licensed provider you appoint — we build the flow and the controls around that access, not the licence. Likewise RBI requires V-CIP to be conducted by your specially trained officials, so your staff operate it and we build what they operate.
What has to be true before going live?
VAPT and a security audit by CERT-In empanelled auditors before rollout and periodically after, with critical gaps closed first. Functional, performance and maintenance testing of the application and its APIs. And per account, not per system: accounts opened through V-CIP become operational only after concurrent audit.
How does the system stop a session being faked?
Connections from IP addresses outside India and spoofed addresses are blocked. Face liveness and spoof detection plus high-accuracy matching are required, and AI may be used — but the entity stays ultimately responsible. Questions must vary so the session is demonstrably real-time, and any prompting of the customer means rejection. The liveness check must not exclude persons with special needs.
Does V-CIP work for existing customers and re-KYC?
Yes — for new individual customers, proprietors, authorised signatories and beneficial owners, and also to convert accounts opened through non-face-to-face Aadhaar OTP e-KYC, plus KYC updation and periodic updation. That conversion path has a deadline attached: an OTP-based e-KYC account cannot stay operational beyond a year without full identification, so a backlog of OTP-opened accounts is a dated liability.
Let's build your V-CIP system.
business days