Skip to main content

Integration profile

Sumsub Identity

AutoKYC orchestrates Sumsub for capture, document, and biometric verification while layering the rules engine and voting controls to document every decision. Analysts see Sumsub evidence alongside dual AML results and audit logs without leaving the platform.

SaaS + Managed Services Coverage: 220+ countries and territories Data residency: EU, US, Singapore
Discuss integration rollout View developer documentation

Why teams pair with Sumsub Identity

  • Dual-provider fallback using AutoKYC routing to keep capture SLAs even during vendor downtime.
  • Biometric capture inherits consent gating and privacy-by-design defaults from AutoKYC SDKs.
  • Case timelines record liveness outcomes, analyst votes, and Sumsub callbacks for regulator-ready evidence.

Use cases

High conversion identity checks

Use Sumsub as the primary document and liveness provider for retail onboarding. The rules engine applies tiered fallbacks and escalates mismatches to analysts with a full audit trail.

Regulated market fallback

Automatically switch to Sumsub capture nodes that meet EU, US, or APAC residency requirements when jurisdiction tags demand in-region processing.

Managed analyst adjudication

AutoKYC Managed Services resolve Sumsub alerts inside the same case, with voting, escalation, and QA scoring linked back to your policy owners.

Setup steps

  1. 1

    Provision Sumsub API credentials

    Create limited-scope API keys in Sumsub, rotate them via AutoKYC secrets management, and avoid embedding credentials in client applications.

  2. 2

    Map provider queues

    Add Sumsub as an identity provider inside AutoKYC, tag it to onboarding flows, and define fallback routing alongside secondary AML networks.

  3. 3

    Sync result schemas

    Use AutoKYC schema mapping to normalise Sumsub response fields for downstream systems and audit exports.

Implementation notes

  • Supports REST callbacks and webhook retries; GraphQL exposure available through the AutoKYC unified API.
  • Enable privacy retention controls per jurisdiction before directing live traffic.

Operational considerations

  • Sumsub does not provide sanctions screening; pair with a dedicated AML provider connector.
  • Default video retention is 30 days; extend via AutoKYC archival policies when regulators require longer evidence windows.
  • Throughput throttles at 50 requests per second without prior approval from Sumsub support.