# Onboard sub-entities

All sellers that process payments with Checkout.com via your platform are represented as sub-entities.

For onboarding, a sub-entity must provide Checkout.com with specific information for compliance and verification purposes.

---

## Onboarding process

The process for onboarding a sub-entity is as follows:

1. [Configure your webhook server](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks/configure-your-webhook-server.md) and subscribe to the [relevant events](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/handle-webhooks.md). This ensures you and your sub-entity receive all necessary notifications throughout onboarding.
2. [Collect verification information](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/collect-verification-information.md) by [using the Platforms API](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/submit-application.md).
3. Add the required [supporting documents](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/add-supporting-documents.md).
4. [Add a payment instrument](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/add-payment-instrument.md) for each of the sub-entity's holding currencies. This step triggers the verification checks.
5. Checkout.com conducts asynchronous verification checks on the sub-entity.

   - You can track the [status](https://www.checkout.com/docs/platforms/for-saas/manage-sub-entities/sub-entity-status.md) of your sub-entities through the onboarding process in the Dashboard or via API responses.
   - We also send [webhooks](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/handle-webhooks.md) about the outcome of the verification checks and any status changes.

   > **Note**
   >
   > The verification timelines depend on the region in which your platform operates and the sub-entity information you submit. For more details, see the [Verification timelines](#verification-timelines) section.

6. Check the outcome of the verification checks.

   - If verification is successful, the sub-entity's capabilities are enabled.

   - If verification fails, we may request additional information to conduct the checks again.

### Verification timelines

For platforms operating in the United States, Checkout.com offers instant onboarding. This enables sub-entities to be verified with minimal upfront information and receive an immediate onboarding decision.

If a sub-entity cannot be automatically verified, we may request additional information and attempt verification again. After information required from sub-entities is submitted, we will retry the verification process.

For platforms operating outside the United States, sub-entity verification may take longer and can delay the onboarding outcome. If you have any concerns, contact your account manager or [request support](https://dashboard.checkout.com/support/new).

- [Collect verification information](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/collect-verification-information.md): Learn about the information required for Checkout.com to verify sub-entities.
- [Handle webhooks](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/handle-webhooks.md): Learn about the webhooks you receive when onboarding sub-entities to your platform.
- [Submit application](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/submit-application.md): Submit an onboarding application using the Platforms API.
- [Add supporting documents](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/add-supporting-documents.md): Add supporting documents using our Platforms API.
- [Add payment instrument](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/add-payment-instrument.md): Learn how to add a payment instrument.
- [Simulate onboarding scenarios](https://www.checkout.com/docs/platforms/for-saas/onboard-sub-entities/simulate-onboarding-scenarios.md): Simulate different onboarding scenarios using the Onboarding simulator API.