Supported Digital IDs

Use Incode's Digital IDs capability to accept and verify government-issued digital identity credentials in any Incode flow. Digital IDs include mobile driver's licenses (mDLs), national eIDs, and government ID apps.

The integration model

Incode integrates digital IDs into multiple verification flows. When you configure a Workflow, you can choose to offer digital IDs the same way you offer physical document capture. The user journey adapts to what's available on the user's device.

Digital IDs do not replace the rest of Incode's identity stack; they feed into it. Each digital ID session can still run liveness, deepfake detection, TrustGraph signal lookup, and risk scoring.

Configuration

Choose the integration path that matches your implementation.

1. Incode Dashboard (Web Flows & Workflows)

1. Ask your Incode Representative to enable the Digital IDs feature for your organization.
2. In each Workflow, open configuration for the ID Capture module. Use the settings under Digital ID to enable specific methods. You can turn on Enable Device Wallet verification, Enable Digital ID upload, or both.
3. Run users through that workflow to make the enabled methods available.

No code changes are required.

2. SDK (mobile, web)

1. Ask your Incode Representative to enable the Digital IDs feature for your organization.
2. Specify which methods to offer with verificationOptions.methods.
3. Let the SDK detect device capability and filter methods at runtime.

3. Server API

1. Ask your Incode Representative to enable the Digital IDs feature for your organization.
2. Use the direct API endpoints for session creation and credential exchange.

Observability

Every digital ID session logs:

• The method presented
• The verification outcome, including success or fail reason
• Whether a fallback was triggered (for example, credential missing → physical document capture)
• The flow ID, session ID, and device metadata

These fields are available in session results and downstream analytics. See the per-type pages for specific failure reason codes.

Common integration notes

• Device capability detection. The SDK checks entitlements and wallet contents before offering a method, so users do not reach a dead end on unsupported devices.
• Chrome on iOS. Digital IDs are not supported because of an Apple restriction. The SDK hides the option.
• Desktop. Not all credential types are available on desktop. See the per-type pages for details.
• Selective disclosure. Incode requests only the attributes required by your flow configuration. You control the minimum data set.

Provider registration

Certain credential types require you to register as a relying party with the scheme operator. Incode Support guides you through this process and, where applicable, completes the registration on your behalf.