This section explains the concepts and architecture behind every Incode integration: how the platform is structured, how it secures data and requests, the difference between onboarding and authentication, how sessions are scored, and how Workflows and Flows control the verification experience.
Read this section to understand how the platform works before moving on to implementation guides for a specific integration type.
Platform Architecture
- Platform Architecture Deep Dive: How the Incode Platform is structured across three layers (Applications, Platform APIs, Third-Party Verification Services), the SaaS infrastructure requests pass through (WAF, API Gateway, microservices, Data Warehouse), and the credential model (API key, session token, admin token) that secures every call.
- Security Model Overview: The architectural security decisions behind the platform: credential boundaries, encryption in transit, capture-only mode, webhook security, and compliance posture.
Verification Concepts
- Onboarding or Authentication: The two verification journeys the platform supports: onboarding (verifying a new user for the first time) and authentication (confirming a returning user via Face Authentication), and how they relate.
- Scoring System Explained: How module-level and overall session scores are calculated, the
ok/warn/manual/fail/unknownstatus model, and how scores map to approve, manual-review, and deny decisions. - User Consent for PII Data: The Privacy Consent and Machine Learning Consent types Incode requires, and how to collect them via Dashboard or API.
Authentication Protocols (OIDC)
- OIDC Automatic Configuration: How OAuth 2.0 and OpenID Connect work together in Incode integrations, and the two ways to configure OIDC: automatic (tied to a Flow or Workflow) or manual.
- OIDC Manual Configuration: Step-by-step instructions for creating and managing an OIDC client directly in Dashboard when you need control beyond the automatic model.
Workflow Configuration
- Flows and Workflows: The difference between the legacy Flows model and the recommended Workflows model, and the node types (Module, Process, Condition, Result) used to build a Workflow.
- Conditions for Workflows: How Condition nodes branch a user journey based on collected data, with common examples like pass/fail logic and manual review triggers.