eKYC US Telco 5 leverages US telco sources of truth 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

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

eKYC request

POST /omni/externalVerification/ekyc

This endpoint performs an eKYC check for the individual specified.

• plugins: must be["kyc"]: (mandatory)
• source:: (mandatory) String. Must be: "US_TELCO_5".
• phone: (mandatory) String. Phone number of the individual (eg. +14081234567)
• firstName:: (optional) String. First name of the individual.
• middlName(optional)String. Middle name of the individual
• surName: (optional) 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.
• countryCode: (mandatory) String. Two letter Alpha-2 country code. Must be: US
• dateOfBirth: (optional) String. Format: yyyy-mm-dd (eg. 1986-01-04)
• emailAddress: (Optional) String. (only if we receive an input in the emailAddress field in the Incode eKYC request).
• idNumber(optional) String. Always will be SSN.

Example request:

{
"plugins": [
    "kyc"
    ],
    "source": "US_TELCO_5", //Mandatory - Must be US_Telco_5
    "firstName": "John", //Optional
    "middleName": "Michael", //Optional
    "surName": "Doe", //Optional
    "street": "42 Baker St", //Optional // House Number and Street
    "postalCode": "98101", //Optional
    "countryCode": "US", //Mandatory - Must be US
    "phone": "+12506581904", //Mandatory
    "state": "WA", //Optional
    "city": "Seattle", //Optional
    "dateOfBirth": "1985-04-23", //Optional - Format yyyy-mm-dd 
    "ssn": "123456789", //Optional - Format 9 digits
  	"emailAddress": "[email protected]" //Optional

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": "checkStatus",
            "status": "pass"
        },
        {
            "key": "phoneFirstNameMatch",
            "status": "exact"
        },
        {
            "key": "phoneMiddleNameMatch",
            "status": "exact"
        },
        {
            "key": "phoneLastNameMatch",
            "status": "exact"
        },
        {
            "key": "phoneNameMatch",
            "status": "exact"
        },
        {
            "key": "phoneDobMatch",
            "status": "exact"
        },
        {
            "key": "taxIdMatch",
            "status": "nomatch"
        },
        {
            "key": "activityScore",
            "status": "900"
        },
        {
            "key": "phoneCarrier",
            "status": "Fastweb - full mvno TIM"
        },
        {
            "key": "phoneLineType",
            "status": "mobile"
        },
        {
            "key": "lastPorted",
            "status": "2020-02-02"
        },
        {
            "key": "phoneEmailMatch",
            "status": "nomatch"
        },
        {
            "key": "emailType",
            "status": "Unknown"
        },
        {
            "key": "phoneStreetMatch",
            "status": "nomatch"
        },
        {
            "key": "phoneCityMatch",
            "status": "nomatch"
        },
        {
            "key": "phoneStateMatch",
            "status": "nomatch"
        },
        {
            "key": "phoneZipcodeMatch",
            "status": "nomatch"
        },
        {
            "key": "phoneAddressMatch",
            "status": "nomatch"
        },
        {
            "key": "overallLevel",
            "status": "low"
        }
    ],
    "income": []
}

Note: unknown is generated when the source of truth does not have this information available.

overallLevel

Overall Level 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 AND (phoneDobMatch OR taxIdmatch ) are exact

High: when phoneNameMatch AND (phoneDobMatch OR taxIdMatch) are no match

Medium: for all otherwise combination.

eKYC error responses

• Please refer to error response to see conventional HTTP response codes to indicate the success or failure of an API request.
• If phone is not in international E.164 format, you will see an error message.
• If both mandatory fields (phone & countryCode) are not submitted, you will see an error message

Single Session Dashboard Result