Skip to main content

Overview

This guide explains how to collect a full verification (selfie + identity document) along with an additional identity document (e.g., residence permit) using the iDenfy API and web redirect. Common use case: Non-resident verification requiring both a primary ID document and a residence permit.

Choosing a Method

Recommendation: Use Method 1 if you need automatic data extraction and comparison between documents.

Method 1: Two Separate Sessions

Generate two sessions with the same clientId, chain them using redirect URLs, and compare the webhook results.

Step 1: Generate Both Sessions

Create the identity verification session first. Set its redirect URLs to point to the second session’s redirect URL.
Then create the document verification session:
Use the authToken from the document session response as DOCUMENT_TOKEN in the identity session’s redirect URLs. This chains the two sessions so the user is automatically redirected after completing the first verification.

Step 2: Send the User to Verification

Step 3: Handle Webhooks and Compare Data

You will receive two separate webhooks β€” one for each session. Use the clientId to link them and compare extracted data.
Suggested fields to compare: first name, last name, date of birth.

User Journey

  1. User clicks verification link
  2. Opens identity verification (selfie + ID)
  3. Completes identity verification
  4. Automatically redirected to document verification (residence permit)
  5. Uploads additional document
  6. Redirected to your success URL
  7. Two webhooks received β€” compare data to validate the same person

Method 2: Additional Steps

Use this when you do not need data extraction from the additional document.

Setup

Contact iDenfy support to configure an additional step in your environment (e.g., RESIDENCE_PERMIT).

Generate Session

The additional step is included automatically from your environment configuration.

Webhook Result

The additional document is stored only β€” no automatic data extraction. You will need to manually review or process the document image from fileUrls.