Video KYC framework

Run video KYC on your own servers, with India’s V-CIP preset ready to go

An officer console, a customer link with nothing to install, one stamped recording per call, masked ID photos, maker-checker review and a signed evidence trail. Your servers and storage keep the records; MediaSFU carries the live call.

  • No app for customers
  • Records on your storage
  • Open source, MIT
Case VK-1042 · India V-CIPChecker approved
  • Recording with GPS and IST stamp6 min
  • Face, PAN and masked Aadhaar photos3 files
  • Random questions and answers6 of 6
  • Liveness and face-match checkslogged
  • Signed evidence bundleEd25519
Activity log verifiedHash chain and signature match
Example case · Sample data
Two ready presets

Pick the rules, keep the framework

A preset holds everything jurisdiction-specific: documents, masking rules, questions, consent text, time zone, countries and storage regions. The server enforces what matters; the rest is wording.

India V-CIP Default

Built around RBI’s video KYC process for banks and NBFCs, with profiles for SEBI-registered intermediaries and IRDAI insurers.

  • PAN, Aadhaar and other ID photos; the Aadhaar number must be masked before saving
  • Video within three working days of obtaining the ID data, with Sundays and your holidays excluded
  • IST date and time plus live location burned into the recording
  • Maker, checker and concurrent auditor, each a different person
  • S3 storage limited to the AWS Mumbai and Hyderabad regions

International ID KYC_PRESET=international

Passport, national ID card or residence permit, with neutral questions and no country-specific rules. Copy it to start your own jurisdiction.

  • Optional masking of the document number or MRZ
  • UTC on the recording, plus the officer’s local time
  • Any location, unless you set allowed countries or a boundary
  • Maker and checker, with an auditor step you can switch on
  • Pin storage to the regions your policy names
A call, start to finish

From a link to a reviewed, signed case

  1. Open a case

    The officer records the customer, the ID source and when it was obtained, then sends a one-time link from your domain.

  2. Customer gets ready

    In the phone’s browser: consent, live location, a camera and microphone check, then a waiting room. Nothing to install.

  3. The call

    The officer asks a random set of questions, captures face and document photos, masks numbers and runs the liveness and face-match aids.

  4. End it plainly

    Completed, interrupted or rejected. A dropped call never resumes: the customer starts a fresh session.

  5. Review and export

    A checker approves, an auditor clears where the preset asks for one, and the case exports as one signed evidence bundle.

What lands on your storage

Everything a reviewer needs, in one case

  • One continuous recording

    Recorded in the officer’s browser with live location and date and time burned in, uploaded in short chunks to your storage.

  • Face and document photos

    Captured on the call. The officer blacks out numbers before saving, and only the masked image leaves the browser.

  • Questions and answers

    Which questions were asked, in what order, and how the officer marked each answer.

  • Checks

    Liveness and face-match aids, or the result from your own vendor, stored beside the officer’s decision.

  • Tamper-evident activity log

    Every step is hash-chained per case and anchored in a server-wide chain, so an edited or missing entry shows up.

  • Signed export

    An Ed25519-signed bundle per case. Anyone with your public key can check it offline with one command.

What you plug in

A clear place for each of your vendors and systems

  • Liveness and face-match vendor

    If your policy needs a certified check, record your vendor’s result through the session checks API. The built-in checks assist the officer.

  • ID-check connectors

    India: Aadhaar e-KYC or offline XML, CKYCR, DigiLocker, PAN. Elsewhere: document chip, eID schemes, registries. The case records which source was used and when.

  • Screening

    Negative-list and sanctions screening feed the case’s screening fields and flags.

  • Officer sign-in

    Swap the built-in sign-in for your SSO in one function. Roles, training dates and the office-network check stay.

  • Storage and retention

    Encrypted files on your disk, or your S3 bucket with your keys, versioning and object lock for your retention period.

  • Location data

    Your IP-to-country database and, if you have one, an official boundary file for the GPS check.

A pilot in a day

From clone to a working pilot in one working day

The repo’s step-by-step guide takes an engineer or integrator from an empty VM to a pilot. Going live with real customers takes longer: your SOP, trained officers and security testing come first.

  1. Morning: Run it, then use real media

    Clone, set up and run a full call between two browser tabs with no account. Then add a MediaSFU staging key and run the headless check over real media.

  2. Midday: Deploy into your environment

    One VM or container: TLS, an encrypted data volume or bucket, your office network ranges, the location database, and real officer accounts with training dates.

  3. Afternoon: Make it yours with compliance

    Replace the sample consent text, review the question bank and holiday calendar, then run five test cases including a dropped call and a rejection.

npm install
npm run setup        # India preset; add -- --preset international
npm run build
npm start            # open /console, then the customer link in a second tab
Your call, your decision

The framework does the heavy lifting; your team stays in charge

Built in, and enforced by the server

  • Different people for each review step on the same case
  • Officer sign-in only from your network, with training dates on every account
  • Required masking and photos before a call can complete
  • The ID-age rule, allowed countries and storage regions from the preset

Yours to decide and own

  • Your KYC policy, SOP, consent text and officer training
  • Security testing and retention before real customers
  • The final decision on every customer

Meeting your regulator’s requirements stays your institution’s responsibility; the framework gives you the building blocks.

Questions

What lenders and integrators ask first

Does using the framework make us compliant?

No framework can do that on its own. It gives you the parts: the officer console, customer link, recording, masking, review steps and evidence trail. Whether a deployment meets your regulator’s rules depends on how you configure, integrate, test and operate it. The India requirement map in the repo shows what the framework does per paragraph and what stays with you; it is a starting point for your compliance team, not legal advice.

Where do recordings and customer data live?

On your servers and storage. Cases, photos, recordings and the activity log are written by the kit server you run. The kit does not use MediaSFU cloud recording, and rooms are created with AI notes off. MediaSFU sees pseudonymous seat names, not the customer’s name or documents.

How is the live call protected?

Media is encrypted on every network hop (DTLS-SRTP) and relayed by MediaSFU’s media servers, which store nothing. Your MediaSFU API key stays on your kit server; browsers only get a seat in their own room. The India preset asks MediaSFU for Asian media servers; that is a placement preference, not a guarantee.

Do customers need an app?

No. The customer link runs in the phone’s browser and is built for mobile data. Phones only allow camera and location on HTTPS, so you serve it from your own domain with TLS.

Can we use it outside India?

Yes. Start with the International ID preset, or copy it into a preset of your own: documents, masking rules, questions, consent text, time zone, allowed countries and storage regions all live in a few JSON files.

What does it cost?

The source is free under the MIT licence. Live calls are billed to your MediaSFU account at our published rates; hosting, storage and any vendors you connect bill you directly.

See a call from both sides in five minutes

Be the officer in one tab and the customer in another, with sample documents. Nothing is uploaded.