eKYC leverages U.S. telco databases to streamline and enhance the customer identity verification process by accessing telecommunications data for more accurate and efficient authentication, reducing fraud, and ensuring regulatory compliance.

Integration

eKYC module configuration for the US Telco source requires that both phone is a mandatory field as you are verifying the other fields (eg. name) against the phone. You will even notice in our API responses a "phoneNameMatch" for example.

Module configuration

In a flow, configure eKYC check and make sure to only check on Name, Address, Phone. See below

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

eKYC request

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.

• plugins: must be ["kyc"]: (mandatory)
• source:: (mandatory) String. Must be: "US_TELCO_1".
• phone: (mandatory) String. Phone number of the individual (eg. +14081234567)
• firstName:: (mandatory) String. First name of the individual.
• surName: (mandatory) String. Last name of the individual.
• street: (optional) String. Full street including house number and apartment number.
• city: (optional) String. City of the individual's address. (eg. San Francisco).
• state: (optional) String. Two letter state of the individual's address (eg. CA).
• postalCode: (optional) String. postalCode formatted based on per-country postalCode basis.
• country: (mandatory) String. Two letter Alpha-2 country code. (Must be US).
• dateOfBirth: (optional) String. Format: yyyy-mm-dd (eg. 1986-01-04)
• email: (optional) String. Email address of the individual (eg. [email protected])
• dlNumber: (optional) String. Driver's license number of individual (eg. F1234566)
• dlState: (optional) String. Two letter driver's license state of individual (eg. CA)
• last4SSN: (optional) String. Last 4 digits of SSN (eg. 1234)

Direct API Response

📘

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.

{
    "kyc": [
        {
            "key": "nameRiskLevel",
            "status": "low"
        },
        {
            "key": "addressRiskLevel",
            "status": "medium"
        },
        {
            "key": "phoneLevel",
            "status": "low",
            "reasonCodes": [
                "PML",
                "PPC5"
            ]
        },
        {
            "key": "dlNumberCheck",
            "status": "No Match",
            "reasonCodes": [
                "PDL"
            ]
        },
        {
            "key": "dlStateCheck",
            "status": "No Match"
        },
        {
            "key": "phoneDobMatch",
            "status": "Exact"
        },
        {
            "key": "phoneNameMatch",
            "status": "Exact"
        },
        {
            "key": "phoneAddressMatch",
            "status": "Partial Match",
            "reasonCodes": [
                "APA"
            ]
        },
        {
            "key": "phoneCityMatch",
            "status": "Exact"
        },
        {
            "key": "phoneZipcodeMatch",
            "status": "Exact"
        },
        {
            "key": "phoneStateMatch",
            "status": "Exact"
        },
        {
            "key": "overallLevel",
            "status": "low"
        }
    ]

overallLevel

overallLevel is the API response key for the submitted name. The fields low, medium, and high are mapped to a proprietary fuzzy matching algorithm that is mapped to a score from 0 to 100.

As a default, overallLevel will return:

• low: when phoneNameMatch & phoneAddressMatch are exact
• medium:
  • Rule 1: when phoneNameMatch is exact & phoneAddressMatch are partialmatch or nomatch OR
  • Rule 2: when phoneNameMatch is nomatch & phoneAddressMatch is a partialmatch
• high: when phoneNameMatch & phoneAddressMatch are nomatch

nameRiskLevel

nameRiskLevel is the API response key for the submitted name. The fields low, medium, and high are mapped to a proprietary fuzzy matching algorithm that is mapped to a score from 0 to 100.

As a default, nameRiskLevel will return:

• low: matching score is between 70-100
• medium: matching score is between 30-70
• high: matching score is less than 30

addressRiskLevel

addressRiskLevel is the API response key for the submitted name. The fields low, medium, and high are mapped to a proprietary fuzzy matching algorithm that is mapped to a score from 0 to 100.

As a default, addressRiskLevel will return:

• low: matching score is 70 <= score <= 100
• medium: matching score is between 30 <= score < 70
• high: matching score <= 30

eKYC error responses

Please refer to error response to see conventional HTTP response codes to indicate the success or failure of an API request.

Single Session Dashboard Result

eKYC Reason Codes

See above in the example single session dashboard results, you can see the bottom section "Codes" that can help you further interpret the results of matches and risk levels in your single session dashboard. All reason codes can be accessed here. Below you can see all the potential applicable reason codes that might be populated from this source: