# Handle webhooks

Before Checkout.com onboards your sub-entities, you must configure your [webhook server](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks/configure-your-webhook-server.md) to receive all necessary notifications throughout the onboarding process.

Subscribe to the following webhooks:

| Webhook | Description |
| --- | --- |
| [Sub-entity created](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/sub_entity_created.md) | Sent when a sub-entity is successfully created. |
| [Payment instrument verification passed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_instrument_verification_passed.md) | Sent after a payment instrument passes verification. |
| [Payment instrument verification failed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payment_instrument_verification_failed.md) | Sent after a payment instrument fails verification. |
| [Full DD passed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/full_dd_passed.md) | Sent after a sub-entity passes its full due diligence checks. |
| [Full DD failed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/full_dd_failed.md) | Sent after a sub-entity fails its full due diligence checks. |
| [Payouts enabled](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payouts_enabled.md) | Sent when payout capabilities become enabled for a sub-entity. |
| [Payouts disabled](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payouts_disabled.md) | Sent when payout capabilities become disabled for a sub-entity. |
| [Payments enabled](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payments_enabled.md) | Sent after the sub-entity passes the CSS checks (VMSS and Match) and its payment capabilities become enabled. |
| [Payments disabled](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/payments_disabled.md) | Sent when payment capabilities become disabled for a sub-entity. |
| [Status changed](https://www.checkout.com/docs/developer-resources/event-notifications/event-types/status_changed.md) | Sent whenever a sub-entity's status changes. |

The sub-entity status also changes as the process progresses.

> **Information**
>
> For all possible statuses, see [Sub-entity status](https://www.checkout.com/docs/platforms/for-saas/manage-sub-entities/sub-entity-status.md).

The following graph shows you all the possible status updates as your sub-entity advances in the onboarding process:

![Full onboarding flow showing pending, active, rejected, requirements_due, verified, and unverified statuses](https://www.checkout.com/docs/NAS/Platforms/saas-platforms-onboarding-webhooks.svg)

> **Information**
>
> If any required information is updated later, Checkout.com runs the verification again.
> If any subsequent checks fail, we send the Full DD failed, Payments disabled, and Payouts disabled webhooks.