flow_id selects which eKYC journey runs for a given session — passed as a query/body parameter to Authentication, the Platform API, or the Vision Score API. Built-in flows are provisioned out of the box; flexible/custom flows are provisioned per client by TrustVision — contact TrustVision to receive your custom flow_id before integrating.
| flow_id | Description |
|---|---|
id_selfie | Built-in flow: ID → Selfie → Matching. |
selfie_id | Built-in flow: Selfie → ID → Matching. |
id_nfc_selfie | Built-in flow: ID capture → NFC chip read → Selfie → Matching. |
qr_nfc_selfie | Built-in flow: QR code scan → NFC chip read → Selfie → Matching. |
id_form_selfie | Built-in flow: ID capture → user-filled form → Selfie → Matching. |
vision_score_sanity_liveness | Called via the Vision Score API. Runs Vision Score with passive liveness: 1–3 selfie images, selfie_type: "passive", with optional liveness video frames. |
vision_score_only | Called via the Vision Score API. Runs Vision Score against a single selfie image, with no liveness check. This is also the default flow_id when none is supplied to Vision Score. |
Two additional non-built-in flow_id values are documented for the Flexible ID & Selfie Capturing integration mode (separate ID/Selfie steps rather than a pre-built journey):
| flow_id | Description |
|---|---|
id | ID capturing only. |
selfie | Selfie capturing only. |
...and more — any custom flow provisioned by TrustVision follows the same flow_id mechanism.