ID Capture Module

The ID Capture module captures front and back images of identity documents (ID cards, passports) with ML-powered quality checks and validation. It also supports digital ID verification through supported device wallets and bank redirects. For implementation details, see Digital ID: mDL Verification and Digital ID: Bank Redirect.

This module follows the camera-capture pattern, plus dedicated states for mandatory consent and manual file upload. See the patterns page for the shared lifecycle; the rest of this page covers ID-specific config, capture properties, and methods.

Tag

<incode-id> is a standard Web Component. Importing the UI subpath registers the custom element; importing the CSS applies the module's styles.

import '@incodetech/web/id';
import '@incodetech/web/id/styles.css';

Properties

Set these as JavaScript properties on the element (not as HTML attributes):

WASM Requirements

The ID Capture module uses WebAssembly for document detection, blur/glare quality checks, and perspective correction. Pre-warm WASM during setup() so models are ready before the user reaches the camera step:

await setup({
  apiURL: 'https://demo-api.incodesmile.com',
  token: 'your-session-token',
  wasm: { pipelines: ['idCapture'] },
});

See WASM Configuration for self-hosted paths and the lower-level warmupWasm() API.

Usage

Vanilla HTML / TypeScript

<incode-id></incode-id>

<script type="module">
  import { setup } from '@incodetech/core';
  import '@incodetech/web/id';
  import '@incodetech/web/id/styles.css';

  await setup({
    apiURL: 'https://demo-api.incodesmile.com',
    token: 'your-session-token',
    wasm: { pipelines: ['idCapture'] },
  });

  const id = document.querySelector('incode-id');
  id.config = {
    showTutorial: true,
    enableId: true,
    enablePassport: false,
    autoCaptureTimeout: 5,
    captureAttempts: 3,
  };
  id.onFinish = () => console.log('ID captured!');
  id.onError = (err) => console.error('ID error:', err);
</script>

React

React 18 or earlier: add the one-time JSX augmentation from Framework Integration → TypeScript: JSX support for incode-* tags. React 19+ doesn't need it, and can also use the simpler form from Framework Integration → React 19+ shortcut.

import { useEffect, useRef } from 'react';
import { setup } from '@incodetech/core';
import type { IdCaptureConfig } from '@incodetech/core/id';
import '@incodetech/web/id';
import '@incodetech/web/id/styles.css';

type IdElement = HTMLElement & {
  config: Partial<IdCaptureConfig>;
  onFinish: () => void;
  onError: (error: string | undefined) => void;
};

await setup({
  apiURL: 'https://demo-api.incodesmile.com',
  token: 'your-session-token',
  wasm: { pipelines: ['idCapture'] },
});

export function IdCapture() {
  const ref = useRef<IdElement>(null);

  useEffect(() => {
    const el = ref.current;
    if (!el) return;
    el.config = {
      showTutorial: true,
      enableId: true,
      enablePassport: false,
      autoCaptureTimeout: 5,
      captureAttempts: 3,
    };
    el.onFinish = () => console.log('ID captured!');
    el.onError = (err) => console.error('ID error:', err);
  }, []);

  return <incode-id ref={ref} />;
}

For Angular (CUSTOM_ELEMENTS_SCHEMA) and Vue (compilerOptions.isCustomElement) setup, see Framework Integration.

Workflow vs Flow

In a Dashboard-driven Flow (<incode-flow> / createOrchestratedFlowManager), ID is a single step that captures the document and runs server-side processing (/process/id). This is what <incode-id> and createIdCaptureManager do by default.

In a server-driven Workflow (<incode-workflow> / createWorkflowManager), the workflow engine emits ID handling as two distinct nodes:

1. ID_CAPTURE: runs idCaptureMachine for the capture portion only, then advances without calling /process/id. Enabled by setting IdCaptureConfig.skipProcessId = true (the workflow engine sets this automatically on the ID_CAPTURE node's config).
2. ID: runs the headless id-verification module (@incodetech/core/id-verification, createIdVerificationManager) which invokes /process/id on its own. The orchestrator renders the corresponding <incode-id-verification> shell while the request is in flight. No UI work needed.code

This split lets the Workflow inject custom logic (manual review, retries, branching) between capture and verification. For a single-step capture+verify flow, keep using the standard <incode-id> / createIdCaptureManager path; skipProcessId defaults to false, so processing runs inline as before.

The id-verification module ships:

• createIdVerificationManager from @incodetech/core/id-verification: headless manager for the verification half (used by Workflow's ID node, also usable headlessly outside Workflow).
• IdVerificationConfig: config type for the manager.
• <incode-id-verification>: Preact UI shell registered automatically by the orchestrator; no public @incodetech/web/id-verification import path, since the orchestrator owns the mount.

Standalone ID verification

After SDK setup and session activation, createIdVerificationManager({ config }) can process an ID already captured in that session. An empty config uses the first ID.

Either isSecondId: true or idRank: 'SECOND_ID' selects the second ID; otherwise the first ID is processed.

The state variants carry only status. The manager also exposes subscribe(), getState(), and stop(). Unsubscribe and call stop() when your host tears down; create a new manager for a new run.

import { createIdVerificationManager } from '@incodetech/core/id-verification';

// After setup and activation of the session containing the captured ID:
const verification = createIdVerificationManager({ config: {} });
const unsubscribe = verification.subscribe((state) => {
  if (state.status === 'expired') {
    // Show expiration feedback; call verification.continue() on confirmation.
  }
});
verification.load();

function disposeVerification() {
  unsubscribe();
  verification.stop();
}

Headless Mode

For complete UI control, use the createIdCaptureManager from @incodetech/core/id.

Quick Start

import { setup } from '@incodetech/core';
import { createIdCaptureManager } from '@incodetech/core/id';
import { resolveDashboardModuleConfig } from '@incodetech/core/flow';
import { warmupWasm } from '@incodetech/core/wasm';

await setup({
  apiURL: 'https://demo-api.incodesmile.com',
  token: 'your-session-token',
});

await warmupWasm({
  wasmPath: '/wasm/webLib.wasm',
  glueCodePath: '/wasm/webLib.js',
  modelsBasePath: '/wasm/models',
  pipelines: ['idCapture'],
});

const config = await resolveDashboardModuleConfig({ moduleKey: 'ID' });
const manager = createIdCaptureManager({ config });

manager.subscribe((state) => {
  console.log('Status:', state.status);

  if (state.status === 'capture') {
    console.log('Mode:', state.currentMode); // 'front' or 'back'
    console.log('Detection:', state.detectionStatus);
    console.log('Counter:', state.counterValue); // Auto-capture countdown
  }

  if (state.status === 'finished') {
    console.log('ID captured successfully!');
    manager.stop();
  }
});

manager.load();

The core factory requires a complete IdCaptureConfig. Resolve it from an active Dashboard Flow containing ID, or supply all required fields. UI components accept partial overrides; core factories do not fill them automatically.

State Machine Flow

flowchart LR
    idle -->|load| chooser
    chooser -->|selectDocument| tutorial
    tutorial -->|nextStep| permissions
    permissions -->|granted| capture
    capture -->|front done| frontFinished
    frontFinished --> capture
    capture -->|back done| processing
    processing --> finished

States Reference

Loading, tutorial, and permission properties

Keep the document and side visible while waiting. permissionsIdle is a silent permission check; avoid flashing a new full-screen loader. Tutorial ready waits for Continue. waitingForPermission and waitingForCamera mean Continue was already requested; show a waiting state. Treat the other loading phases as preparation without exposing implementation details to the user.

Capture State Properties

When status === 'capture':

Mandatory Consent State Properties

When status === 'mandatoryConsent':

RegulationTypes is a string union:

type RegulationTypes =
  | 'US'
  | 'Worldwide'
  | 'Other'
  | 'US_Illinois'
  | 'US_Texas'
  | 'US_California'
  | 'US_Washington';

'Other' is the fallback the SDK uses when the upload response doesn't pin a specific regulation. Drive your consent copy off this value.

Drive the screen with acceptMandatoryConsent() (proceed) or cancelMandatoryConsent() (abort the flow).

Manual Upload State Properties

When status === 'manualUpload'. The user is uploading ID images by file picker — used as a fallback when live capture isn't possible, or when the backend forces it via configuration. The state has tab-aware UI hints (ID vs Passport), per-slot file metadata, and a continue gate.

With onlyBack: true, the manual-upload screen exposes only the ID tab and back-of-ID slot. canContinue becomes true after the back upload succeeds. If manual upload is disabled, onlyBack skips the document chooser and starts camera capture on the back. If manual upload and showDocumentChooserScreen are enabled, the chooser shows only Identity Card and Upload ID.

Drive the screen with manualUploadSelectFile(side, file), manualUploadChangeTab(tab), and manualUploadContinue(). Call manualUploadReset() to clear all selections and start the tab over.

Digital ID Upload State Properties

When status === 'digitalIdUpload'. Reached when the backend allows uploading a digital ID (typically an EU eID or similar government-issued PDF) instead of capturing a physical document. The sub-flow walks the user through a tutorial → file picker → preview → upload → success/failure cycle with a bounded retry budget (3 attempts).

Accepted files. PDF only (application/pdf), 5 MB maximum.

Phase progression. tutorial → selecting (host opens picker on each pickerRequestId change) → reviewing (user confirms or replaces) → uploading → success (auto-advances out of the sub-flow) or error → back to selecting, until attemptsRemaining === 0 → exhausted. fileTooLarge is shown immediately when the user picks an oversized file and does not consume a retry.

Drive the screen with digitalUploadNextStep(), digitalUploadPickFile(file), digitalUploadConfirm(), digitalUploadReplace(), digitalUploadRetry(), digitalUploadChooseAnother(), and digitalUploadScanInstead() (falls back to live capture when allowed).

Digital ID redirect and wallet states

Digital methods must be enabled in Dashboard and supported by the current device. Render options from chooser.availableDocumentTypes; do not offer an unavailable wallet route.

Wallet completion advances the ID manager to finished; identity attributes are retrieved through session results, not the wallet state. On failure, offer retry or another configured method. See the mDL headless example.

Expired-document recovery

expired exposes attemptsRemaining and currentMode. Once attempts are exhausted, render expiredExhausted with a Continue action calling continueExhausted(). The configured journey determines whether the SDK captures another side, completes processing, or finishes this module. Continue does not establish an approved verification; use the session result.

Detection Status Values

API Methods

React Example

import { useState, useEffect, useRef } from 'react';
import {
  createIdCaptureManager,
  type IdCaptureState,
  type IdCaptureConfig,
} from '@incodetech/core/id';

function CustomIdCapture({ config }: { config: IdCaptureConfig }) {
  const videoRef = useRef<HTMLVideoElement>(null);
  const [manager] = useState(() =>
    createIdCaptureManager({
      config,
    }),
  );
  const [state, setState] = useState<IdCaptureState>({ status: 'idle' });

  useEffect(() => {
    const unsubscribe = manager.subscribe(setState);
    manager.load();
    return () => {
      unsubscribe();
      manager.stop();
    };
  }, [manager]);

  useEffect(() => {
    if (state.status === 'capture' && state.stream && videoRef.current) {
      videoRef.current.srcObject = state.stream;
    }
  }, [state]);

  switch (state.status) {
    case 'chooser':
      return (
        <div>
          <button onClick={() => manager.selectDocument('id')}>ID Card</button>
          <button onClick={() => manager.selectDocument('passport')}>
            Passport
          </button>
        </div>
      );

    case 'permissions':
      return (
        <div>
          <p>Camera access is required</p>
          <button onClick={() => manager.requestPermission()}>
            Allow Camera
          </button>
        </div>
      );

    case 'capture':
      return (
        <div>
          <video ref={videoRef} autoPlay playsInline muted />
          <p>Capturing: {state.currentMode} side</p>
          <p>{state.detectionStatus}</p>
          {state.captureStatus === 'detecting' && (
            <p>Auto-capture in: {state.counterValue}s</p>
          )}
          {state.detectionStatus === 'manualCapture' && (
            <button onClick={() => manager.capture()}>Capture</button>
          )}
          {state.captureStatus === 'uploadError' && state.canRetry && (
            <button onClick={() => manager.retryCapture()}>Retry</button>
          )}
        </div>
      );

    case 'finished':
      return <div>✅ ID captured successfully!</div>;

    case 'error':
      return <div>Error: {state.error}</div>;

    default:
      return <div>Loading...</div>;
  }
}

Capture-only flow

createIdCaptureOnlyManager exposes the same state machine and API surface as createIdCaptureManager, but bypasses the Incode upload pipeline. Instead of submitting the captured frames to Incode and waiting on server-side processing, the manager invokes a customer-supplied onCapture(response) callback with the captured images and reaches finished locally. Use this when you want to capture in the browser but upload (or process) the bytes through your own pipeline.

The config contains supported optional capture UX fields plus a required onCapture callback. It is a subset of IdCaptureConfig, not the full Dashboard configuration:

import { setup } from '@incodetech/core';
import { initializeSession } from '@incodetech/core/session';
import {
  createIdCaptureOnlyManager,
  type IdCaptureOnlyConfig,
  type CaptureOnlyResponse,
} from '@incodetech/core/id';

await setup({
  apiURL: 'https://demo-api.incodesmile.com',
  wasm: { pipelines: ['idCapture'] },
});
await initializeSession({ token: 'your-session-token' });

const config: IdCaptureOnlyConfig = {
  showTutorial: true,
  enableId: true,
  enablePassport: false,
  autoCaptureTimeout: 5,
  captureAttempts: 3,
  onCapture: async (response: CaptureOnlyResponse) => {
    // response.frontImage: IdCapturedImageData
    // response.backImage: IdCapturedImageData | undefined
    await uploadToMyBackend(response.frontImage.blob, response.backImage?.blob);
  },
};

const manager = createIdCaptureOnlyManager({ config });
manager.subscribe((state) => {
  if (state.status === 'finished') manager.stop();
});
manager.load();

The CaptureOnlyResponse payload is:

type CaptureOnlyResponse = {
  frontImage: IdCapturedImageData;
  backImage: IdCapturedImageData | undefined;
};

type IdCapturedImageData = {
  imageBase64: string; // Always present — the unprocessed full frame
  blob: Blob; // Same content as Blob
  url: string; // Object-URL for direct rendering
  metadata: string; // Capture metadata (serialized)
  croppedImage?: {
    // Best-effort document crop (see caveat below)
    imageBase64: string;
    blob: Blob;
    url: string;
  };
};

About croppedImage. This is a best-effort approximate crop produced by a bilinear quad mapping — not a true perspective/homography warp. It is populated only when on-device quad detection succeeds, and it will visibly diverge from the correct projective result for strongly tilted captures. Prefer imageBase64 (the unprocessed full frame) when fidelity matters; treat croppedImage as a preview hint.

createIdCaptureOnlyManagerFromActor is also exported for advanced cases where you supply a pre-built XState actor (e.g. to swap services in tests).

Configuration Options

IdCaptureConfig is TutorialIdConfig & { ...extras } — TutorialIdConfig is the Dashboard-driven shape (almost all fields are required), and the extras are advanced overrides.

Orchestrated vs headless: <incode-flow> and createOrchestratedFlowManager supply the complete Dashboard configuration. createIdCaptureManager({ config }) also requires a complete configuration. The standalone <incode-id>.config property accepts partial overrides and resolves remaining Dashboard fields when configuration merging is enabled (the default).

Document selection

Digital ID configuration

Import these types from @incodetech/core/id. A method has required provider and flowType, plus optional method, country, and displayName. Use the Dashboard-resolved configuration for your provisioned methods. See Bank Redirect for return-route wiring.

Capture behavior

Per-country / per-document overrides

Extras (from IdCaptureConfig beyond TutorialIdConfig)

Capture result preview

The built-in <incode-id> component reassures the user mid-capture: partway through the frame-selection window it flashes and freezes the best frame found so far under a "Successfully captured" heading, while the camera and frame analysis keep running. If the user keeps holding the document steady, the frame that actually uploads may be a better one than the one they were shown. Headless integrations skip that preview by default.

To render your own version of it, create the manager with supportsOptimizingStatus: true. captureStatus then reaches optimizing partway through capture, carrying the best-frame-so-far on candidateImageUrl, and leaves it on its own once the frame is committed — at which point previewImageUrl carries the frame that will upload.

Read state.candidateImageUrl ?? state.previewImageUrl, not candidateImageUrl alone: on manual capture (the user taps the button) the preview runs after the frame is committed, so only previewImageUrl is set and a host reading just candidateImageUrl renders nothing. See Headless Mode for the per-path table.

const manager = createIdCaptureManager({
  config: { ...idConfig, supportsOptimizingStatus: true },
});

manager.subscribe((state) => {
  if (state.status === 'capture' && state.captureStatus === 'optimizing') {
    // Covers both paths: automatic capture sets `candidateImageUrl`,
    // manual capture only `previewImageUrl`. On the automatic path the image is
    // display-only — detection is still running and may find a better frame.
    showPreview(state.candidateImageUrl ?? state.previewImageUrl);
  }
});

optimizingDwellMs reports how long the SDK holds the preview. Treat it as a minimum: the SDK runs the dwell on its own timer on both paths, and on automatic capture the state additionally waits for the frame-selection loop to commit a frame, which can take slightly longer. React to captureStatus leaving optimizing rather than assuming an exact duration.

Nothing waits on you: the SDK bounds the state itself, so there is no callback to fire. Your integration should still handle the direct capture-to-upload path, because the preview does not appear on every session. Pass false to opt out explicitly. See Headless Mode for the full walkthrough.

IdCaptureConfig also exposes a few advanced fields reserved for Incode-internal tooling. They aren't part of the public integration surface and aren't documented here.

Error Codes

Examples

Each example shows a config object you can assign to <incode-id>.config (or pass through your framework's property binding). Plug it into the React or vanilla pattern shown in Usage.

ID Card Only

const config: Partial<IdCaptureConfig> = {
  enableId: true,
  enablePassport: false,
  showTutorial: true,
  autoCaptureTimeout: 5,
};

Passport Only

const config: Partial<IdCaptureConfig> = {
  enableId: false,
  enablePassport: true,
  showTutorial: false,
};

See Also

• Headless Mode: Complete headless API reference
• WASM Configuration: Setting up WebAssembly
• Individual Modules: Overview of all modules