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

# orchestration.status_details.travel_rule_info_required

> Webhook triggered when an orchestration enters the travel_rule_info_required sub-state

Triggered when an orchestration moves into the `travel_rule_info_required` sub-state. This occurs when the orchestration's crypto withdrawal is rejected because the destination address has no Travel Rule information.

`awaiting_action_from` will be `AWAITING_ACTION_FROM_CLIENT`. The orchestration stays in `PROCESSING` and retries the withdrawal automatically.

To resolve, call [Put Crypto Destination Address](https://docs.paxos.com/api-reference/endpoints/crypto-destination-addresses/put-crypto-destination-address.md) with `travelrule_metadata` populated for the destination address. See [Collecting Travel Rule Information](https://docs.paxos.com/guides/travel-rule/collection-patterns.md) for the fields to collect. The next retry creates the withdrawal, and `status_details` moves to `destination_transfer_in_progress`.

This event can fire more than once for the same orchestration. If a retry fails for a different reason, `status_details` returns to `destination_transfer_in_progress`, and a later Travel Rule rejection sets `travel_rule_info_required` again. Make handlers idempotent.

> [!NOTE]
>
> Webhook payloads contain only event metadata. Use the [Get Event API](https://docs.paxos.com/api-reference/endpoints/events/get-event.md) with the event ID to retrieve full details.

## Event Object Structure

The Get Event API returns an [`orchestration_status_details_change`](https://docs.paxos.com/api-reference/events/orchestration-status-details-object) object, which includes `status_details.travel_rule_info_required`.

> See the [Webhook Integration Guide](https://docs.paxos.com/guides/developer/orchestrations/webhook-integration.md) to understand when to use granular `status_details` events versus the high-level `orchestration.processing` webhook.


## OpenAPI

````yaml webhooks-openapi.json webhook orchestration.status_details.travel_rule_info_required
openapi: 3.1.0
info:
  title: Paxos Webhooks
  version: '2.0'
  description: >-
    Webhooks allow you to register endpoints to receive asynchronous events from
    the Paxos Platform. These webhooks are triggered when specific events occur
    in the system, enabling real-time notifications for your application.


    **Important**: Webhook payloads contain only the event metadata. To retrieve
    the full event object details, use the [Get
    Event](/api-reference/events/get-event) REST API endpoint with the event ID
    from the webhook payload.
  x-logo:
    url: /docs/paxos.svg
    backgroundColor: '#FFFFFF'
    altText: Paxos logo
servers: []
security: []
paths: {}

````