Automatic Document verification (DVFC 047)

---

Introduction

W2 DVFC 047 is a digitized and AML-compliant (Anti-money laundering) method of automated identity verification that uses AI technology to reliably identify users.

This service can be used via API only.

This service will not leave a credit search footprint.

For technical details regarding integration, please check our Developer Documentation by following this link:

DVFC 047 Dev Docs

---

Process

DVFC offers a simple process to reliably identify users.

1. Create a session. This will include submitting basic textual data of the user you are attempting to identify, which will generate a session url.
2. the user needs to submit physical documents. (i.e. Passport, Id, etc.).
3. The user will have to proceed to a Liveness Check prompted by the service.
4. Information is processed.
5. Result is returned via our webhook and stored in the results section on the case.

---

Request

The following properties pertain for creation of an session.

Property Name	Type	Optional/Mandatory
CaseId	String	Mandatory*
City	String	Optional
ClientReference	String	Mandatory*
ConfCode	String	Optional*
Firstname	String	Optional
Lastname	String	Optional
Country	String	Optional
Postcode	String	Optional
Email	String	Optional
Gender	String	Optional
DayOfBirth	String	Optional*
MobilePhone	String	Optional
MonthOfBirth	Integer	Optional*
YearOfBirth	Integer	Optional*
PreferredLang	String	Optional

DayOfBirth, MonthOfBirth and YearOfBirth are optional parameters, but if a date is provided then all three fields must be populated, (i.e. 08/2025 - Not Accepted, 12/08/2025 - Accepted).

CaseId or ClientReference must be provided to use this endpoint. If a CaseId is not provided then a case will automatically be created upon the creation of a session, but a ClientReference must be provided. If a CaseId is provided then your session information will be created and linked to your existing Case.

ConfCode is optional however a default configuration will be used when no ConfCode is provided. Please consult about the use of this during onboarding.

---

Custom Configurations

The following customizations are available when creating a DVFC 047 session:

Property Name	Type	Optional/Mandatory
ConfigName	String	Mandatory
DocumentsToCapture	List of DocsToCapture	Mandatory

Each DocsToCapture is a seperate document definition and can contain multiple accepted documents or verification types. DocsToCapture has the following properties:

Property Name	Type	Optional/Mandatory	Description
Code	String	Mandatory	Code to associate with the captured document when returning the result. E.g. OWNER_ID
DocTypes	List of String	Mandatory	List of the documents expected from this document definition. - ID national identity card - P passport - V visa - DL driving license - HC health card - RP resident permit - SELFIE picture of user - LIVENESS Liveness detection - CAR_REG car registration - KBIS company registration (not analysed) - RIB bank account identity (not analysed) - ADR_PROOF residence certificate (not analysed) - PAY_SHEET remuneration statement (not analysed) - TAX_SHEET tax bill (not analysed) - OTHER other type of document (not analysed)
Optional	Boolean	Optional	Flag indicating that the document capture is optional, SELFIE and LIVENESS documents can not be optional. Default: false
VersoHandling	String	Optional	Indicate how to handle verso of the document. - DEFAULT trust the algorithm on verso handling (No verso requested if the document is not analysed). - MANDATORY always ask for a verso, user is not allowed to skip its capture (Useful for documents that are not analysed). - OPTIONAL always ask for a verso, but user is allowed to skip its capture (Useful for documents that are not analysed).
Description	String	Optional	Description of the document, to display in the web page used to capture the document ⇒ If null, the default value will be used. WARNING, mandatory for document of type OTHER E.g.: Please, take a picture of the trunk owner national identity card.
Label	String	Optional	Title of the page used to capture the document. ⇒ If null, the default value will be used. WARNING, mandatory for document of type OTHER Example: Car owner ID card

Notes

The CustomerIdentificationUrl provided upon successful creation of a session has an expiry time of 24 hours. The session is needed only for the submission of information, so once the information is submitted for identification, it is no longer required and the result of the identification can be monitored from the Case to which it's attached.

However, if you have not started or completed the submission of information and your session expires you simply need to call the create endpoint with the existing case id (whether it was created as part of the original submission or whether it is an existing Case which you provided), and a new CustomerIdentificationUrl will be supplied.

---

Response

Our DVFC Alert Webhooks have been created to trigger a webhook whenever an Alert is generated from our verification system. This will enable you to utilise any downstream automation like updates to ongoing verification checks.

Our Webhooks are an important new feature of our Document Verification & Facial Recognition, in order to make use of them you will need to ensure:

1. You are using our DVFC 047 system.
2. You have informed us of the callback URL you are listening on.

To establish either of these you can reach out to our Support team who can help you get started.

There are multiple response types depending on your requirements.

The response types can be found in our Developer Documentation by following this link:

DVFC Webhook Response