Incode’s Phone Risk Check determines the level of risk associated with a phone number. The Phone Risk Check module can be added to your workflow to evaluate the trust and potential risk of a phone number based on intelligence and behavioral signals.

Integration

User input flow

Phone Risk Check module configuration allows collection of user data via a user input flow where users can select the country code and type in their phone number. 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/kyc

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.

phone: (mandatory) String.
country: (mandatory) String. Must be "GL".

Example request:

{
"countryCode": "GL",
"phone": "+13421111234",
"plugins": [
"kyc"
],
"source": "PHONE_RISK_1"
}

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": "phoneValid",
"status": "true"
},
{
"key": "phoneFraudScore",
"status": "low"
},
{
"key": "phoneCarrier",
"status": "AT&T"
},
{
"key": "phoneLineType",
"status": "Wireless"
},
{
"key": "phoneActive",
"status": "true"
},
{
"key": "phoneVOIP",
"status": "false"
},
{
"key": "phonePrepaid",
"status": "false"
},
{
"key": "phoneRisky",
"status": "false"
},
{
"key": "phoneLeaked",
"status": "false"
},
{
"key": "phoneSpammer",
"status": "false"
},
{
"key": "overallLevel",
"status": "low"
}
]
}

eKYC error responses

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

For email, custom 400 error messages if country is “ “ or null:

Incode API Key	Status	Definition
phoneValid	true, false	Indicates if the phone number is properly formatted and considered valid based on assigned phone numbers available to carriers in that country.
phoneActive	true, false, Unknown	Indicates whether this phone number is a live, usable phone number that is currently active.
phoneVOIP	true, false, Unknown	Indicates whether this phone number is a Voice Over Internet Protocol (VOIP) or a digital phone number.
phonePrepaid	true, false, Unknown	Indicates whether this phone number is associated with a prepaid service plan.
phoneRisky	true, false, Unknown	Indicates whether this phone number is associated with fraudulent activity, scams, robocalls, fake accounts or other unfriendly behaviour.
phoneLineType	String	The type of line this phone number is associated with.
phoneLeaked	true, false	Indicates if this phone number has recently been exposed in an online database breach or compromise.
phoneSpammer	true, false	Indicates if the phone number has recently been reported for spam or harassing calls/texts.
phoneFraudScore	high, medium, low	Less than 75 - LOW 75 to 85 - MEDIUM Greater than 86 - HIGH
overallLevel	Very High, High, Medium, Low	VERY HIGH if: phoneValid == False OR phoneActive == False OR phoneRisky == True OR phoneFraudScore == High HIGH if: (phoneValid == False OR phoneActive == False) AND (phoneRisky == True OR phoneFraudScore == High) MEDIUM if: phoneValid == True AND phoneActive == True AND (phoneRisky == True OR phoneFraudScore == Medium) LOW if: Otherwise

Integration

User input flow

Module configuration

Direct API Approach

API Authentication

eKYC request

Direct API Response

API Authentication

Single Session Dashboard Result