Identity Verification Integration
Integration Guides
Web SDK guide
This guide provides step-by-step instructions on how to integrate the European Identity Verification solution with the Web SDK.
Before you begin, make sure you have completed the following:
Flow
Click to magnify.
1. Authenticate
Create an access token to authenticate in our API:
- You provide your Fourthline API credentials.
- You receive an
access_token.
Tutorial: Create access tokenAPI Reference: Create access token
Important
For security, access tokens are valid for 1 hour only.
If your token expires, create a new one by making another Create access token request.
2. Create workflow
Create a European Identity Verification workflow:
- You specify the
workflowNameand provide your unique identifier for the client. - You receive a
workflowIdand a FourthlineclientId.
Tutorial: Create workflowAPI Reference: Create workflow
Status: The Identity Verification case status changes to
new.
Upload identity data
If configured, upload relevant identity data:
- You provide the
verificationIdand relevant data points. - A successful response is empty.
Tutorial: Upload identity dataAPI Reference: Upload identity data
3. Create SDK session
Create the Web SDK session:
- You provide the
workflowId. - You receive an 8-digit, alphanumerical
validationCodeto pass to the SDK in your backend.
If the client starts on your website in their:
- Desktop browser: Initialize the Web SDK, display the redirect options, and redirect the client to the workflow in their mobile browser.
- Mobile browser: Display the redirect options and then redirect them to the workflow on your subdomain.
Tutorial: Create Web SDK sessionAPI Reference: Create SDK session
Important
- SDK validation codes are single-use and expire after 2 hours.
- If the client stops partway through the workflow, create a new SDK session.
- When the client closes the browser, the
validationCodeis invalidated and removed from the cache.
Status: The case status changes to one of the following and we send the relevant webhook notification:
| Status | Description | Action |
|---|---|---|
pending | The data is valid. | Wait for the next status. |
invalid_data | Invalid or missing data. | Create a new workflow. |
Status: The case status then changes to one of the following and we send a webhook notification:
| Status | Description | Action |
|---|---|---|
inconsistent_data | We found inconsistent data. | Create a new workflow. |
completed | We have processed the case. For our recommendation to accept or reject the client, see the risk code. | Download the CDD Report. |
Check case status
When you receive webhook notifications, we recommend also requesting the full case details:
- You provide the
verificationId(same value as theworkflowId). - You receive all the data on the case.
Tutorial: Get case statusAPI Reference: Get case status
4. Download CDD Report
When the case status is completed, download the CDD Report zipfile:
- You provide the
workflowId. - A successful response is empty and the report is downloaded.
API Reference: Get CDD zipfile
Updated 3 months ago