W2DataEkycUk015
About the service
Within the TransUnion service you are able to request either an Identity check or an Anti-Money Laundering check, which will leave the corresponding footprints against the individuals credit file, further information can be found below:
Identity check: Is an identity verification service that includes the Edited Electoral Roll, CCJ and Credit Lenders data. This service will leave a Identification Check footprint on the lenders profile of the person you are requesting information about.
Money Laundering Check: Is an identity verification service that includes the full Electoral Roll, CCJ and Credit Lenders data. This service will leave a money laundering footprint on the lenders profile of the person you are requesting information about.
If no option is selected, the platform will default to the money laundering check.
Product Code: W2-DATA-EKYC-UK-015
Does this service leave a credit search Footprint? Yes
Configuration This service has some configuration that will be discussed with you as part of the on-boarding process. We can configure a matching profile and which sources of information to use when calculating a 2 plus 2 check. Please contact W2 Support for more information.
Request
Query Data
The following Query Data properties pertain to this service. Please note that in the SOAP request the fields must be in alphabetical order.
Property Name | Type | Min Length | Max Length | Optional/Mandatory | Accepted Characters |
---|---|---|---|---|---|
Title | String | 10 | Optional | All apart from (new line ' - \ \\ ,) | |
Forename | String | 1 | 30 | Mandatory | All apart from (new line ' - \ \\ ,) |
MiddleNames | String | 15 | Optional | All apart from (new line ' - \ \\ ,) | |
Surname | String | 1 | 30 | Mandatory | All apart from (new line ' - \ \\ ,) |
DayOfBirth | Integer | 1 | 2 | Mandatory | Numbers Only - greater than 0 |
MonthOfBirth | Integer | 1 | 2 | Mandatory | Numbers Only - greater than 0 |
YearOfBirth | Integer | 1 | 4 | Mandatory | Numbers Only - greater than 0 |
HouseName | String | 1 | 26 | Either HouseName or | |
HouseNumber | String | 1 | 26 | HouseNumber is Mandatory | |
Flat | String | 20 | Optional | ||
Street | String | 40 | Optional | ||
Region | String | 20 | Optional | ||
County | String | 20 | Optional | ||
Country | String | 20 | Optional | ||
City | String | 20 | Optional | ||
Postcode | String | 1 | 8 | Mandatory |
After performing the search, the validation result (pass, fail, etc.) will be part of the <TransactionInformation>
returned for the service call.
Options
This service leaves a Money Laundering Footprint by default, but an Identification Footprint can be specified:
"options": {
"FootprintConfiguration": "MoneyLaundering" | "Identification"
}
Response
Example Response
{
"DataSources": [
{
"Source": 1,
"NumberOfMatches": 1,
"MatchingCriteria": 1,
"AllowMultipleRecordsAsSeparateDataSources": "false"
},
{
"Source": 7,
"NumberOfMatches": 1,
"MatchingCriteria": 1,
"AllowMultipleRecordsAsSeparateDataSources": "true"
}
],
"InterpretResult" : "Pass",
"TransactionResult": "Success"
}
Response Breakdown
Below is some more information about the 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.
Example Response: The below example shows a case where we have found one NameAndAddress match on the Electoral roll and 3 NameAndAddressAndDateOfBirth matches on CreditLendersB. This has resulted in a Pass.
Transaction Result
Property | 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 |
ServiceInterpretResult | - OneResult - MultipleResults - Fail - NoResults - NoInterpretPerformed - NotPerformed - An error occurred and the search was not performed |
ServiceTransactionResultMessage | Usually empty, can contain optional information such as too many matches etc. |
ValidationResult | - Pass - NotPerformed - No search occurred to match against - Fail - MissingMandatoryField or PatternNotMatched |
Sandbox
Sandbox mode can be used to test the service.
By setting the following query option and sending some the below query data we will return a pre-configured response without actually calling our suppliers.
Example Request
{
"Bundle": "KYC_UK_015",
"Data": {
"Forename": "Amber",
"Surname": "Ball",
"DayOfBirth": 9,
"MonthOfBirth": 7,
"YearOfBirth": 1957,
"HouseNumber": "147",
"Street": "Ocean View",
"Postcode": "WT1 1TD"
},
"Options": {
"Sandbox": "true"
},
"ClientReference": "your-client-reference"
}
Sandbox cases
These are the sandbox options for these service. Learn about our Sandbox here
Click on a sandbox case to view the request and response