Skip to main content
The Marketplace lets you connect third-party identity verification providers to your organization and choose, feature by feature, which engine actually runs the check: Didit’s own engine, or a provider you connect yourself.

​
Choosing an engine per feature

Every feature node’s first configuration tab — in both Simple and Advanced workflow mode — starts with a Verification engine control. It shows the engine currently running that check and, next to it, how many providers are available for that feature. Opening the control lists every provider for that feature with an explicit status: Features that only Didit’s own engine supports show that engine with a “no other providers” note and a direct link into the Marketplace, so the control stays consistent across every feature even where there is nothing to switch to.

​
Automatic fallback to Didit

Once you select a connected third-party engine for a feature, a Fall back to Didit if my provider fails switch appears for that feature:
  • On (default): if your provider is unavailable, Didit’s own engine runs automatically for that step, so the verification never fails outright.
  • Off: if your provider is unavailable, the step fails instead of silently running on Didit.

​
Configuring engine selection through the API

Engine selection and fallback are not part of the workflow feature config reference — the Management API accepts them as provider_key and fallback_to_native on the feature’s config object, but they are managed through this Marketplace UI rather than being documented per-feature fields:

Workflows

Build the workflow that each feature’s engine selection applies to.

Workflow feature configs

The full config reference for every workflow feature.