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

# Individual Verification

> Individual Person Verification results across six domains: identity, document, biometric, phone, email, and address.

# Individual Verification

Individual (Person Verification) results are returned across six domains: identity, document, biometric, phone, email, and address. Each domain has its own section in the [compliance report](/data-model/compliance-report).

## Identity Verification

The `identity` object provides the overall identity verification decision.

| Field               | Type    | Description                                  |
| ------------------- | ------- | -------------------------------------------- |
| `verified`          | boolean | `true` if identity was successfully verified |
| `decision`          | string  | `Pass`, `Refer`, or `Fail`                   |
| `score`             | number  | Confidence score, 0-100                      |
| `authentication_id` | string  | Provider reference ID for audit purposes     |

### Example

```json theme={null}
{
  "identity": {
    "verified": true,
    "decision": "Pass",
    "score": 95,
    "authentication_id": "auth-xyz789"
  }
}
```

<Note>A `score` above 80 typically indicates a strong match. Scores between 60-80 may result in a `Refer` decision, requiring manual review.</Note>

## Document Verification

The `document` object contains results from identity document scanning, OCR extraction, and tamper analysis.

| Field               | Type    | Description                                                |
| ------------------- | ------- | ---------------------------------------------------------- |
| `verified`          | boolean | `true` if the document passed all authenticity checks      |
| `document_type`     | string  | Type of document: `Passport`, `ID Card`, `Driving Licence` |
| `document_country`  | string  | Issuing country (ISO 3166-1 alpha-2)                       |
| `validation_result` | string  | `PASSED`, `ATTENTION`, or `FAILED`                         |
| `tamper_result`     | string  | `Pass`, `Warning`, or `Failed`                             |
| `extracted_data`    | object  | OCR-extracted fields from the document                     |

### Extracted Data Fields

| Field                            | Type          | Description                                                |
| -------------------------------- | ------------- | ---------------------------------------------------------- |
| `extracted_data.full_name`       | string        | Full name as printed on the document (typically uppercase) |
| `extracted_data.date_of_birth`   | string (date) | Date of birth extracted via OCR                            |
| `extracted_data.expiration_date` | string (date) | Document expiration date                                   |
| `extracted_data.gender`          | string        | `M` or `F`                                                 |

### Example

```json theme={null}
{
  "document": {
    "verified": true,
    "document_type": "Passport",
    "document_country": "GB",
    "validation_result": "PASSED",
    "tamper_result": "Pass",
    "extracted_data": {
      "full_name": "JANE ELIZABETH SMITH",
      "date_of_birth": "1990-06-15",
      "expiration_date": "2030-12-01",
      "gender": "F"
    }
  }
}
```

### Validation Results

| Value       | Meaning                                                                | Action                         |
| ----------- | ---------------------------------------------------------------------- | ------------------------------ |
| `PASSED`    | Document is authentic and legible                                      | Proceed                        |
| `ATTENTION` | Potential issues detected (blurry image, minor discrepancy)            | Manual review recommended      |
| `FAILED`    | Document failed authenticity checks (tampering, expired, unrecognized) | Reject or request resubmission |

### Tamper Results

| Value     | Meaning                                            |
| --------- | -------------------------------------------------- |
| `Pass`    | No signs of digital manipulation                   |
| `Warning` | Possible tampering detected, requires human review |
| `Failed`  | Clear evidence of document tampering               |

## Biometric Verification

The `biometric` object contains liveness detection and face matching results.

| Field                 | Type    | Description                                     |
| --------------------- | ------- | ----------------------------------------------- |
| `liveness_verified`   | boolean | `true` if the user passed liveness detection    |
| `liveness_assessment` | string  | `Live` or `Spoof`                               |
| `liveness_score`      | number  | Liveness confidence, 0-100                      |
| `face_match`          | boolean | `true` if the selfie matches the document photo |
| `face_match_score`    | number  | Face match confidence, 0-100                    |

### Example

```json theme={null}
{
  "biometric": {
    "liveness_verified": true,
    "liveness_assessment": "Live",
    "liveness_score": 98.5,
    "face_match": true,
    "face_match_score": 96.2
  }
}
```

<Warning>A `liveness_score` below 70 or a `face_match_score` below 75 typically triggers a `Refer` decision. A `Spoof` assessment means the system detected a photo-of-photo, screen recording, or mask attempt.</Warning>

## Phone Verification

The `phone_verification` object contains results from phone number validation.

| Field        | Type    | Description                                          |
| ------------ | ------- | ---------------------------------------------------- |
| `verified`   | boolean | `true` if the phone number was successfully verified |
| `carrier`    | string  | Mobile carrier name (e.g., `Vodafone UK`)            |
| `phone_type` | string  | `mobile`, `landline`, or `voip`                      |

### Example

```json theme={null}
{
  "phone_verification": {
    "verified": true,
    "carrier": "Vodafone UK",
    "phone_type": "mobile"
  }
}
```

Phone verification runs when a `phone` field is provided in the request. VoIP numbers may indicate higher risk depending on your compliance policy.

## Email Verification

The `email_verification` object contains results from email address analysis.

| Field         | Type    | Description                                          |
| ------------- | ------- | ---------------------------------------------------- |
| `verified`    | boolean | `true` if the email address is valid and deliverable |
| `risk_score`  | number  | Fraud risk score, 0-100. Lower is better             |
| `deliverable` | boolean | `true` if the email can receive messages             |

### Example

```json theme={null}
{
  "email_verification": {
    "verified": true,
    "risk_score": 12,
    "deliverable": true
  }
}
```

<Tip>A `risk_score` above 70 suggests the email may be disposable, recently created, or associated with known fraud patterns.</Tip>

## Address Verification

The `address_verification` object contains results from address validation.

| Field         | Type    | Description                              |
| ------------- | ------- | ---------------------------------------- |
| `verified`    | boolean | `true` if the address could be validated |
| `match_level` | string  | `full`, `partial`, or `none`             |

### Example

```json theme={null}
{
  "address_verification": {
    "verified": true,
    "match_level": "full"
  }
}
```

### Match Levels

| Value     | Meaning                                                                                     |
| --------- | ------------------------------------------------------------------------------------------- |
| `full`    | Complete address match against reference databases                                          |
| `partial` | Street or city matched, but some components (e.g., apartment number) could not be confirmed |
| `none`    | Address could not be verified against any reference source                                  |

## Decision Matrix

Combine results across domains to determine your action:

| Identity | Document  | Biometric | Screening | Recommended Action             |
| -------- | --------- | --------- | --------- | ------------------------------ |
| Pass     | Pass      | Pass      | No Hit    | Auto-approve                   |
| Pass     | Attention | Pass      | No Hit    | Manual document review         |
| Pass     | Pass      | Pass      | Hit       | Manual screening review        |
| Fail     | Any       | Any       | Any       | Reject or request resubmission |

<Warning>Only auto-approve when all four domains return clean results. Any `Attention`, `Warning`, or `Hit` flag should trigger manual review.</Warning>