Skip to content
On this page

W2 Data EKYC ES 029

About the service

W2 Data EKYC ES 029 is an identity verification service for Spain. W2 will combine several sources of data to make a match. We have a default setup for how we combine sources to make a match, which can be configured if needed. Please contact W2 support for more details.

Product Code: W2-DATA-EKYC-ES-029

Does this service leave a credit search Footprint? Yes


Query Data

The following QueryData elements pertain to this service.

Property NameTypeLengthOptional/MandatoryNotes
GenderStringOptionalMust be 'M' or 'F' if provided
HouseNameString26Mandatory if no HouseNumber givenMinimum address fields are HouseName or Housenumber as well as the postcode. We advise that more address information be sent if possible as this will improve the chances of a match
HouseNumberString26Mandatory if no HouseName given
Phone NumberString16OptionalPlease 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.

Example request

A typical request might look like this:

  "Data": {
  	"City": "Madrid",
  	"DayOfBirth": 27,
  	"Forename": "Mariano",
  	"HouseNumber": "1",
  	"MonthOfBirth": 3,
  	"Postcode": "28071",
  	"Street": "Palace of Moncloa",
  	"Surname": "Rajoy",
  	"YearOfBirth": 1955


The following shows the basic schema for the <W2DataEkyc029Result> object that is returned in the <ServiceResult> Section of the <ProcessRequestResult> object.

Example responses

Single data source example

"w2DataEkycES029Result": {
	"dataSources": [{
			"AllowMultipleRecordsAsSeparateDataSources": false,
			"MatchingCriteria": "NameAndAddress",
			"NumberOfMatches": 1,
			"Source": "Credit"
	"interpretResult": "Pass",
	"Message": "The call was successful",
	"transactionResult": "SuccessIncompleteResults"

Multiple data source exmaple

"w2DataEkycES029Result": {
	"dataSources": [{
			"AllowMultipleRecordsAsSeparateDataSources": false,
			"MatchingCriteria": "NameAndAddress",
			"NumberOfMatches": 1,
			"Source": "Credit"
			"AllowMultipleRecordsAsSeparateDataSources": false,
			"MatchingCriteria": "NameAndAddressAndDateOfBirth",
			"NumberOfMatches": 3,
			"Source": "Goverment"
	"interpretResult": "Pass",
	"Message": "The call was successful",
	"transactionResult": "SuccessIncompleteResults"

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> elment.

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. 8 = Credit

SourceIdSource MatchedNotes
8CreditEstablished credit agencies in the country (Coverage: > 90%; Update Frequency: Daily)
9GovernmentElectoral data, driver's license or history (Coverage: > 90%; Update Frequency: Daily)
10CommercialInsurance Records, Business Directory, Tenancy Information (Coverage:  > 50%; Update Frequency: Quarterly )
11ConsumerPublic Records, Citizen Data sources, marketing and membership data (the AA etc) (Coverage:  > 50%; Update Frequency: Quarterly )
12UtilityData issued for a national utility provider which includes telephone, gas, electricity, or water. (Coverage: > 90%; Update Frequency:  Annually)
14TelecoPublic Number Directory (Coverage: > 75%; Update Frequency:  Annually)

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 occurred, in which case the verification check will be aborted.

Transaction Result

|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
- ClientErrorInsufficientInformationRequired field not supplied or insufficient/invalid information |ServiceInterpretResult|- OneResult
- MultipleResults
- Fail
- NoResults
- NoInterpretPerformed
- NotPerformedAn 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


If the Sandbox query option is set to "true" then any of the following entities will return a result:

Example sandbox request

To use sandbox the following example request can be used.

Remember to include the W2 provided API key in the Authorization Header.

    "Bundle": "KYC_ES_029",
    "Data": {
        "Forename": "Michael",
        "Surname": "Tschank",
        "HouseNumber": "51",
        "Street": "Nobilegasse",
        "Postcode": "1150"
    "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