VBIP stands for Video Based Identification Process: IRDAI's optional process for life, general and health insurers in India to complete KYC over a live, consent-based video call. It is set out in Annexure II of the IRDAI AML/CFT Master Guidelines 2022. An insurer using VBIP must start the call from its own domain, geotag the customer in India, stamp recordings with GPS, date and time, and keep any third-party or cloud hosting in India.

This guide is for insurance product, compliance and engineering teams who are building or buying a VBIP flow. It walks through the IRDAI VBIP guidelines clause by clause, with the paragraph number for every rule, and separates what IRDAI requires from what is only common practice. Each rule is cited by paragraph or clause, so you can check it against the IRDAI PDF. This guide explains the regulatory text for builders; it is not legal advice.

Building the video step of a VBIP flow?

VideoSDK gives you the video layer: a waiting lobby where your official admits the customer, a geo-tag recording template that watermarks the coordinates your app sends, and delivery of recordings to your own cloud bucket. A new account comes with a $20 credit.

Sign up and get API keysTalk to us

Key takeaways

  • VBIP is "an alternative (optional)" KYC process under para 3.17 of the IRDAI Master Guidelines on AML/CFT 2022, not a mandate.
  • The video call must be triggered from the insurer's own domain, not from a third-party service provider (Annexure II (k)).
  • Each session needs live geotagging in India, varied questions, a liveness check and a recording that carries GPS coordinates, date and time.
  • Aadhaar offline XML or Secure QR files used in VBIP must be no older than 3 days (Annexure II (g)).
  • The application needs CERT-In empanelled security testing, end-to-end encryption from the customer to the hosting point, and India hosting for any cloud or third-party location (Annexure II (q)).

What is IRDAI VBIP?

VBIP (Video Based Identification Process) is how insurers run paperless KYC over video: the insurer, or a person it has authorised and trained, holds a real-time, consent-based audio-visual interaction with the customer to collect identification details and KYC documents. The IRDAI Master Guidelines on AML/CFT 2022 (IRDAI/IID/GDL/MISC/160/8/2022, dated 1 August 2022, in force from 1 November 2022) define it in para 3.17 and set out the process in Annexure II.

VBIP runs in two modes. In online VBIP the customer joins from their own device. In face-to-face VBIP an authorised person of the insurer facilitates the session at the customer's end (Annexure II (n)). Both modes follow Annexure II and need the customer's informed consent; online VBIP adds extra caution and the preservation of details such as the IP address (Annexure II (l)).

Most teams first meet VBIP in insurance as "video KYC for insurance", and some guides call it IRDAI video KYC. The mechanics resemble bank video KYC, but the rules come from IRDAI, and several details differ (see the comparison below). VBIP covers identification and KYC only. Insurers that also examine applicants over video for underwriting run that as a separate process; see our guide to Video MER (Medical Examination Report). A pre-issuance verification call (PIVC), which checks that the customer understood the policy before it is issued, is another separate step.

The IRDAI VBIP guidelines live inside the insurer AML/CFT framework. That framework applies to all classes of life, general and health insurance business carried out by insurers, except reinsurance (para 2.2). It consolidated earlier circulars, including the September 2020 VBIP circular IRDA/SDD/CIR/MISC/245/09/2020, which it repealed. Pages that cite only the 2020 circular are working from superseded text.

IRDAI has amended the Master Guidelines at least three times since 2022. None of the amendments changes para 3.17, para 8.1.7, para 19.1 or Annexure II:

  • IRDAI/IID/CIR/MISC/71/3/2023 (20 March 2023) aligns the definition of a politically exposed person in para 3.14 with the PML Rules.
  • IRDAI/IID/CIR/MISC/177/10/2023 (10 October 2023) revises customer due diligence, politically exposed person, group-wide and high-risk-country provisions. It also adds to para 15.1, which covers new products, delivery mechanisms and technologies, that insurers "shall undertake ML / TF risk assessment prior to the launch or use of such products, practices and technologies". Plan that risk assessment before you launch a new VBIP flow.
  • IRDAI/IID/CIR/MISC/112/8/2024 (12 August 2024) updates the CKYCR provisions in para 12.

Is VBIP mandatory?

No. VBIP is optional. Para 3.17 calls it "an alternative (optional)" electronic process, and para 8.1.7 lists it as one of six alternative KYC methods an insurer may use:

  1. Aadhaar online authentication, subject to government notification under section 11A of the PMLA
  2. Aadhaar offline verification
  3. Digital KYC under the PML Rules
  4. VBIP, as a consent-based alternate method (para 8.1.7.4)
  5. The KYC identifier allotted by the CKYCR (Central KYC Records Registry)
  6. Officially Valid Documents (OVDs)

Alongside whichever method is used, para 8.1.7.7 adds PAN or Form 60 where applicable, and any other documents the insurer needs.

KYC in insurance does not require video: five of the six methods in para 8.1.7 involve no video call. In practice, an insurer picks VBIP when it wants to see the customer and the documents live, for example in remote sales.

Who must comply with VBIP?

Insurers. The Master Guidelines are addressed to insurers, and responsibility for client due diligence stays with the insurer (Annexure II (n)). Annexure II places every obligation on the insurer and mentions third parties only to limit them: the call cannot be triggered from a third-party service provider (Annexure II (k)), and a third-party or cloud hosting location must be in India (Annexure II (q)). Para 19.2 adds that where an insurer uses a third-party service provider for records, it must be satisfied that the provider's systems protect the data. The insurer keeps the details of every authorised person who facilitates a session (Annexure II (o)).

IRDAI VBIP guidelines: Annexure II clause by clause

Annexure II of the IRDAI Master Guidelines on AML/CFT 2022 has seventeen clauses, (a) to (q), covering identity sources, live location, the insurer's domain, recording, encryption and hosting. The table maps each clause to what a VBIP application has to do. Rule text is paraphrased from the IRDAI PDF; read the original before you sign off a design.

ClauseWhat IRDAI requiresTypical build response
(a) Identity sourcesRecord clear live video and collect identity through Aadhaar authentication (subject to government notification under section 11A of the PMLA) or Aadhaar offline verification (if the customer voluntarily submits Aadhaar), or an OVD from DigiLocker or through eSignOffer DigiLocker, Aadhaar offline (XML or Secure QR) and eSign steps beside the video room
(b) PANThe insurer may also verify PAN (wherever applicable): capture a clear image of the PAN card unless e-PAN is given, and verify it with the issuing authority; a printed e-PAN is not validIn-call image capture of PAN and a PAN database check
(c) Video clarityVideo clear, faces of customer and authorised person recognisable and uncoveredVideo quality checks and prompts before the call proceeds
(d) Live locationCapture the customer's live location (geotagging) to show they are in India, in both modesLocation permission and capture before or at call start
(e) Face and document matchMatch the photo and details in Aadhaar, OVD or PAN with the person on the callFace match support for the official
(f) Varied questionsVary the sequence or type of questions so the call is real-time, not pre-recordedA question set the official can randomise
(g) Aadhaar file ageAadhaar XML or Secure QR must be generated no more than 3 days before the VBIPA timestamp check on the offline Aadhaar file
(h) Activation after verificationActivate a policy or service only after proper verification by the insurerA back-office review step after the call
(i) Encryption and livenessA real-time, secured, end-to-end encrypted interaction, with quality good enough to identify the customer, plus a liveness checkEncrypted media path, quality monitoring, liveness detection
(j) Security auditSoftware and security audit and validation before roll-out and from time to timeAudit evidence from the vendor and the insurer
(k) Own domain and logsCall triggered from the insurer's own domain, not a third party; run by the insurer or authorised persons; activity log and official's credentials preservedEmbed the call in the insurer's app or site; log every action with the official's identity
(l) Recording stampRecording bears GPS coordinates, date (DD:MM:YY) and time (HH:MM:SS); for online VBIP, also keep the IP address and similar detailsBurn-in or attached metadata on the recording, plus IP logs
(m) AI useAI and face matching are encouraged, but identification stays the insurer's responsibilityAI as a helper; we recommend a human reviewer on every case
(n), (o) Authorised personsAuthorised persons facilitate face-to-face VBIP only at the customer's end; insurer keeps their detailsAgent roles and an authorised-person register
(p) Aadhaar redactionRedact or black out the Aadhaar number as per the PML RulesMasking in screenshots, recordings and stored images
(q) Security and India hostingFollow IRDAI cyber security guidelines; CERT-In empanelled testing; end-to-end encryption from customer to hosting point (minimum standards such as AES 256); India hosting for third-party or cloud locationsSecurity test reports, encryption settings and an India region for media and recordings

The two clauses that decide most build choices are (k) and (q). Clause (k) rules out a hosted vendor link as the place where the call starts. Clause (q) rules out recordings stored outside India when they sit with a third party or in the cloud.

VBIP process flow

A VBIP session that follows Annexure II can run in the order below. Only two points of order are fixed: consent comes before the interaction, and activation comes after verification (Annexure II (h)). The rest is one reasonable sequence; the clause next to each step says which rule the step meets.

Video SDK Image
VBIP session flow under IRDAI Annexure II, with the clause that drives each step.
  1. Start on the insurer's domain. The customer opens the insurer's own app or website and starts the video step there (Annexure II (k)).
  2. Record informed consent. The customer agrees to the VBIP before the interaction (Annexure II, opening paragraph).
  3. Capture live location. The app records the customer's location to show they are in India (Annexure II (d)).
  4. Connect the live call. A trained official of the insurer, or an authorised person, joins. The video must be clear, with both faces visible (Annexure II (c)).
  5. Collect identity. The customer either shares Aadhaar, by authentication or by an offline XML or QR file generated no more than 3 days earlier, or shares an OVD through DigiLocker or eSign. Where the insurer also verifies PAN, the customer shows the PAN card for image capture or provides e-PAN. Clauses (a), (b) and (g) apply.
  6. Check liveness and match. The official varies the questions, runs a liveness check and matches the face with the documents (Annexure II (e), (f), (i)).
  7. Close and store the recording. The recording carries GPS coordinates, date and time; the insurer keeps the activity log, the official's credentials and, for online VBIP, the IP address (Annexure II (k), (l)).
  8. Verify, then activate. A back-office check confirms the case before the policy or service goes live (Annexure II (h)).

Records relating to verification of a client's identity are kept for five years under para 19.1, in line with Rule 5 of the PML Rules. Para 19.1 does not say when that period starts, but para 19.5 keeps customer identification data obtained through customer due diligence for at least five years after the business relationship ends. Confirm the start point for your product with your compliance team.

Technical architecture for VBIP

A VBIP system has four parts: the customer-facing app on the insurer's domain, a real-time video layer, a verification back office, and compliant storage. The video layer carries the call and the recording. The back office holds the case, the documents, the review queue and the activity log.

The insurer's own domain rule

Annexure II (k) says the audio-visual interaction "shall be triggered from the domain of the insurers itself". For a technology supplier, that means the customer never leaves the insurer's app or website to join a call on a vendor-branded page. One common approach is an embedded video SDK: the insurer's backend creates the session and tokens, and the call UI runs inside the insurer's own web or mobile app. The media still flows through the video provider's servers, so confirm with your compliance team that your reading of (k) accepts this design.

The same clause says the insurer or its authorised persons operate the process. A vendor can supply the software and the infrastructure, but the official on the call works for the insurer. For logging, the IRDAI VBIP guidelines require the insurer to preserve the activity log along with the credentials of the official performing the VBIP (Annexure II (k)). For online VBIP, the insurer must also preserve the IP address and similar details (Annexure II (l)).

Security testing, encryption and India hosting

Annexure II (q) sets four technical conditions:

  1. The Video KYC application and its APIs get gray box and white box application security testing from a CERT-In empanelled vendor, and every reported vulnerability is fixed before production.
  2. The hosting infrastructure gets a vulnerability assessment and secure configuration review from a CERT-In empanelled vendor.
  3. End-to-end encryption runs from the customer to the hosting point of the application, with minimum standards such as AES 256.
  4. If the application or the recordings sit at a third party or in the cloud, that location is in India.

Clause (q) also points to IRDAI's cyber security guidelines "as amended from time to time". The current text is the IRDAI Information and Cybersecurity Guidelines, 2026 (6 April 2026). It does not mention VBIP, so read it with your security team for the general controls, and take the VBIP-specific rules from Annexure II.

Note the wording of (q): "end-to-end encryption from the customer/beneficiary to the hosting point of the Video KYC application". Clause (i) also asks for an end-to-end encrypted interaction. How a given video platform meets both, especially when the session is also recorded, is a question to settle with the vendor in writing.

VBIP vs V-CIP (RBI video KYC)

VBIP and V-CIP (Video based Customer Identification Process) are the insurance and banking versions of video KYC. They share most of the mechanics, so the same video stack can often serve both, but the rulebooks are separate. The table compares the points teams most often mix up.

PointVBIP (insurers)V-CIP (commercial banks)
Regulator and textIRDAI Master Guidelines on AML/CFT 2022, Annexure IIRBI Commercial Banks KYC Directions 2025 (RBI/DOR/2025-26/169), para 26 and 27
Where the call startsTriggered from the insurer's own domain, not a third party (Annexure II (k))Originates from the bank's own secured network domain; infrastructure in the bank's own premises (para 27(1)(i))
CloudThird-party or cloud hosting must be in India (Annexure II (q))Allowed if the bank owns the data and the cloud or technology provider retains none (para 27(1)(i))
RecordingsGPS, date and time on the recording (Annexure II (l))GPS, date and time stamp; all data and recordings stored in India (para 27(1)(iv), 27(3)(i))
Assisted modeAn authorised person of the insurer facilitates face-to-face VBIP at the customer's end (Annexure II (n))Assisted V-CIP through Business Correspondents, only at the customer's end (para 27(2)(xiv))

The RBI issued the Commercial Banks KYC Directions 2025 on 28 November 2025, and para 80 repeals the existing KYC directions for commercial banks. If a bank partner sends you a V-CIP checklist that still cites the 2016 Master Direction, ask for the current paragraph numbers. For a fuller walkthrough of V-CIP, see our guide to how video KYC works under RBI's 2025 Directions.

Common mistakes in VBIP implementation

Many VBIP problems come from reading bank V-CIP habits or vendor marketing into the IRDAI text. The first three below appeared in published VBIP guides, including an earlier version of this page; the rest are clauses those guides leave out.

  1. Calling VBIP mandatory. It is optional (para 3.17). Calling it mandatory gives product owners a constraint the rule does not set.
  2. Hard-coding business hours. Annexure II sets no time window for sessions. The practical limit is when trained officials are on shift, which is an operational choice for the insurer.
  3. Asking the customer to hold an Aadhaar card to the camera. Aadhaar comes in through authentication or offline XML or QR, and OVDs through DigiLocker or eSign (Annexure II (a)). Where the insurer verifies PAN, the card shown on camera is PAN, or the customer provides e-PAN (Annexure II (b)). Any Aadhaar number that appears must be redacted (Annexure II (p)).
  4. Starting the call on a vendor URL. A link to a vendor-hosted page breaks Annexure II (k). Embed the call in the insurer's own app or site.
  5. Skipping the 3-day check on Aadhaar offline files. An XML or QR older than 3 days fails Annexure II (g). Read the generation timestamp from the file and reject stale ones.
  6. Activating the policy when the call ends. Annexure II (h) requires proper verification by the insurer first. Build a review step between the call and activation.
  7. Letting AI decide. AI and face matching are encouraged, but the responsibility for identification rests with the insurer (Annexure II (m)). We recommend that a human reviewer sign off on every case.

Two more habits are worth dropping: assuming IRDAI sets a latency target, and assuming a fixed deadline for producing an audit record. Annexure II sets neither; it asks for quality "adequate to allow identification of the customer/ beneficiary beyond doubt" (Annexure II (i)). Test call quality on the networks your customers actually use.

Sample VBIP test cases

A test case per clause makes the review faster, because each Annexure II stipulation becomes a pass or fail check. The cases below are suggestions built from the clause text, not an IRDAI checklist; extend them to your own flow.

ClauseTestPass condition
(d)Start a session with location permission deniedThe call does not proceed until live location is captured
(g)Submit an Aadhaar offline XML generated 4 days earlierThe file is rejected before verification continues
(k)Open the session from a link outside the insurer's app or siteThe call cannot start outside the insurer's domain
(l)Play back a stored online VBIP recordingGPS coordinates, DD:MM:YY date and HH:MM:SS time are on the recording, and the IP address is in the case record
(h)End the call without back-office approvalThe policy or service stays inactive
(p)Store a frame in which an Aadhaar number is visibleThe stored image shows the number redacted
(a)Try to proceed with an OVD photo uploaded outside DigiLocker or eSignThe document step does not accept it
(i)Hold a printed photo or replay a video to the cameraThe liveness check fails and the official is alerted
(q)Review the security test report before go-liveGray box and white box tests by a CERT-In empanelled vendor, with every reported vulnerability closed

Building VBIP on a video SDK

The common pattern is to buy the real-time video layer and build the rest. The insurer's app hosts the call UI, the insurer's backend creates rooms and access tokens and holds the case, and the video platform carries media, the waiting lobby and the recording. This keeps the call inside the insurer's app and leaves the KYC decision with the insurer's systems.

VideoSDK's video KYC solution and its video KYC guide for React follow that pattern. It covers a customer who waits in a lobby until the agent admits them, a recording that starts once the customer is admitted, and a recording-started webhook to the backend.

What the VideoSDK docs cover

Documented features relevant to Annexure II:

  • Recordings in your own bucket. Recordings can be stored in the insurer's own AWS S3, Azure Blob or GCP Cloud Storage bucket, configured per API key (recording storage). Choose an India region for that bucket. That covers where recordings are finally stored; talk to us to confirm where recordings are processed before upload on your plan.
  • Recordings encrypted at rest. Recordings can be encrypted with AES-256-GCM or AES-256-CTR using the insurer's RSA public key, set per API key (recording encryption). It cannot be turned on together with transcription and summaries on the same API key.
  • GPS stamp on the recording. A custom recording template can overlay the customer's latitude and longitude, sent from the app over PubSub (geo-tagged recording). The overlay shows the coordinates your app supplies and is not independent proof of location, so capture and check location in your own app as clause (d) requires. Add the date and time format that clause (l) asks for in the same template.
  • India media region. Geo-fencing can pin sessions to the INDIA region, on the Enterprise plan only (geo-fencing).
  • IP-based access rules. Geo IP Restriction can allow or deny connections based on the customer's IP address on the Enterprise plan only, which adds a network-level signal alongside the live location that clause (d) requires.

Encryption and recording caveats

Plan the encryption design early. VideoSDK's E2EE page says recording and transcription are not supported while end-to-end encryption (E2EE) is on, and clause (l) needs a recording. Our guide to end-to-end encryption in video calls explains what E2EE protects and where it stops. Talk to us about how a recorded VBIP session can meet clauses (i) and (q) on your plan, and have your compliance team confirm that an embedded call started by your backend meets your reading of clause (k).

The same docs also list OCR, Face Match and Face Spoof Detection APIs, on the Enterprise plan only. Our guide to building a video KYC agent dashboard shows how the official's interface can call OCR and Face Match during the session. PAN database checks, DigiLocker, eSign and Aadhaar offline verification come from other providers, and the KYC decision stays with the insurer.

To start building, follow the video KYC guide, then extend the test cases above to every Annexure II clause before your security review.

Build your VBIP flow on VideoSDK. Sign up for VideoSDK to get API keys and run the video KYC guide; a new account comes with a $20 credit (pricing). Planning a VBIP rollout that needs India geo-fencing, the identity APIs or recordings in your own bucket? Talk to our team.

Glossary

  • Authorised person: Someone the insurer authorises and specifically trains for face-to-face VBIP (para 3.17); they facilitate sessions only at the customer's end.
  • OVD (Officially Valid Document): An identity document defined in rule 2(d) of the PML Rules 2005; in VBIP it arrives through DigiLocker or eSign.
  • Aadhaar offline verification (Aadhaar XML, Secure QR): Identity verification from a digitally signed Aadhaar XML file or Secure QR code; for VBIP it must be generated no more than 3 days before the session.
  • CKYCR (Central KYC Records Registry): The central registry that issues a KYC identifier, which is a separate KYC route from VBIP.
  • CERT-In empanelled vendor: A security auditor on the Indian Computer Emergency Response Team's approved list, required for VBIP application and infrastructure testing.
  • V-CIP (Video based Customer Identification Process): The RBI's video KYC process for banks and other RBI-regulated entities.
  • Geotagging: Capturing the customer's live location during the session to show they are physically in India.

FAQ

What is the full form of VBIP?

VBIP stands for Video Based Identification Process. Para 3.17 of the IRDAI Master Guidelines on AML/CFT 2022 defines it as "an alternative (optional) electronic process of Identification/ KYC in paperless form". The insurer, or an authorised person it has specifically trained for face-to-face VBIP, carries it out through a real-time, consent-based audio-visual interaction with the customer. Some older articles write "Video Based Identification Procedure"; the IRDAI Master Guidelines use "Process".

Can VBIP be done face to face?

Yes. Annexure II allows VBIP online, with the customer on their own device, or face to face, where an authorised person of the insurer facilitates the session at the customer's end (Annexure II (n)). The insurer keeps that person's details (Annexure II (o)), and both modes need geotagging in India.

What is the difference between VBIP and video KYC in banking?

VBIP is IRDAI's video KYC process for insurers, set out in Annexure II of the 2022 AML/CFT Master Guidelines. Video KYC in banking is V-CIP under the RBI's KYC Directions 2025, which are issued separately for each type of regulated entity. Both require the call to start from the regulated entity's own domain. The RBI also requires the bank's own premises (or bank-owned data on cloud) and lets Business Correspondents assist; IRDAI lets an insurer's authorised person facilitate face-to-face VBIP.

Can an InsurTech platform conduct the VBIP session on behalf of the insurer?

An InsurTech can supply the software, but the session has to be triggered from the insurer's own domain and operated by the insurer or its authorised persons (Annexure II (k)). In practice the InsurTech's video layer runs inside the insurer's app, and the official on the call acts for the insurer, which keeps the activity log and the official's credentials.

How long must VBIP records be kept?

Para 19.1 of the 2022 Master Guidelines requires insurers to keep records relating to verification of client identity for five years, in line with Rule 5 of the PML Rules. Para 19.1 does not state when that period starts, but para 19.5 keeps customer identification data obtained through customer due diligence for at least five years after the business relationship ends, so confirm the start point with your compliance team. Transaction records under Rule 3 are kept five years from the date of transaction, and records required by other laws follow those laws, but for at least five years from the end of the business relationship. Annexure II (l) adds that recordings carry GPS coordinates, date and time stamps.

Which documents can a customer use in a VBIP session?

The customer can verify identity through Aadhaar authentication or Aadhaar offline verification (with an XML or Secure QR no older than 3 days) if they choose to submit Aadhaar, or an OVD issued to DigiLocker or shared through eSign (Annexure II (a), (g)). The insurer may also verify PAN by capturing an image of the card on the call; a printed e-PAN is not valid (Annexure II (b)).

Are there permitted hours for VBIP sessions?

No. Annexure II of the IRDAI Master Guidelines does not set any time window for VBIP sessions. It requires a live, real-time interaction run by the insurer or its authorised persons, so the practical limit is when trained officials are available. When to offer sessions is an operational choice for each insurer.