Apply document liveness and selfie best practices for IDV integrations

domain: developer.apple.com/design/human-interface-guidelines/identity-verification · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Use a vendor-provided native SDK (iOS, Android, or web) for document capture rather than a generic camera API; IDV SDKs include autocapture, blur detection, glare detection, and real-time guidance that significantly reduce capture failure rates.
  2. For document capture, guide the user to capture both front and back of ID documents on a dark contrasting background, with instructions to remove any case or sleeve; validate the captured image server-side for ICAO 9303 compliance where applicable.
  3. For selfie liveness, prefer active liveness (challenge-response, e.g., head turn or blinking prompts) over passive liveness for higher assurance; confirm your IDV vendor's liveness level meets the assurance requirements of your jurisdiction or program.
  4. Perform a facial similarity comparison between the selfie and the document portrait server-side using your IDV vendor's matching endpoint; do not rely on client-side comparison.
  5. Set minimum image quality thresholds (resolution, brightness, sharpness) and return actionable error messages to users when captures fail, rather than silently submitting poor-quality images.
  6. Regularly review your IDV vendor's presentation attack detection (PAD) and injection attack mitigation capabilities and update SDK versions promptly when security patches are released.

Known gotchas

Related routes

Configure and tune the selfie-to-document face match threshold in an IDV pipeline
identity-general · 6 steps · unrated
Integrate AU10TIX for document authentication and selfie liveness verification
identity-general · 6 steps · unrated
Implement passive liveness detection compliant with ISO 30107-3 PAD Level 1 using a single-frame selfie capture
iso.org · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans