---
title: "Simulate an account holder's enrollment review"
method: POST
path: "/v1/simulate/account_holders/enrollment_review"
tags: ["Account Holder"]
---

# Simulate an account holder's enrollment review

`POST /v1/simulate/account_holders/enrollment_review`

Simulates an enrollment review for an account holder. This endpoint is only applicable for workflows that may required intervention such as `KYB_BASIC`.

## Request body

- SimulateEnrollmentReviewRequest
  - `account_holder_token` string — The account holder which to perform the simulation upon.
  - `status` 'ACCEPTED' | 'REJECTED' | 'PENDING_REVIEW' — An account holder's status for use within the simulation.
  - `status_reasons` string[] — Status reason that will be associated with the simulated account holder status. Only required for a `REJECTED` status.

## Response `200`

OK

- AccountHolderResponse
  - `token` string, uuid — Globally unique identifier for the account holder.
  - `account_token` string, uuid — Globally unique identifier for the account.
  - `business_account_token` string, uuid, nullable — Only applicable for customers using the KYC-Exempt workflow to enroll authorized users of businesses. Pass the account_token of the enrolled business associated with the AUTHORIZED_USER in this field.
  - `created` string, date-time — Timestamp of when the account holder was created.
  - `exemption_type` 'AUTHORIZED_USER' | 'PREPAID_CARD_USER', nullable — The type of KYC exemption for a KYC-Exempt Account Holder. `null` if the account holder is not KYC-Exempt.
  - `external_id` string, nullable — Customer-provided token that indicates a relationship with an object outside of the Lithic ecosystem.
  - `user_type` 'BUSINESS' | 'INDIVIDUAL' — The type of Account Holder. If the type is "INDIVIDUAL", the "individual" attribute will be present. If the type is "BUSINESS" then the "business_entity", "control_person", "beneficial_owner_individuals", "naics_code", "nature_of_business", and "website_url" attributes will be present.
  - `verification_application` VerificationApplication — Represents the status of an identity verification application for an account holder
    - `created` string, date-time, required — Timestamp of when the application was created.
    - `status` 'ACCEPTED' | 'PENDING_DOCUMENT' | 'PENDING_RESUBMIT' | 'REJECTED', required — Enrollment status for KYC/KYB
    - `status_reasons` StatusReasons[], required — Reason for the evaluation status.
    - `updated` string, date-time, required — Timestamp of when the application was last updated.
    - `ky_passed_at` string, date-time — Timestamp of when the application passed the verification process. Only present if `status` is `ACCEPTED`
  - `individual` Individual
    - `address` Address
      - `address1` string, required — Valid deliverable address (no PO boxes).
      - `address2` string — Unit or apartment number (if applicable).
      - `city` string, required — Name of city.
      - `country` string, required — Valid country code. Only USA is currently supported, entered in uppercase ISO 3166-1 alpha-3 three-character format.
      - `postal_code` string, required — Valid postal code. Only USA ZIP codes are currently supported, entered as a five-digit ZIP or nine-digit ZIP+4.
      - `state` string, required — Valid state code. Only USA state codes are currently supported, entered in uppercase ISO 3166-2 two-character format.
    - `dob` string — Individual's date of birth, as an RFC 3339 date.
    - `email` string — Individual's email address. If utilizing Lithic for chargeback processing, this customer email address may be used to communicate dispute status and resolution.
    - `first_name` string — Individual's first name, as it appears on government-issued identity documents.
    - `last_name` string — Individual's last name, as it appears on government-issued identity documents.
    - `phone_number` string — Individual's phone number, entered in E.164 format.
    - `government_id` string — Government-issued identification number (required for identity verification and compliance with banking regulations). Social Security Numbers (SSN) and Individual Taxpayer Identification Numbers (ITIN) are currently supported, entered as full nine-digits, with or without hyphens
  - `business_entity` KybBusinessEntity
    - `address` Address, required
      - `address1` string, required — Valid deliverable address (no PO boxes).
      - `address2` string — Unit or apartment number (if applicable).
      - `city` string, required — Name of city.
      - `country` string, required — Valid country code. Only USA is currently supported, entered in uppercase ISO 3166-1 alpha-3 three-character format.
      - `postal_code` string, required — Valid postal code. Only USA ZIP codes are currently supported, entered as a five-digit ZIP or nine-digit ZIP+4.
      - `state` string, required — Valid state code. Only USA state codes are currently supported, entered in uppercase ISO 3166-2 two-character format.
    - `dba_business_name` string — Any name that the business operates under that is not its legal business name (if applicable).
    - `government_id` string, required — Government-issued identification number. US Federal Employer Identification Numbers (EIN) are currently supported, entered as full nine-digits, with or without hyphens.
    - `legal_business_name` string, required — Legal (formal) business name.
    - `parent_company` string, nullable — Parent company name (if applicable).
    - `phone_numbers` string[], required — One or more of the business's phone number(s), entered as a list in E.164 format.
  - `beneficial_owner_individuals` Individual[] — Only present when user_type == "BUSINESS". You must submit a list of all direct and indirect individuals with 25% or more ownership in the company. A maximum of 4 beneficial owners can be submitted. If no individual owns 25% of the company you do not need to send beneficial owner information. See [FinCEN requirements](https://www.fincen.gov/sites/default/files/shared/CDD_Rev6.7_Sept_2017_Certificate.pdf) (Section I) for more background on individuals that should be included.
    - `address` Address
      - `address1` string, required — Valid deliverable address (no PO boxes).
      - `address2` string — Unit or apartment number (if applicable).
      - `city` string, required — Name of city.
      - `country` string, required — Valid country code. Only USA is currently supported, entered in uppercase ISO 3166-1 alpha-3 three-character format.
      - `postal_code` string, required — Valid postal code. Only USA ZIP codes are currently supported, entered as a five-digit ZIP or nine-digit ZIP+4.
      - `state` string, required — Valid state code. Only USA state codes are currently supported, entered in uppercase ISO 3166-2 two-character format.
    - `dob` string — Individual's date of birth, as an RFC 3339 date.
    - `email` string — Individual's email address. If utilizing Lithic for chargeback processing, this customer email address may be used to communicate dispute status and resolution.
    - `first_name` string — Individual's first name, as it appears on government-issued identity documents.
    - `last_name` string — Individual's last name, as it appears on government-issued identity documents.
    - `phone_number` string — Individual's phone number, entered in E.164 format.
    - `government_id` string — Government-issued identification number (required for identity verification and compliance with banking regulations). Social Security Numbers (SSN) and Individual Taxpayer Identification Numbers (ITIN) are currently supported, entered as full nine-digits, with or without hyphens
  - `control_person` Individual
    - `address` Address
      - `address1` string, required — Valid deliverable address (no PO boxes).
      - `address2` string — Unit or apartment number (if applicable).
      - `city` string, required — Name of city.
      - `country` string, required — Valid country code. Only USA is currently supported, entered in uppercase ISO 3166-1 alpha-3 three-character format.
      - `postal_code` string, required — Valid postal code. Only USA ZIP codes are currently supported, entered as a five-digit ZIP or nine-digit ZIP+4.
      - `state` string, required — Valid state code. Only USA state codes are currently supported, entered in uppercase ISO 3166-2 two-character format.
    - `dob` string — Individual's date of birth, as an RFC 3339 date.
    - `email` string — Individual's email address. If utilizing Lithic for chargeback processing, this customer email address may be used to communicate dispute status and resolution.
    - `first_name` string — Individual's first name, as it appears on government-issued identity documents.
    - `last_name` string — Individual's last name, as it appears on government-issued identity documents.
    - `phone_number` string — Individual's phone number, entered in E.164 format.
    - `government_id` string — Government-issued identification number (required for identity verification and compliance with banking regulations). Social Security Numbers (SSN) and Individual Taxpayer Identification Numbers (ITIN) are currently supported, entered as full nine-digits, with or without hyphens
  - `naics_code` string, nullable — Only present when user_type == "BUSINESS". 6-digit North American Industry Classification System (NAICS) code for the business.
  - `nature_of_business` string — Only present when user_type == "BUSINESS". User-submitted description of the business.
  - `website_url` string — Only present when user_type == "BUSINESS". Business's primary website.
  - `email` string — (Deprecated. Use control_person.email when user_type == "BUSINESS". Use individual.phone_number when user_type == "INDIVIDUAL".) Primary email of Account Holder.
  - `phone_number` string — (Deprecated. Use control_person.phone_number when user_type == "BUSINESS". Use individual.phone_number when user_type == "INDIVIDUAL".) Primary phone of Account Holder, entered in E.164 format.
  - `status` 'ACCEPTED' | 'PENDING_DOCUMENT' | 'PENDING_RESUBMIT' | 'REJECTED' — Enrollment status for KYC/KYB
  - `status_reasons` StatusReasons[] — (Deprecated. Use verification_application.status_reasons) Reason for the evaluation status.
  - `required_documents` RequiredDocument[] — Only present for "KYB_BASIC" and "KYC_ADVANCED" workflows. A list of documents required for the account holder to be approved.
    - `entity_token` string, uuid, required — Globally unique identifier for an entity.
    - `valid_documents` string[], required — A list of valid documents that will satisfy the KYC requirements for the specified entity.
    - `status_reasons` string[], required — Provides the status reasons that will be satisfied by providing one of the valid documents.

## Other responses

- `400` — A parameter in the query given in the request does not match the valid queries for the endpoint.
- `401` — | | | |---|---| | User has not been authenticated | Invalid or missing API key | | API key is not active | The API key used is no longer active | | Could not find API key | The API key provided is not associated with any user | | Please provide API key in Authorization header | The Authorization header is not in the request | | Please provide API key in the form Authorization: [api-key] | The Authorization header is not formatted properly | | Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Reach out at [lithic.com/contact](https://lithic.com/contact) | | Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege | Reach out at [lithic.com/contact](https://lithic.com/contact) |
- `404` — The specified resource was not found.
- `409` — The request could not be completed due to a conflict with the current state of the target resource.
- `429` — Client has exceeded the number of allowed requests in a given time period. | | | |---|---| | Rate limited, too many requests per second | User has exceeded their per second rate limit | | Rate limited, reached daily limit | User has exceeded their daily rate limit | | Rate limited, too many keys tried | One IP has queried too many different API keys |

---

[API](https://skmtc.net/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.net/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/revisions/53ab5d4e2adb/schema)