eKYC (electronic Know Your Customer)
Identity Verification
eKYC, or electronic Know Your Customer, is a digital process for verifying the identity of customers online. eKYC verifies that the information provided by an end user, such as their name, date of birth, address, social security number, driver's license, matches against the records in a recognized database. Advanced security technologies in eKYC improve identity verification, protecting against cyber threats and fraud. Ultimately, eKYC customers will experience a seamless online onboarding experience, enhanced security, global accessibility, and abide regulatory compliance.
This comprehensive user guides starts off by showing an overarching view of the the eKYC module. As you continue to navigate through the tabs within the eKYC module, you can learn how to configure the exact fields you are looking to verify based on country and source of truth.
Integration
User input flow
eKYC module configuration gives various options to specify different search criteria with various sources of truth for each country (eg. US has multiple via Telco, Credit Bureau, and Driver's License). User data can be collected via a user input flow by using pre-selected fields where users can type in their name or date of birth, etc. See an example below:
Module configuration
The module configuration can be leveraged to select the applicable fields for the input data you would like to collect from the end user.
Direct API Approach
All module configurations and user data can be forwarded directly in the request for performing an eKYC search. This will override existing configuration and data collected about the user.
API Authentication
All endpoints require authentication headers to be specified as stated in Incode API Documentation
POST /omni/externalVerification/ekyc
This endpoint performs an eKYC check for the individual specified. Note: Endpoint can have empty body {} and in that case information will be pulled from module configuration and session details.
Note: Some fields are mandatory and others are optional depending on the data source and the country. These details are listed in the following tabs in eKYC.
- plugins: must be ["ekyc"]: (mandatory)
- source:: String. eKYC source(s) that to validate the below information against (eg. US_TELCO_1).
- firstName:: String. First name of the individual.
- surName: String. Last name or Surname of the individual.
- street: String. Full street including house number and apartment number.
- city: String. City of the individual's address.
- state: String. State of the individual's address.
- postalCode: String. Zipcode or postalCode formatted based on per-country postalCode basis.
- country: (mandatory) String. Two letter Alpha-2 country code. (eg. US, BR, CN).
- taxId: String. Tax ID of the individual (eg. SSN in US, CPF in Brazil).
- dateOfBirth: String. Format: yyyy-mm-dd (eg. 1986-01-04)
- email: String. Email address of the individual.
- phone: String. Phone number of the individual.
Conditions
eKYC results can be used in conditions to impact further user journey or session result:
- Overall eKYC Level: The overall eKYC risk level: 'LOW', 'MEDIUM', 'HIGH', 'VERY_HIGH'
- Tax ID Status: The overall tax ID match status: 'MATCH', 'FUZZY', 'NO MATCH'
- Tax ID Level: The overall tax ID risk level: 'LOW', 'MEDIUM', 'HIGH', 'VERY_HIGH'
- Phone Level: The overall phone risk level: 'LOW', 'MEDIUM', 'HIGH', 'VERY_HIGH'
Single Session Dashboard Results
They are available on Single Session view under ID Verification tab
Direct API Response
All module configurations and user data can be forwarded directly in the request for performing an eKYC verification check. This will override existing configuration and data collected about the user.
API Authentication
All endpoints require authentication headers to be specified as stated in Incode API Documentation
Note: Endpoint can have empty body {} and in that case information will be pulled from module configuration and session details.
RESPONSE EXAMPLE
{
"kyc": [
{
"key": "addressRiskLevel",
"status": "low"
},
{
"key": "emailDomainLevel",
"status": "low"
},
{
"key": "emailLevel",
"status": "low",
"reasonCodes": [
"EAF4Y"
]
},
{
"key": "phoneCarrier",
"status": "Verizon"
},
{
"key": "phoneLevel",
"status": "low",
"reasonCodes": [
"PAVN",
"PML",
"PPC9"
]
},
{
"key": "phoneLineType",
"status": "Mobile"
},
{
"key": "taxIdAddressMatch",
"status": "exact"
},
{
"key": "taxIdCityMatch",
"status": "exact"
},
{
"key": "taxIdDobMatch",
"status": "exact"
},
{
"key": "taxIdLevel",
"status": "low",
"reasonCodes": [
"TLADB"
]
},
{
"key": "taxIdMatch",
"status": "exact"
},
{
"key": "taxIdNameMatch",
"status": "exact"
},
{
"key": "taxIdStateMatch",
"status": "exact"
},
{
"key": "taxIdZipcodeMatch",
"status": "exact"
},
{
"key": "overallLevel",
"status": "low"
}
]
}
Please refer to error response to see conventional HTTP response codes to indicate the success or failure of an API request.
eKYC analytics
To identify trends within your end-user verification strategy over time and at a higher level than analyzing each individual's verification, you can take advantage of our analytics dashboard.
Provisioning
To obtain comprehensive details on the pricing and provisioning of the eKYC module, we encourage you to contact our dedicated customer support team. Our experts are on hand to assist you in tailoring a workflow that precisely meets your unique requirements, guiding you through the most effective configuration options for your specific use case. This personalized approach ensures that you leverage the full potential of the eKYC module, optimizing your workflows for security and compliance. Our team is committed to providing you with the support and insights needed to make informed decisions, ensuring a seamless integration process.
Updated 3 months ago