Skip to main content

Mobile Capture SDK

The Mobile Capture SDK provides the on-device capture components a verification session needs — document, face, liveness, and NFC — for Android and iOS, with a Flutter plugin for cross-platform apps. The SDK handles 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.
NFCTravelDocumentReaderReads the document's NFC chip (mobile only).

How capture works​

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

Captured media is protected in transit; the app never performs matching or scoring itself.

Securing the app​

Because capture runs on a device the Company does not control, integrators should harden their apps with platform attestation — Google Play Integrity API (Android) and App Attest (iOS) — to detect tampering and block fraud via modified apps.

Relationship to the IDV Toolkit​

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

See also​