Skip to content
English
  • There are no suggestions because the search field is empty.

What do the Stolen and Synthetic Identity scores mean?

Learn how to evaluate stolen and synthetic identity risk indicators in your verification workflow.

During Identity Verification, we analyze personal information to evaluate whether an identity may be fabricated or misused.

Two risk scores (0–100%) are generated:

  • Synthetic Identity Risk
  • Stolen Identity Risk

Each score is categorized as Low, Medium, or High to help guide review decisions.

Note: These scores indicate probability—not certainty. Final decisions should align with your organization’s risk tolerance and internal policies.


Risk Level Guidance

  • Low Risk: Proceed with standard verification.
  • Medium Risk: Consider additional verification steps.
  • High Risk: Recommend enhanced review before approval.

Synthetic Identity Risk

What it measures:
Indicates the likelihood that an identity was fabricated using a combination of real and false information.

Thresholds

  • Low: 0–59
  • Medium: 60–69
  • High: 70–100

Stolen Identity Risk

Indicates the likelihood that the information belongs to a real individual whose identity may be used fraudulently.

Thresholds

  • Low: 0–79
  • Medium: 80–89
  • High: 90–100

How Risk Is Evaluated

Risk scores are calculated by analyzing the consistency, history, and associations of user-provided information such as:

  • Name
  • Address
  • Phone number
  • Email
  • Date of birth
  • Social Security number

Signals evaluated may include:

  • Whether the identity is linked to a deceased individual
  • How many identities share the same phone number or email
  • Whether SSN issuance aligns with the individual’s age
  • The length of history tied to the SSN, phone number, or email

Data Matching Notes

Verification typically begins by matching records using the SSN or ID number, then comparing other details (such as name and address).

If an incorrect SSN is entered, the system may retrieve the wrong record, which can cause mismatches and lead to a failed verification. In these cases, document verification may be used as a fallback.