Capabilities & Features

What you can orchestrate, observe, and decide with the IDnow's Trust Platform

The Trust Platform is organized around three capabilities needed to Trust-Your-Customer:

• Orchestration enables all of our Trust-Your-Customer services to work seamlessly together, allowing you to build, adapt, and combine multiple services into a single configurable flow.
• Observe enables you to understand how flows perform in terms of completion rates & speed, conversion rates, drop-off rates.
• Decide enables you to constantly mitigate your risk, by configuring rules & thresholds in Protect and other fraud-signal-related steps, automating your risk-minimising business-decision making process.

Orchestration

Build and operate flows through their full lifecycle — from initial design to live deployment.

Flow Editing & testing

The visual flow editor lets you compose flows from steps, configure each step's options and wire routes between steps. You can launch a test session directly from the editor to validate your flow against the Player before publishing.

The nifty Validator in the sidepanel will highlight opportunities for improvements and display warnings for misconfigurations. You'll also be able to download the OpenAPI specs for the flow.

Flow Versioning & environments

Flows are versioned. Every change creates a new draft version that can be reviewed and tested before being published. Versions can be published independently to staging and live — only one version is active per logical environment at a time - but the same version can be in both environments!.

Example: Let's say you have created a flow called "KYC: enduser onboarding", and let's say you have v2 in staging and v5 in live.

• When using live as the {environment}-parameter for API calls, you will be interacting with v5 of the flow.
• When using staging as the {environment}-parameter for API calls, you will be interacting with v2 of the flow.

warning

Deploying a new version replaces the current one without deleting the old deployment history.

Flow Configurations

Within the editor, you can also find additional configuations & settings that apply to just the respective flow's version:

Sessions lifetime	Languages & translations
Each flow version carries a configurable session timeout — the maximum duration a session can remain in progress before it expires. The default is 24 hours. The timeout is set per version inside the editor and is aligned with the SDK token lifetime for the Player.	The Translation manager lets you replace the default text for any customisable text element in a flow version. Translations are managed per flow version and cover only the flow languages configured for that version. Changes are stored on the flow version and applied to end users at runtime.

Flow settings

Flow Settings lets you update the flow's name, description and configure webhooks for each environment.

You can subscribe to specific webhook events and optionally include custom HTTP headers for extra security. Deliveries are retried on failure and carry a signed JWT for verification. Each event includes an eventSequence field for ordered processing on the consumer side.

---

Observe

Understand how your flows are performing, quickly being able to identify opportunities for optimising for completion rate & speed, conversion rate, etc.

Flow Analytics

The Overview tab of a flow surfaces session-level metrics for the selected environment and time window:

• Status distribution — breakdown of sessions by outcome status (completed, running, expired, aborted, error)
• Running now — live count of active sessions
• Conversion history — accepted and rejected session counts over time
• Per-step breakdown — verdict distribution for each step in the flow

Metrics can be filtered by environment and scoped to specific deployed versions.

Flow Funnel

The Funnel tab overlays session volume directly onto the flow graph. Each step shows how many sessions passed through it and what fraction continued onward, making drop-off points immediately visible. The funnel can be filtered by environment and date range.

---

Decide

Based on your flow orchestration - and the enablement of Protect - sessions automatically result your designated business-outcome, so you can immediately decide if you can Trust-Your-Customer.

Sessions details

Each session has a detail page showing:

• Session result — the final outcome with the verified identity, document capture, and portrait where available
• User journey — a step-by-step timeline of what happened during the session, including routing-decisions at each step
• Device signals — fingerprinting and device intelligence signals collected during the session
• Protect checks — any fraud rules triggered during the session, with their severity level
• Data blocks — the full structured output produced by the flow

Protect rules & threshold

tip

This feature is not yet available to all customers. Please reach out to your Account Manager to find out more

Additionally to the routing from step to step, you can configure fraud signal rules at the organization level to control how the platform responds when a signal is detected during a session.

Each rule in the catalogue can be set to one of three severity levels:

Severity	Behavior
off	Rule is disabled; signal is not evaluated
warning	Signal is flagged and visible in session detail
block	Session is blocked when the signal fires

Rule names and descriptions are provided by the Protect service. Changes apply immediately to new sessions; in-progress sessions are not affected.