Sub-entity status
Beta
Last updated: October 7, 2026
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:
If you configure your webhook server, you receive a Status changed webhook.
A sub-entity can have one of the following statuses:
- Draft
- In review (
pendingin the API) - Active
- Restricted
- Rejected
- Inactive
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.
We start verification checks only after we have all of the required information. 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.
Information
The outcome of the verification checks may affect the sub-entity's payment capabilities.
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.
If the sub-entity's payment capabilities are restricted, its status displays as restricted.
The sub-entity cannot process payments or payouts.
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.
If you attempt to update a rejected sub-entity via the API, you receive a 442 response with the error code status_invalid.
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.