Global Identity Check

A service that produces a quick overall identity risk assessment by validating and linking the User name, address, email, telephone, and IP address against publicly known directories. Global Identity Check assesses the overall risk of an identity and delivers an overall risk score.

The service provides an overall identity risk score which translates to a passed, rejected or warning outcome.

The overall outcome is determined by looking for linkages, validations and behavior of the input elements across two primary sources of information:

Identity graph
Identity network.

Identity Graph

The Identity Graph is used to validate the identity elements.

For example:

Does this email belong to the person?
What type of phone number is this?

The Identity graph is built from over 70 trusted and thoroughly vetted database sources includingTelcos, Government, Agencies, utilities, Voter registration, and Census data.

Identity Network

The Identity Network focuses on how the identity elements are used online.

For example:

When was this email first/last used?
How many times has this address been used?
Why is this phone number associated with 50 IP addresses?

The network analyzes patterns of how information is being used in digital interactions. It is made up of more than 400M global monthly queries that surface usage patterns of identity data.

Use Case: Lightweight Verification for Onboarding

Onboarding at a Financial Institution will require vetting of the provided personal information as part of an accounting opening process. Global Identity Check offers a lightweight check to validate Name, Address, Email and Phone information.

It is often combined with other risk signals like Device and more stringent checks on Name, Address, DOB and SSN. The outcome of these checks often drive the authentication methods given to the customer.

Supported Credentials

The following values can be uploaded as Prepared Data. Alternatively, they can be extracted by an upstream capability in a workflow.

To use Prepared Data with global identity check as a standalone capability use workflow key 10007.

Supported Credentials

Key	Type	Mandatory	Description
firstName	string	no	Optimal to include.
middleName	string	no	Middle name of the subject.
lastName	string	no	Optimal to include.
address	object	yes	Address details
address.line1	string	no	First line of the address.
address.line2	string	no	Second line of the address.
address.city	string	yes	City of residence as it appears on the ID.
address.postalCode	string	yes	Postal or zip code.
address.subdivision	string	no	City subdivision of residence as it appears on the ID.
address.country	string	yes	Country in ISO-3166-1 Alpha-3 Code or ISO-3166-1 Alpha-2 Code format.
phoneNumber	string	yes	Phone number of the subject in E.164 format. Country code is required.
email	string	no	Optimal to include.
ipAddress	string	no	The IP address entered as a string. Either IPv4 or IPv6 format is accepted.

Example: Prepared Data Body

{
    "firstName": "M***in",
    "lastName": "C***g",
    "email": "m***inc***g@gmail.com",
    "phoneNumber": "+65644***8",
    "ipAddress": "122.23.23.233",
    "address": {
   	 "line1": "153 Rd",
   	 "line2": null,
   	 "city": "Singapore",
   	 "postalCode": "42***1",
   	 "country": "SGP"
    }
}

Example Response

"capabilities": {
  "globalIdentityCheck": [
    {
      "id": "d1c96816-3beb-490d-9243-7e58cc9ed2f1",
      "credentials": [
        {
          "id": "81e9001e-e4d3-4836-8bda-d475330e8224",
          "category": "DATA"
        }
      ],
      "decision": {
        "type": "REJECTED",
        "details": {
          "label": "HIGH_RISK"
        }
      },
      "data": {
        "emailValid": false,
        "emailDomainCreationDate": "1995-08-13",
        "emailMatchToName": "no - match",
        "emailFirstSeenDays": 4682,
        "phoneValid": true,
        "phoneMatchToName": "match",
        "phoneLineType": "MOBILE",
        "phoneCarrier": "Singapore Telecommunications Ltd (singtel)",
        "phoneCountryCode": "SG",
        "phoneLastSeenDays": 49.0,
        "phoneEmailFirstSeenDays": 646.0,
        "phoneMatchToAddress": "country-match",
        "addressValidityLevel": "valid",
        "addressMatchToName": "match",
        "ipRisk": false,
        "ipRiskScore": 0.951,
        "ipLastSeenDays": 4.0,
        "ipGeolocationCountryCode": "US",
        "ipGeolocationSubdivision": "Oregon",
        "ipAddressDistance": 8127.0,
        "identityNetworkScore": 0.934,
        "identityRiskScore": 469
      }
    }
  ]
}

Decision Details Labels

Details

Decision Type	Label	Description
PASSED	LOW_RISK	No significant risk associated with the data.
REJECTED	HIGH_RISK	High risk associated with the data.
WARNING	MEDIUM_RISK	Moderate risk associated with the data.
NOT_EXECUTED	VALIDATION_FAILED	The data provided failed validation.
NOT_EXECUTED	NOT_ENOUGH_DATA	Not enough data to process the request.
NOT_EXECUTED	PRECONDITION_NOT_FULFILLED	Preconditions were not met to process the data.
NOT_EXECUTED	TECHNICAL_ERROR	There was an error in processing the request.

Data

Details

Parameter	Type	Possible Values / Description
emailValid	boolean	`true`, `false` – True if the email address is valid.
emailDomainCreationDate	string	Date in `YYYY-MM-DD` format.
emailMatchToName	string	`"not-found"`, `"match"`, `"no-match"` – Match status between input names and the queried entity.
emailFirstSeenDays	string	`null`: input email missing, `0`: never seen before (high risk), `1-90`: very high risk, `91-365`: neutral risk, `366+`: low risk.
phoneValid	boolean	`true`, `false` – True if the phone number is valid.
phoneMatchToName	string	`"not-found"`, `"match"`, `"no-match"` – Match status between input names and the queried entity.
phoneLineType	string	`null` (if invalid or unknown), `"Landline"`, `"Fixed-VoIP"`, `"Mobile"`, `"Voicemail"`, `"Toll-free"`, `"Premium"`, `"Non-fixed-VoIP"`, `"Other"`.
phoneCarrier	string	The company providing voice/data services for the phone number.
phoneCountryCode	string	ISO-3166 alpha-2 country code of the phone number.
phoneLastSeenDays	integer	Count of days since the phone was last observed. `0` if never seen before.
phoneEmailFirstSeenDays	integer	Count of days since the combination of phone and email was first observed. `0` if never seen before.
phoneMatchToAddress	string	`"match"`, `"postal-match"`, `"zip4-match"`, `"city-state-match"`, `"metro-match"`, `"country-match"`, `"no-match"` – Phone location vs. input address match status.
addressValidityLevel	string	`"valid_to_house_number"`, `"valid_to_street"`, `"valid_to_city"`, `"valid_to_country"`, `"valid"`, `"invalid"`, `"missing_address"`, `"valid_to_house_number_missing_apt"`.
addressMatchToName	string	`"not-found"`, `"match"`, `"no-match"` – Match status between input names and the queried entity.
ipRisk	boolean	`true`, `false` – True if the IP address is considered risky.
ipRiskScore	number	Risk score (0 to 1), rounded to three decimal places. Higher score indicates greater risk.
ipLastSeenDays	integer	Count of days since the IP address was last observed. `0` if never seen before.
ipGeolocationCountryCode	string	ISO-3166 alpha-2 country code for the geolocation of the IP.
ipGeolocationSubdivision	string	More granular detail about the IP address location.
identityNetworkScore	double	Machine learning prediction of risk (0.000 - 1.000). `<0.33`: low risk, `0.33-0.8`: uncertain, `>0.8`: high risk. `null` when timeout occurs.
identityRiskScore	integer	Risk score (`0-500`). `<250`: low risk, `250-350`: uncertain, `>350`: high risk. `null` when timeout occurs.

Network Score

Activity patterns that the Network Score focuses on include the following:

Velocity: how often element(s) are used
Popularity: At how many merchants element(s) are used
Volatility: how often element(s) are used with other elements
Age/maturity: when elements were first/last seen

The Network Score is derived from an Identity Network, which is made up of more than 400M global monthly queries that surface usage patterns of identity data provided by our network of customers.

The Identity Risk Score is a comprehensive risk score calculated in real time that combines authoritative data (match statuses, metadata, linkages) from the Identity Graph as well as usage patterns of elements in the Identity Network

To return a score, we need at least one valid element. For best results, we recommend sending as much of the following information as possible:

Name
Phone
Address
Email Address

Identity Graph​

Identity Network​

Use Case: Lightweight Verification for Onboarding​

Supported Credentials​

Example: Prepared Data Body​

Example Response​

Decision Details Labels​

Data​

Network Score​

Table of Contents

Identity Graph

Identity Network

Use Case: Lightweight Verification for Onboarding

Supported Credentials

Example: Prepared Data Body

Example Response

Decision Details Labels

Data

Network Score