> ## 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.
# Verification Statuses
> Understand iDenfy verification statuses including approved, denied, suspected, reviewing, and expired and how each affects your workflow.
## Overall Status
| Status | Meaning |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **APPROVED** | Automated and manual checks were successful. Check `autoFace`, `manualFace`, `autoDocument`, `manualDocument` for details. Typical success: `FACE_MATCH` + `DOC_VALIDATED`. |
| **DENIED** | Verification failed. Check detailed statuses for the reason (e.g., `FACE_MISMATCH`, `DOC_NOT_FOUND`). |
| **SUSPECTED** | Checks may have passed, but discrepancies were found — flagged with `fraudTags` or `mismatchTags`. You decide whether to approve or deny. |
| **REVIEWING** | A human reviewer is currently checking the verification. Contact support to toggle this feature. |
| **EXPIRED** | The verification token was never used and has expired. |
| **ACTIVE** | The token has been created but not yet used. |
| **EXPIRED-DELETED** | Token expired and data was deleted. |
| **DELETED** | Verification data has been deleted. |
| **ARCHIVED** | Verification data was archived. |
`APPROVED` and `DENIED` are explained by the detailed statuses on the `autoFace`, `manualFace`, `autoDocument`, and `manualDocument` fields below, and `SUSPECTED` by the `fraudTags`/`mismatchTags` below. For what to do with each status in your integration, see [Status Handling](/guides/dashboard/kyc/status-handling).
***
## Common Values
| Value | Description |
| ---------- | ------------------------------------------------------------ |
| `clientId` | A unique string identifying a client on your side. |
| `scanRef` | A unique string identifying a verification on iDenfy's side. |
***
## Face Status Values
| Status | Description |
| ------------------- | -------------------------------------------------------------------------------------------- |
| `FACE_MATCH` | Selfie face matches the document photo. Person and document owner are the same. |
| `FACE_MISMATCH` | Face could not be matched — features not fully visible, low quality, blur, shadow, or glare. |
| `NO_FACE_FOUND` | Face cannot be accurately determined in the selfie. |
| `TOO_MANY_FACES` | More than one face visible in the selfie. |
| `FACE_TOO_BLURRY` | Selfie too blurry for face matching. |
| `FACE_ERROR` | Unclassified error during face matching. |
| `FACE_NOT_ANALYSED` | Verification denied for another reason — face analysis skipped. |
| `FACE_NOT_CHECKED` | Selfie was not compared to the document face. |
| `FAKE_FACE` | Photo not taken in real time, virtual camera detected, or face is fake. |
| `FACE_GLARED` | Glare detected in selfie photo. |
| `FACE_UNCERTAIN` | Face liveness cannot be determined — poor lighting, potential fake, or obstructions. |
***
## Document Status Values
| Status | Description |
| --------------------------- | ----------------------------------------------------------------------------- |
| `DOC_VALIDATED` | Document is valid — all data visible, readable, and genuine. |
| `DOC_NOT_FOUND` | No document found in the photo. |
| `DOC_NOT_FULLY_VISIBLE` | Document or data not fully visible — blur, shadow, glare, fingers, or damage. |
| `DOC_NOT_SUPPORTED` | Document type not supported for selected country or session. |
| `DOC_FACE_NOT_FOUND` | Face could not be located on the document. |
| `DOC_NAME_ERROR` | Name field could not be found or parsed. |
| `DOC_SURNAME_ERROR` | Surname field could not be found or parsed. |
| `DOC_EXPIRY_ERROR` | Expiry date field could not be found or parsed. |
| `DOC_DOB_ERROR` | Date of birth field could not be found or parsed. |
| `DOC_PERSONAL_NUMBER_ERROR` | Personal code could not be found or parsed. |
| `DOC_NUMBER_ERROR` | Document number could not be found or parsed. |
| `DOC_DATE_OF_ISSUE_ERROR` | Date of issue field could not be found or parsed. |
| `DOC_SEX_ERROR` | Sex field could not be found or parsed. |
| `DOC_NATIONALITY_ERROR` | Nationality field could not be found or parsed. |
| `DOC_GLARED` | Document glared — data parsing cannot be performed. |
| `DOC_FACE_GLARED` | Document face area is glared. |
| `DOC_TOO_BLURRY` | Document too blurry for parsing. |
| `DOC_NOT_ALLOWED` | Document readable but type not allowed in your settings. |
| `DOC_EXPIRED` | Document has expired. |
| `DOC_ERROR` | Unclassified error during document analysis. |
| `DOC_NOT_ANALYSED` | Verification denied for another reason — document analysis skipped. |
| `DOC_DAMAGED` | Document is physically damaged (cracked, broken). |
| `DOC_FAKE` | Document detected as not genuine (virtual camera, photo of screen). |
| `DOC_SPOOF_DETECTED` | Document detected as not real. |
| `DOC_SIDE_MISMATCH` | Document side different than expected. |
| `DOC_TYPE_MISMATCH` | Selected document type doesn't match the shown document. |
| `DOC_PERSONAL_CODE_INVALID` | Personal code could not be verified. |
| `DOC_INFO_MISMATCH` | Information provided doesn't match the document. |
| `AUTO_UNVERIFIABLE` | Cannot be automatically verified — needs human review. |
| `COUNTRY_NOT_SUPPORTED` | Document country not supported. |
| `COUNTRY_MISMATCH` | Selected country and document issuing country don't match. |
| `NFC_FAILED` | NFC read/authentication failed. |
| `NFC_TIMEOUT` | Client didn't finish NFC read in time. |
| `EID_FAILED` | E-ID (electronic ID) capture was not taken successfully. |
***
## MRZ and Barcode Statuses
| Status | Description |
| ----------------------- | ------------------------------------------------------------ |
| `MRZ_NOT_FOUND` | Machine Readable Zone could not be located. |
| `MRZ_OCR_READING_ERROR` | Failed to read/parse MRZ — possible check-digit discrepancy. |
| `MRZ_INVALID` | MRZ is invalid and cannot be verified. |
| `BARCODE_NOT_FOUND` | Document barcode could not be located. |
***
## Fraud Tags
| Tag | Description |
| ------------------------------ | --------------------------------------------------------------------------------- |
| `AML_SUSPECTION` | Client found in PEPs or Sanctions list (AML enabled). |
| `AML_FAILED` | AML check failed (AML enabled). |
| `LID_SUSPECTION` | Document found in lost/stolen documents database (LID enabled). |
| `LID_FAILED` | LID check failed. |
| `CRIMINAL_SUSPECTED` | Criminal check found a hit that needs to be reviewed. |
| `CRIMINAL_CHECK_FAILED` | Criminal check was not initiated successfully and needs to be initiated manually. |
| `DL_FAILED` | The DMV database is currently unavailable, try again later. |
| `RC_FAILED` | Failed to check registry center (RC) data. |
| `FAKE_PHOTO` | General identifier for a fake photo. |
| `VIRTUAL_CAMERA` | Virtual camera likely detected. |
| `DEV_TOOLS_OPENED` | Client opened browser dev-tools during verification. |
| `DUPLICATE_FACE` | Selfie matched with a previous verification. |
| `DUPLICATE_DOC_FACE` | Document face matched with a previous verification. |
| `DUPLICATE_PERSONAL_DATA` | Document data matched with a previous verification. |
| `FACE_IN_BLACKLIST` | Face photo added to blacklist. |
| `DOC_FACE_IN_BLACKLIST` | Document face added to blacklist. |
| `DOC_FACE_BLACKLISTED` | Document face matched an existing blacklist entry. |
| `FACE_SUSPECTED` | Automatic algorithms suspect the selfie is not genuine. |
| `FACE_BLACKLISTED` | Selfie matched an existing blacklist entry. |
| `DATA_BLACKLISTED` | Data matched against an existing blacklist entry. |
| `DATA_IN_BLACKLIST` | Verification data used to create a blacklist entry. |
| `PORTRAIT_SUBSTITUTION` | Document photo may have been replaced/substituted. |
| `DOCUMENT_TOO_CLOSE_TO_BORDER` | Document image too close to frame border for liveness validation. |
| `DOC_MOBILE_PHOTO` | Document shown from a mobile screen. |
| `DOC_PRINT_SPOOFED` | Document appears to be printed on paper. |
***
## Mismatch Tags
These appear when data provided during session creation doesn't match document data:
| Tag | Description |
| ------------------------------- | --------------------------------------------------------- |
| `NAME` | Client name doesn't match document. |
| `SURNAME` | Client surname doesn't match document. |
| `FULL_NAME` | Full name doesn't match document. |
| `DOCUMENT_NUMBER` | Document number doesn't match. |
| `PERSONAL_CODE` | Personal code doesn't match. |
| `EXPIRY_DATE` | Expiry date doesn't match. |
| `DATE_OF_BIRTH` | Date of birth doesn't match. |
| `DATE_OF_ISSUE` | Date of issue doesn't match. |
| `NATIONALITY` | Nationality provided doesn't match document. |
| `SEX` | Sex provided doesn't match document. |
| `DOC_INFO_MISMATCH` | Information provided doesn't match the document. |
| `UNDER_AGE` | Client age below the configured minimum age limit. |
| `OVER_AGE` | Client age above the configured maximum age limit. |
| `UNKNOWN_AGE` | Age could not be read and an age limit is configured. |
| `UTILITY_ADDRESS` | Address on utility bill doesn't match provided address. |
| `UTILITY_NAME` | Name on utility bill doesn't match provided name. |
| `EXPIRED_UTILITY_BILL` | Utility bill has expired. |
| `REGISTRY_CENTER_INFO_MISMATCH` | Registry center data doesn't match provided information. |
| `DRIVER_LICENSE_INFO_MISMATCH` | Driver's license data doesn't match provided information. |
Don't see a `fraudTags` or `mismatchTags` value explaining a `SUSPECTED` result? [Contact support via our ticketing portal](https://idenfy-ivs.atlassian.net/servicedesk/customer/portal/1).
***
## Additional Step Statuses
| Status | Description |
| -------------------------------------- | ---------------------------------------------------------------- |
| `INVALID_ADDITIONAL_STEP` | Additional step document was invalid. |
| `ADDITIONAL_STEP_NOT_FOUND` | Additional step was not found. |
| `ADDITIONAL_STEP_INFORMATION_MISMATCH` | Additional step data doesn't match the document. |
| `EXPIRED_ADDITIONAL_STEP_INFORMATION` | The provided additional document has expired. |
| `ADDRESS_UNVERIFIED` | Address verification not performed or address not matched/found. |
| `NOT_SUPPORTED_POA_DOCUMENT_TYPE` | Proof of address document type not supported. |
| `NOT_SUPPORTED_POA_DOCUMENT_COUNTRY` | Proof of address document country not supported. |
| `POA_COUNTRIES_MISMATCH` | Proof of address country doesn't match the expected country. |
| `POA_SCREENSHOT_DETECTED` | Proof of address document appears to be a screenshot. |
## Related topics
- [Shopify](/integrations/shopify.md)
- [Changing Verification Statuses](/guides/dashboard/general/changing-statuses.md)
- [Verification Details](/guides/dashboard/kyc/verification-details.md)
- [List identifications](/api-reference/kyc-verifications/list-identifications.md)
- [Suspected Status](/kyc/suspected-status.md)