> ## Documentation Index
> Fetch the complete documentation index at: https://developer.tazapay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Holds

> How Tazapay screens incoming collects and when payments are placed on hold

Any incoming collect is screened against Tazapay's compliance and risk rules. If a payment gets flagged, it is moved to an `on_hold` state.

While a collect is on hold:

* Funds are not yet credited to your balance. A `balance_transaction` object is not created.
* You will not see the collect as `succeeded`.
* You may be reached out for additional information.
  The collect will transition either to `succeeded` (funds credited) or `failed` (funds returned via a [reversal](/collection-accounts/incoming-payments/reversals)).

***

## Subscribing to Compliance Hold Events

You can subscribe to the [`collect.on_hold` webhook event](/api-reference/tazapay-api/collect-webhook#collect-on_hold) to be notified when a collect is placed on a compliance hold.

This is useful for:

* Pausing downstream order fulfillment until the collect clears.
* Alerting your operations team to follow up with the customer.
* Reconciling delayed credits in your books.

***

## See Also

<CardGroup cols={2}>
  <Card title="State Machine" icon="diagram-project" href="/api-reference/tazapay-api/collect-state-machine">
    How a collect moves between states, including holds.
  </Card>

  <Card title="Reversals" icon="rotate-left" href="/collection-accounts/incoming-payments/reversals">
    What happens if a held collect ultimately fails.
  </Card>
</CardGroup>