Skip to main content

Web Capture Components

The Web Capture Components provide the in-browser capture a verification session needs — document, face, and liveness — for browser-based journeys, with no app install required. They deliver the same functionality as the Mobile Capture SDK, except for NFC chip reading, which is available only on the mobile SDK. The components handle capture and quality guidance; all biometric processing runs server-side through the Capture & Workflow API.

Capture components​

The API hands back a nextStep naming the component to launch:

ComponentPurpose
DocumentCaptureAuto-capture of an identity document (front and back where applicable).
FaceCaptureAuto-capture of a selfie with real-time quality guidance.
SmileLivenessActive liveness — smile challenge.
MagnifeyeLivenessActive liveness — MagnifEye challenge.
MultirangeLivenessActive liveness — distance/range challenge.

NFC chip reading (NFCTravelDocumentReader) is not available in the browser — use the Mobile Capture SDK for flows that require it.

How capture works​

  1. The page launches the component named in nextStep.
  2. The component captures data in the browser with real-time guidance, and returns it to the page.
  3. The page submits the data via the Capture & Workflow API; the server validates quality and either advances or requests a retake.

Web components only capture — quality validation, matching, liveness, and scoring all run server-side. Captured media is protected in transit.

Relationship to the IDV Toolkit​

These components are built within the Innovatrics' IDV Toolkit. For low-level details — installation, browser APIs, customization, localization — refer to the Toolkit documentation; this page covers how the components fit a Platform session.

See also​