Identity verification service with Electoral Roll and Credit Bureau data.
Compatible Cases
About this service
W2 Data Ekyc UK 005 is an identity verification service that includes the full Electoral Roll and Credit Bureau data. This service will leave a money laundering footprint on the bureau profile of the person you are requesting information about.
Product Code: W2-DATA-EKYC-UK-005
Does this service leave a credit search Footprint? Yes
Request
The following QueryData properties pertain to this service. Please note in the actual SOAP request the fields should be in alphabetical order.
Property | Type | Length | Optional/Mandatory | Notes |
---|---|---|---|---|
Forename | String | 15 | Mandatory | |
MiddleNames | String | 15 | Optional | The contents of this field will be converted into initials, therefore the character limit can usually be ignored. |
Surname | String | 30 | Mandatory | |
DayOfBirth | Integer | 2 | Mandatory | |
MonthOfBirth | Integer | 2 | Mandatory | |
YearOfBirth | Integer | 4 | Mandatory | |
HouseName | String | 26 | Optional | Either house name or house number must be supplied |
HouseNumber | String | 10 | Optional | Either house name or house number must be supplied |
Flat | String | 16 | Optional | |
Street | String | 40 | Optional | |
County | String | 20 | Optional | |
City | String | 20 | Optional | |
Postcode | String | 8 | Mandatory | |
PhoneNumber | String | 16 | Optional | Please provide the phone number as one contiguous set of numbers with no other characters or spaces. |
After performing the search, the validation result (pass, fail, etc.) will be part of the TransactionInformation
returned for the service call.
Notes
- Address information is optional if an AddressLookupRef is supplied in the query options. The AddressLookupRef is retrieved from the W2 Data Address Lookup 024 service as an addressId.
- If an AddressLookupRef is not supplied then a minimum of House Name/Number and Postcode are required. Though it is advised to supply as much address information as possible as this is more likely to return a match if no prematched addressId is supplied.
Example Request
{
"Bundle": "YOURBUNDLE",
"Data": {
"DayOfBirth": 22,
"Forename": "Isabelle",
"MonthOfBirth": 10,
"Surname": "Davidson",
"YearOfBirth": 1997
},
"Options":{
"AddressLookupRef":"12345"
}
}
Response
Example response
"w2DataEkycUk007BResult": {
"dataSources": [{
"AllowMultipleRecordsAsSeparateDataSources": false,
"MatchingCriteria": "NameAndAddressAndDateOfBirth",
"NumberOfMatches": 2,
"Source": "CreditLendersB"
}
],
"interpretResult": "Pass",
"Message": "The call was successful",
"transactionResult": "SuccessIncompleteResults"
}
Response breakdown
The following shows the basic schema for the W2DataEkycUk007BResult
result.
Below is some more information about some of the elements of the response that require explanation:
DataSources = A collection showing every source of data that was used to formulate the result. Each source is represented by a MatchingSource
element.
AllowMultipleRecordsAsSeparateDataSources = Indicates that two different record matches from the same data source may count as independent sources when formulating the 2 + 2 result. For example, two Insight results may count as two sources, rather than one, as they would do under normal service circumstances.
MatchingCriteria = Precisely what data has been matched by the data source. E.g. NameAndAddressAndDateOfBirth
NumberOfMatches = The number of matches found by this data source
Source = An integer representing the source of the data match. E.g. 2 = CCJ (County Court Judgement)
SourceId | Source Matched |
---|---|
1 | Electoral Roll |
2 | County Court Judgements (CCJs) |
3 | N/A |
4 | Credit Lenders (Insight) |
5 | BT_OSIS |
6 | Mortality Data |
7 | Credit Lenders (Call Credit) |
InterpretResult = The overall verification result, based on what matches were found in the data source against the query data submitted. The possibilities are Pass, Fail or Refer
Message = Gives some more details / context on the verification result
TransactionResult = A diagnostic result showing whether or not any technical errors were experienced during the check. This should always be "Success" unless a technical error has occured, in which case the verification check will be aborted.
Transaction Result
Property Name | Value |
---|---|
HaltTriggered | False |
ServiceTransactionResult | - Success - SuccessIncompleteResults - Too many matches on the search criteria and the results have been truncated - SuccessNoResults - No matches found - ServerErrorGeneralError - An error occurred - ServiceFailureError - Unable to contact third party service - ClientErrorInsufficientInformation - Required field not supplied or insufficient/invalid information - ClientErrorInformationFormatInvalid - Address fields cannot contain commas |
ServiceInterpretResult | - NotPerformed - An error occurred and the search was not performed - Pass - Fail - Inconclusive - NotApplicable - Validation has failed, please check ValidationResult for further details. |