# Sub-entity status

Through its lifecycle, a sub-entity can have different statuses that define its payment capabilities.

You can check the status of a sub-entity in the responses of the following API calls:

- [Onboard a sub-entity](https://api-reference.checkout.com/tag/Platforms/#operation/onboardEntity)
- [Retrieve a sub-entity's details](https://api-reference.checkout.com/tag/Platforms/#operation/getEntityDetails)
- [Update a sub-entity's details](https://api-reference.checkout.com/tag/Platforms/#operation/updateEntityDetails)

If you configure your [webhook server](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks/configure-your-webhook-server.md), you receive a [Status changed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/status_changed.md) webhook.

A sub-entity can have one of the following statuses:

- Draft
- In review (`pending` in the API)
- Active
- Restricted
- Rejected
- Inactive

---

## Draft

If the sub-entity has begun but not submitted its onboarding application, its status displays as `draft`. This means that the onboarding application is incomplete and verification checks haven't been triggered.

---

## In review

We start verification checks only after we have all of the [required information](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/collect-verification-information.md). After we start the verification process, the Dashboard displays the sub-entity's status as _In review_, and API responses and webhooks return `pending`.

To retrieve the outstanding requirements and submit the information we need, see [Resolve pending requirements](https://www.checkout.com/docs/platforms/for-saas/manage-sub-entities/resolve-pending-requirements.md).

> **Information**
>
> The outcome of the verification checks may affect the sub-entity's payment capabilities.

---

## Active

If the sub-entity passes verification checks, its status displays as `active` in API responses and webhooks, and its payments or payouts capabilities are enabled.

> **Note**
>
> Updating a sub-entity's information or adding new products after a sub-entity has been set to active, may require us to run additional verification checks.

---

## Restricted

If the sub-entity's payment capabilities are restricted, its status displays as `restricted`.

The sub-entity cannot process payments or payouts.

---

## Rejected

If the sub-entity fails verification checks, its status displays as `rejected` in API responses and webhooks.

The sub-entity cannot resume onboarding. To challenge the decision, [request support](https://dashboard.checkout.com/support/new).

If you attempt to update a rejected sub-entity via the API, you receive a `442` response with the error code `status_invalid`.

---

## Inactive

If the sub-entity is inactive and no longer able to process payments, its status displays as `inactive` in API responses and webhooks.

This status can be due to offboarding or the termination of its contract with your platform.

The `status_reason` field displays the reason for this status.

---

## Related topics

**[Update a sub-entity](https://www.checkout.com/docs/platforms/for-saas/manage-sub-entities/update-a-sub-entity.md)**

Learn how a sub-entity can be updated on your platform.

**[Handle webhooks](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/handle-webhooks.md)**

Learn about the different webhooks you receive when onboarding sub-entities.

**[Resolve pending requirements](https://www.checkout.com/docs/platforms/for-saas/manage-sub-entities/resolve-pending-requirements.md)**

Learn how to list, review, and resolve compliance requirements on your sub-entities.