Overview
A workflow defines the checks a user must complete: a biometric face scan, scanning an identity document, and any other steps your account is configured for. You set up workflows in the pawaPass backoffice, and every verification runs one. You do not send the list of checks on each request. When you create a verification, pawaPass resolves the workflow to run, and the workflow decides the checks. You choose the workflow in one of two ways:- By country (default). Omit
workflowIdand pawaPass runs the default workflow configured for the verification’scountry. You set the per-country defaults under verification markets in backoffice. - By ID. Pass a
workflowIdto run a specific workflow. This is the 8-character workflow shortId shown in backoffice.
workflowId is returned on the verification and on every webhook, so you can tell which workflow ran. It can be null in some cases (see Reading the workflow back).
Checks a workflow can include
Face scan
Face scan
The user completes a biometric face scan with liveness detection. When the workflow also includes a document scan, the live face is compared against the document photo.
Document scan
Document scan
The user scans an identity document (passport, national ID, driver license, voter card, refugee card, or residence permit). The extracted data is returned in the
identityDocument field once the verification is approved.Selecting a workflow
- By country default
- By workflow ID
Omit
workflowId. pawaPass runs the default workflow configured for the country, so most integrations never send a workflow at all.Reading the workflow back
The verification response and every webhook include the resolvedworkflowId:
workflowId is the id of the workflow that ran the verification, when it is known. It can be null in two situations:
- Before it is pinned. A verification created with neither
workflowIdnorrequirementsruns on the country default and is pinned when it starts, soworkflowIdisnullwhile it is stillCREATED(unstarted) and fills in fromSTARTEDonward. SendingworkflowIdorrequirementson create pins it right away. - On older verifications. Records that predate pawaPass storing
workflowId, or predate workflows entirely, reportnullwhatever their status.
workflowId is null, read the requirements array on the response to see the checks the verification runs. Before the verification is pinned, the array can still change when it starts, if the country default was reassigned since create. Read it from STARTED onward for the checks that run.
Older integrations set the checks by sending a
requirements array on create. That still works, but a workflow runs either way: the resolved workflow decides the checks, and the array no longer overrides it. Sending it is no longer the recommended way to configure checks. See Verification requirements.