W2 DVFC 047
About the service
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.
DVFC offers a simple process to reliably identify users.
- Create a session. (This will include submitting basic textual data of the user you are attempting to identify, which will generate a session url)
- Submitting physical documents. (i.e. Passport, Id, etc.)
- Information is processed.
- Result is returned via our webhook. Click Here to view potential responses returned.
Product Code: W2_DVFC_047
Does this service leave a credit search Footprint? No
Create
The section below describes how to create a session.
How to use
To call the endpoint you will need to perform a HTTP POST request to the URL:
API Version | Url |
---|---|
1.5 | https://api.w2globaldata.com/identification?api-version=1.5 Latest |
Request
The following properties pertain for creation of an session.
Property Name | Type | Optional/Mandatory |
---|---|---|
Birthplace | String | Optional |
CaseId | String | Optional |
City | String | Optional |
ClientReference | String | Optional |
CompanyId | Integer | Mandatory |
Country | String | Optional |
Custom2 | String | Optional |
Custom3 | String | Optional |
Custom4 | String | Optional |
Custom5 | String | Optional |
DayOfBirth | String | Optional* |
String | Optional | |
Firstname | String | Optional |
Gender | String | Optional |
Lastname | String | Optional |
MobilePhone | String | Optional |
MonthOfBirth | Integer | Optional* |
Nationality | String | Optional |
Postcode | String | Optional |
PreferredLang | String | Optional |
YearOfBirth | Integer | Optional* |
Notes
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 is an optional parameter with the use of this endpoint. If a CaseId is not provided then a case will automatically be created upon the creation of a session. If a CaseId is provided then your session information will be created and linked to your existing Case.
Example Request
{
"dayOfBirth": 23,
"monthOfBirth": 5,
"yearOfBirth": 1987,
"birthplace":"London",
"custom1": "999000999",
"custom2": "Eg. Job Position ",
"custom3": "Eg. Insurance number",
"custom4":"or store any data strings",
"custom5":"you like.",
"email":"[email protected]",
"firstname":"Erika",
"gender":"FEMALE",
"lastname":"Musterman",
"mobilephone":"+441763109660",
"nationality":"GB",
"zipcode":"W1U",
"preferredLang":"en",
"clientReference": "o199i-2idjjj3x",
"companyId": 1,
"caseId": "581ebe6d-9b1b-4b92-a057-e4d5cbb34012"
}
Example Response
{
"CustomerIdentificationUrl": "https://{example_url}/session/{sessionId}",
"CaseId": "581ebe6d-9b1b-4b92-a057-e4d5cbb34012"
}
Notes
The CustomerIdentificationUrl provided upon successful creation of a session has an expiry time of 1 day. 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 submition 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.