Suspicions

Suspicion types

fraudTags

FACE_IN_BLACKLIST

Explanation:

This particular verification face photo was added to face blacklist.

DOC_FACE_IN_BLACKLIST

Explanation:

This particular verification document face photo was added to document blacklist.

DATA_BLACKLISTED

Explanation:

Verification data has been matched against an already existing blacklist entry.

DATA_IN_BLACKLIST

Explanation:

This verification data has been used to create a blacklist entry, e.g., when a scanRef is added to a blacklist.

DUPLICATE_FACE

Explanation:

A face matched with an earlier done verification selfie.

DUPLICATE_DOC_FACE

Explanation:

A document face matched with an earlier done verification document face.

DUPLICATE_PERSONAL_DATA

Explanation:

This verification has duplicated personal data from an earlier done verification.

DUPLICATE_PERSONAL_DATA

Explanation:

Document information matched with previously done verification.

VIRTUAL_CAMERA

Explanation:

Likely virtual camera was detected.

ADDRESS_UNVERIFIED

Explanation:

Address verification hasn't been performed or its status is unverified.

PORTRAIT_SUBSTITUTION

Explanation:

Passive document liveness failed to successfully validate the document photo and marked it as potentially replaced/substituted.

FACE_SUSPECTED

Explanation:

Automatic algorithms triggered a suspicion that selfie face is not genuine.

FACE_BLACKLISTED

Explanation:

Verification selfie has been matched against an already existing blacklist entry.

DOC_FACE_BLACKLISTED

Explanation:

Verification document face has been matched against an already existing blacklist entry.

DOC_MOBILE_PHOTO

Explanation:

A photo of a document is shown from a mobile screen.

DEV_TOOLS_OPENED

Explanation:

A client performing verification has opened dev-tools in the browser.

DOC_PRINT_SPOOFED

Explanation:

Automatic algorithms triggered a suspicion that the document is printed on paper.

FAKE_PHOTO

Explanation:

General identifier for a fake photo.

AML_SUSPECTION

Explanation:

A client is found in PEPs or Sanctions list.

AML_FAILED

Explanation:

AML check failed.

LID_SUSPECTION

Explanation:

Client's document is found in lost or stolen documents database.

LID_FAILED

Explanation:

LID check failed.

CRIMINAL_SUSPECTED

Explanation:

A record was found in the criminal database that potentially matches document data.

CRIMINAL_CHECK_FAILED

Explanation:

Criminal check failed.

RC_FAILED

Explanation:

Registry Center check failed.

DL_FAILED

Explanation:

AAMVA driver license check failed.

AUTO_UNVERIFIABLE

Explanation:

This verification cannot be automatically verified and needs to be verified by a human.

mismatchTags

NAME

Explanation:

The user's name provided by the partner does not match the name extracted from the document.

SURNAME

Explanation:

The user's surname provided by the partner does not match the surname extracted from the document.

DOCUMENT_NUMBER

Explanation:

The document number provided by the partner does not match the document number extracted from the document.

PERSONAL_CODE

Explanation:

The personal code provided by the partner does not match the personal code extracted from the document.

EXPIRY_DATE

Explanation:

The expiry date provided by the partner does not match the expiry date extracted from the document.

DATE_OF_BIRTH

Explanation:

The date of birth provided by the partner does not match the date of birth extracted from the document.

DATE_OF_ISSUE

Explanation:

The date of issue provided by the partner does not match the date of issue extracted from the document.

NATIONALITY

Explanation:

The user's nationality provided by the partner does not match the nationality extracted from the document.

SEX

Explanation:

The gender provided by the partner does not match the gender extracted from the document.

FULL_NAME

Explanation:

The full name provided by the partner does not match the full name extracted from the document.

DOC_INFO_MISMATCH

Explanation:

Some of the provided data by the partner does not match the extracted data from the document, and the "Detect info mismatch" setting is turned off. If the "Detect info mismatch" setting is activated, and discrepancies are detected, a specific mismatch tag (e.g., NAME, SURNAME, etc.) will be applied, otherwise verification is placed as SUSPECTED in our dashboard - with the webhooks expect to receive "overall":"DENIED" with: - "autoDocument":"DOC_INFO_MISMATCH", - "manualDocument":"DOC_INFO_MISMATCH".

UNDER_AGE

Explanation:

The age derived from the document is below the partner's minimum age requirement.

OVER_AGE

Explanation:

The age derived from the document is above the partner's minimum age requirement.

UNKNOWN_AGE

Explanation:

The document does not contain age information, but the partner has set a minimum age requirement.

INVALID_ADDITIONAL_STEP

Explanation:

The document provided for the additional step (e.g. Proof of address, Utility bill) is found to be invalid.

ADDITIONAL_STEP_NOT_FOUND

Explanation:

The document required for the additional step (e.g. Utility bill, Proof of address) could not be located.

ADDITIONAL_STEP_INFORMATION_MISMATCH

Explanation:

The information from the additional step (e.g., Proof of Address or Utility Bill) does not match the information provided by the partner.

EXPIRED_ADDITIONAL_STEP_INFORMATION

Explanation:

The document provided for the additional step (e.g., Proof of address, Utility Bill) is expired.

REGISTRY_CENTER_INFO_MISMATCH

Explanation:

The information obtained from the Registry Center database does not match the information extracted from the document.

DRIVER_LICENSE_INFO_MISMATCH

Explanation:

Provided information does not match with information in the AAMVA database

(DEPRICATED) suspicionReasons

Explanation:

Parameter is retained for backward compatibility and may return tags from mismatchTags or fraudTags.

If at least one of these tags are present, the verification will be marked as SUSPECTED

---

understanding suspicion status

A SUSPECTED status doesn't mean automatic failure. Always check the document (manualDocument) and face (manualFace) statuses too (e.g., for DOC_VALIDATED, FACE_MATCH), as they might still be approved.

Handling SUSPECTED status

• If a webhook's overall status is SUSPECTED, check the fraudTags and mismatchTags lists (in the status object) for specific reasons.
• Use fraudTags and mismatchTags in combination with document/face validation results to decide whether to onboard the user.
• Important: Prepare your system to handle new, unexpected tag values appearing in the future.

Callback Status Example with Suspected Status

{
    ...
    "status": {
        "overall": "SUSPECTED",
        "mismatchTags": ["UNDER_AGE", "NAME"],
        "fraudTags": ["FACE_IN_BLACKLIST", "AML_SUSPECTION"],
        "autoDocument": "DOC_VALIDATED",
        "autoFace": "FACE_MATCH",
        "manualDocument": "DOC_VALIDATED",
        "manualFace": "FACE_MATCH",
        "additionalSteps": null
    ...
  }