W2Global Data eKYC – List of APIs to be used

Services Included in the journey

W2 ServiceDescriptionResponse
Email check (WS010)Contis will use the email address, provided by the applicant, to check for fraudulent activity linked to the email address providedIf the email address appears in any list or data-base the application will be declined at decision point 1
Address look-up and formatter (WS024)Contis will use the postcode provided by the applicant to return a list of addresses to the applicant. The applicant will select their address from those returned.All addresses linked to the postcode will be returned, user will select from the list provided and this will be returned to Contis (New API development). Address will be formatted in a standard way
KYC_Contis UKA bundle of checks containing a PEP check (WS003), a Sanctions check (WS001) and a voters roll check (WS007b) with one API call.Contis will use data provided during the application to make the call. W2 will return responses to Contis. Contis will store the responses in COMS
KYC_Contis_RoWA bundle of checks containing a PEP check (WS003), a Sanctions check (WS001) and a global multisource check (WS43) with one API call.Contis will use data provided during the application to make the call. W2 will return responses to Contis. Contis will store the responses in COMS
Document UploadHosted – Contis will integrate W2 SDK into Canvas
API – Client will integrate the W2 SDK within their App and, using the journey screens provided by Contis, the applicant will take an image of their document and a selfie (liveness check) and will upload it to Contis
Contis will store an image of the document for audit and compliance purposes
Document Verification (WS039)Contis will send the uploaded document image to W2 who will complete the document verification processW2 will notify Contis on whether the document provided has passed the verification process. Contis will use the response in its decision-making process along with results of the other checks
Facial Comparison (039)Contis will send the uploaded document image to W2 who will complete a facial comparison between the selfie and the image on the documentW2 will notify Contis on the % match of the facial comparison. Contis will set a % match on what will be accepted as a ‘pass’.

List of Contis methods to perform eKYC & DVFC with W2Global Data

Dev portal controllerWeb method nameDescription
ContisAddConsumerUpdate, internal logic change. Perform eKYC with W2Gbolal as Service Provider configured against program.
DVFCProcessW2Global as Service Provider configured against program and KYC status as “Refer” from Consumer/AddConsumer API. DVFCProcess method is used to upload documents to process Document Verification and Facial Comparison to perform further KYC. DVFC process can perform only one time per user.

During the application process, Contis will use the information provided by the applicant to call the W2 APIs.

When calling the WS024 service, Contis will return the list of addresses back to the client. The client will display the list back to the applicant, the applicant will select one of the returned addresses or be able to enter a different address to those returned.

For the UK journey, not all applications will require documents to be uploaded or selfies to be submitted. If the applicant, successfully passes the previous checks (Email, Voters Roll, PEP and Sanctions) that would be sufficient to open the account.

API clients will also need to integrate the W2 Global SDK and develop the application screens, as part of the onboarding journey. This will enable clients to capture a document image and a selfie and pass these to Contis to enable verification to take place. Clients should only build the document upload capability and not the verification journey, this will be controlled by Contis.

W2 Address Examples

Forename Surname Day Of Birth Month Of Birth Year Of Birth Flat House Name / Number Street Postcode Result
Taylor Giles 19 6 1984  164 Ocean View WT1 1TD 007 Pass, No Sanctions, No PEPs – Overall Pass
Ellis Austin 23 5 1954  173 Ocean View WT1 1TD 007 Pass, No Sanctions, Single PEP – Overall Refer
See PEPDeskCheck Transaction object -> ServiceInterpretResult for more info
Ewan Wells 3 10 1961  191 Ocean View WT1 1TD 007 Pass, Single Sanctions, No PEP – Overall Refer
See SISPlusCheck Transaction object -> ServiceInterpretResult for more info
Isabelle Nolan 15 2 1973  999 Ocean View WT1 1TD 007 Refer (Single Name + DOB match), No Sanctions, No PEPs – Overall Refer
See W2_DATA_EKYC_UK_007_B Transaction object -> ServiceInterpretResult for more info
Andrew Kirk 10 10 1964  177 Ocean View WT1 1TD 007 Refer (Single Name + DOB match), No Sanctions, Single PEP – Overall Refer
See W2_DATA_EKYC_UK_007_B and PEPDeskCheck Transaction objects -> ServiceInterpretResult for more info

Kayleigh Weston 17 5 1952  195 Ocean View WT1 1TD 007 Refer (Single Name + DOB + Address match), Single Sanctions, No PEPs – Overall Refer
See W2_DATA_EKYC_UK_007_B and SISPlusCheck Transaction objects -> ServiceInterpretResult for more info
Sean Johnston 4 6 1983  163 Ocean View WT1 1TD 007 Fail (No matches), No Sanctions, No PEPs – Overall Refer
See W2_DATA_EKYC_UK_007_B Transaction object -> ServiceInterpretResult for more info
Oliver Thomson 30 1 1968  235 Ocean View WT1 1TD 007 Fail (Mortality Match, Multiple Sanctions, Multiple PEPs – Overall Refer
See W2_DATA_EKYC_UK_007_B, PEPDeskCheck and SISPlusCheck Transaction objects -> ServiceInterpretResult for more info
Isabelle Error 15 2 1973  168 Ocean View NP1 1NP 007 Error, Failover to 005 Pass, No Sanctions, No PEPs – Overall Pass
See W2_DATA_EKYC_UK_007_B, and W2_DATA_EKYC_UK_005 Transaction objects -> ServiceInterpretResult for more info