Skip to main content

Prerequisites

  • A pawaPass partner account
  • An API key (create one in the Backoffice)
1

Create a verification

Make a POST request to create a verification session. You do not list the checks: the default workflow for the country decides them. This example assumes a workflow with a face scan and a document scan.
The response includes a url field. Redirect the user there:
Verifications are deduplicated by externalId. When you create a verification, pawaPass checks for an existing active verification with the same externalId:
  • No active verification exists: a new verification is created and the response status is 201 Created.
  • An active verification already exists: the existing verification is returned unchanged and the response status is 200 OK. A new verification is not created.
A verification is considered active until it reaches a final status (APPROVED, DECLINED, or EXPIRED). Once the previous verification is in a final status, creating a verification with the same externalId starts a fresh one (201 Created). If short links are enabled, the new verification reuses the same url as the previous one, so the link you shared earlier keeps pointing to the latest verification.
2

Redirect the user

Send the user to the url from the response. They will complete the face scan and document scan in the pawaPass verification flow.After completion, the user is redirected to your successUrl or errorUrl.
Want to keep the user on your site? Use the Web SDK to embed the verification flow directly in your app.
3

Check the result

Fetch the verification to see the status and extracted document data:
When the status is APPROVED, the identityDocument field contains the extracted data:

Next steps