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

# Identity checks

> How to create and manage identity and address verification checks for customers.

## Overview

The **Identity checks** page helps your team request, track, and review identity verification for customers. It is commonly used for virtual office onboarding and compliance workflows.

You can use it to:

* Create checks for one customer at a time
* Choose whether the check covers address, identity, or both
* Set accepted document types for manual review
* Add clear instructions customers can follow
* Override default check settings from a plan when needed

When you create a new check, Nexudus opens the check details view automatically so you can review the result, upload documents, and mark the check as verified or rejected.

## How to access

Go to **CRM → Identity checks**.

<Note>
  You can also reach identity checks from related customer and contract screens when handling onboarding.
</Note>

## Check types

When you create a check, select one of these options:

* **Address and identity check**: Requests both checks in one workflow
* **Address check**: Requests proof of address only
* **Identity check**: Requests proof of identity only

The form updates automatically based on your selection.

## Create a new identity check

<Steps>
  <Step title="Start a new check">
    Open **CRM → Identity checks** and create a new record.
  </Step>

  <Step title="Select location and customer">
    Choose the location and the customer who needs verification.
  </Step>

  <Step title="Set a reference">
    Add a reference your team can search later. A default reference is created automatically for new checks.
  </Step>

  <Step title="Choose the check type">
    Select address only, identity only, or both.
  </Step>

  <Step title="Configure provider and documents">
    For each active check section, choose the provider and optionally select accepted document types.
  </Step>

  <Step title="Add customer instructions">
    Add short instructions so customers know what to upload. You can reuse previously saved guidance.
  </Step>

  <Step title="Save and monitor status">
    Save the check. Nexudus opens the check details view for that record so you can review status and documents.
  </Step>
</Steps>

## New check defaults

New checks start with both address and identity sections available so your team can decide what to request. If you switch to address only or identity only, Nexudus clears the unused section fields for you.

Nexudus also creates a reference automatically for new checks so the record is easy to identify and search later.

## Provider behavior

### Address checks

* Address checks use manual review.
* You can define accepted document types or leave the list empty to accept all document types.

### Identity checks

* **Manual**: You choose accepted document types and provide customer instructions.
* **Stripe Identity**: Automated verification flow. Manual document type selection is not shown.

<Info>
  If no document types are selected for manual review, all document types are treated as accepted.
</Info>

<Note>
  If Stripe Identity is selected but the integration is not enabled in your settings, Nexudus shows a warning in the form.
</Note>

## Statuses

The list view groups checks by status so your team can see where each request is in the process:

| Status | Meaning |
| - | - |
| **Requested** | The check has been created and is waiting for customer action |
| **Submitted** | The customer has uploaded documents or completed the request |
| **Verified** | The check has been approved |
| **Rejected** | The check has been rejected |
| **Cancelled** | The check was stopped before completion |

When Stripe Identity is used, the detail view can also show the verification result payload returned by Stripe.

## Reusing customer instructions

For address and manual identity checks, you can save short guidance for customers, then reuse it later.

This is useful when your team wants consistent wording across:

* Plan onboarding defaults
* Customer-specific identity checks
* Ongoing compliance renewals

## Field reference

| Field | Description |
| - | - |
| **Location** | The location that owns this check |
| **Customer** | The customer who must complete verification |
| **Reference** | Internal reference used by operators |
| **Check type** | Address and identity, address only, or identity only |
| **Address provider** | Provider used for address verification |
| **Identity provider** | Manual review or Stripe Identity |
| **Accepted document types** | Document types accepted for manual checks |
| **Additional details for customers** | Extra guidance shown to customers |
| **Status** | Current check state, for example pending, verified, or requires review |
| **Stripe Identity results** | Result details returned by Stripe when the automated provider is used |

## Best practices

* Keep instructions short and specific so customers upload the correct files first time.
* Use one naming pattern for references so your team can filter checks quickly.
* Review pending checks daily to avoid onboarding delays.
* Use manual checks when your process needs local policy review.
* Use Stripe Identity when you want a faster automated verification flow.

## Related features

<CardGroup cols={2}>
  <Card title="Plans" icon="file-contract" href="/platform/billing/plans">
    Configure default onboarding and compliance requirements at plan level.
  </Card>

  <Card title="Virtual Office Onboarding" icon="building" href="/member-portal/virtual-office/onboarding">
    See the customer-facing onboarding flow and compliance steps.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.