Suspected Status

Understand why an iDenfy KYC verification resolves to SUSPECTED, which mismatch tags trigger it, and worked examples for common review cases.

A verification resolves to SUSPECTED when the document and face checks themselves succeeded, but the system attached one or more fraudTags or mismatchTags to the result. SUSPECTED never appears without at least one of those tags present — it exists specifically to carry that signal to you.

For the full list of every tag value and its plain-English meaning, see Verification Statuses → Fraud Tags and → Mismatch Tags.

Worked Examples

The same shape repeats every time: autoDocument/autoFace (and manualDocument/manualFace, if reviewed) come back clean, but a tag is present. Only the tag differs.

A Data Mismatch

You created the session with firstName: "Jon". The document reads “John”.

{
  "status": {
    "overall": "SUSPECTED",
    "mismatchTags": ["NAME"],
    "fraudTags": [],
    "autoDocument": "DOC_VALIDATED",
    "autoFace": "FACE_MATCH"
  },
  "scanRef": "d2714c8a-...",
  "clientId": "user-123"
}

The document and face are genuinely valid — the flag exists purely because the name you supplied doesn’t exactly match the document.

An Age Policy Flag

You configured ageLimit, and the document’s date of birth puts the client under it.

{
  "status": {
    "overall": "SUSPECTED",
    "mismatchTags": ["UNDER_AGE"],
    "fraudTags": [],
    "autoDocument": "DOC_VALIDATED",
    "autoFace": "FACE_MATCH"
  }
}

The document is real and the face matches — this tag exists only to enforce a policy you configured, not to flag a fake document.

An AML/Watchlist Hit

AML screening (checkAml) found the client on a PEPs or sanctions list.

{
  "status": {
    "overall": "SUSPECTED",
    "fraudTags": ["AML_SUSPECTION"],
    "mismatchTags": [],
    "autoDocument": "DOC_VALIDATED",
    "autoFace": "FACE_MATCH"
  }
}

Nothing about the document or selfie is in question — the flag is about who the person is, screened against an external list.

A Duplicate Signal

checkDuplicateFaces is enabled, and this selfie matches a face from a previous verification — possibly under a different clientId.

{
  "status": {
    "overall": "SUSPECTED",
    "fraudTags": ["DUPLICATE_FACE"],
    "mismatchTags": [],
    "autoDocument": "DOC_VALIDATED",
    "autoFace": "FACE_MATCH"
  }
}

This can mean one person opening a second account — which is sometimes abuse, and sometimes a legitimate returning user or a shared household device. The tag can’t tell you which; only your context can.

Wondering whether iDenfy will decide this for you, or how to build a procedure for resolving it? See Status Handling.

Next Steps

Status Handling

What to do with every overall status, not just SUSPECTED.

Verification Statuses

Full definitions of every tag value.

Resolving False Positives

Clear a tag from the dashboard.

Request Update

Reactivate the token — POA, Risk Assessment, or Questionnaire cases only.