Identity · V-CIP
The API behind FinHub's Video KYC products — start a session, run liveness and face match, capture documents and consent, and retrieve the sealed record.
Overview
What the Video KYC API does
This is the API layer. It starts and manages a video session, runs liveness and face match against the customer's identity document, extracts document fields with OCR, and records geotagged, time-stamped consent — returning a session record sealed to a tamper-evident audit trail. Which product it serves decides who runs the session: agent-led Video KYC puts a trained official on the call for RBI V-CIP, while Intelli VKYC runs the session automatically where a live official is not required.
Inputs
- Customer & session details
- ID document
- Consent artifact ID
Returns
- Session status & recording reference
- Liveness & face-match scores
- Extracted document fields
- Geotag & timestamp
POST /v1/kyc/vcip/session
How it works
Three steps to a verified result
Start the V-CIP session
Launch a live video session with the customer and capture purpose-bound consent.
Verify in real time
Run liveness, face match against the ID and OCR field extraction during the call.
Seal the record
Store the encrypted recording, scores and geotag, sealed to your audit trail for RBI review.
Use cases
Where teams use Video KYC
- Remote account opening for banks & NBFCs
- Digital lending onboarding
- Insurance policy issuance
- Re-KYC without a branch visit
FAQ
Video KYC API — FAQs
Common questions about FinHub's Video KYC API.
Yes. The flow is aligned to the RBI's Video-based Customer Identification Process (V-CIP) guidelines, with liveness, face match, geotagging, time-stamping, encryption and an auditable session record.
More verification APIs
Explore related APIs
Ready to add Video KYC to your flow?
Book a demo and see the API return a verified result on your own test data in minutes.