> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.idenfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

<Tip>
  For the full list of every tag value and its plain-English meaning, see [Verification Statuses → Fraud Tags](/guides/dashboard/kyc/verification-statuses#fraud-tags) and [→ Mismatch Tags](/guides/dashboard/kyc/verification-statuses#mismatch-tags).
</Tip>

## 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".

```json theme={"system"}
{
  "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.

```json theme={"system"}
{
  "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.

```json theme={"system"}
{
  "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`.

```json theme={"system"}
{
  "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.

<Tip>
  Wondering whether iDenfy will decide this for you, or how to build a procedure for resolving it? See [Status Handling](/guides/dashboard/kyc/status-handling#idenfy-does-not-evaluate-suspected).
</Tip>

## Next Steps

<CardGroup cols={2}>
  <Card title="Status Handling" icon="route" href="/guides/dashboard/kyc/status-handling">
    What to do with every overall status, not just SUSPECTED.
  </Card>

  <Card title="Verification Statuses" icon="circle-dot" href="/guides/dashboard/kyc/verification-statuses">
    Full definitions of every tag value.
  </Card>

  <Card title="Resolving False Positives" icon="tag" href="/guides/dashboard/kyc/resolving-false-positives-removing-mismatch-tags">
    Clear a tag from the dashboard.
  </Card>

  <Card title="Request Update" icon="pen" href="/kyc/request-update">
    Reactivate the token — POA, Risk Assessment, or Questionnaire cases only.
  </Card>
</CardGroup>


## Related topics

- [Status Handling](/guides/dashboard/kyc/status-handling.md)
- [Data Retrieval](/kyc/data-retrieval.md)
- [Resolving False Positives and Mismatch Tags](/guides/dashboard/kyc/resolving-false-positives-removing-mismatch-tags.md)
- [FAQ](/resources/faq.md)
- [Identification expired](/api-reference/webhooks/identification-expired.md)