> ## 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.

# Rollout & Enforcement

> Availability dates, enforcement timeline, and migration guidance.

## Timeline

| Phase                | Date                  | What happens                                                                                                                                                                                                                                                                                                                                                                            |
| -------------------- | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Available**        | July 2026             | Travel Rule fields available on [`PUT /v2/transfer/crypto-destination-address`](/api-reference/endpoints/crypto-destination-addresses/put-crypto-destination-address). [`GET /v2/travelrule/vasps`](/api-reference/endpoints/vasps/list-vasps) directory endpoint live. Fields are accepted and stored but not enforced — existing flows continue to work without Travel Rule metadata. |
| **Migration window** | July → Nov 30, 2026   | \~4.5 months for partners to update integrations. Recommended: complete integration testing in sandbox by end of September 2026 to leave buffer for production rollout.                                                                                                                                                                                                                 |
| **Enforced**         | **November 30, 2026** | Above-threshold withdrawals and orchestrations to addresses without valid Travel Rule metadata return `403 Travel Rule Information Required`. The legacy `beneficiary` field on `POST /v2/transfer/crypto-withdrawals` is no longer accepted.                                                                                                                                           |

## What changes at enforcement

* [**`POST /v2/transfer/crypto-withdrawals`**](/api-reference/endpoints/crypto-withdrawals/create-crypto-withdrawal) — the `beneficiary` field is removed. Travel Rule data must be on the saved destination address.
* [**`POST /v2/transfer/fees/crypto-withdrawal`**](/api-reference/endpoints/fees/create-crypto-withdrawal-fee) — `identity_id` is now used to resolve the destination address and enforce Travel Rule requirements at fee-quote time.
* [**`PUT /v2/transfer/crypto-destination-address`**](/api-reference/endpoints/crypto-destination-addresses/put-crypto-destination-address) — `travelrule_metadata` is required for addresses used in above-threshold transfers.
* [**`POST /v2/orchestration/orchestrations`**](/api-reference/endpoints/orchestration/create-orchestration) and [**`POST /v2/orchestration/rules`**](/api-reference/endpoints/orchestration-rules/create-orchestration-rule) — the crypto destination is specified by `address` + `network` (pass `identity_id` on the request for third-party scoping); the deprecated `crypto_address_id` / `address_id` fields should no longer be used.

## Recommended migration steps

<Steps>
  <Step title="Sandbox: add Travel Rule metadata collection to your UI">
    Integrate the VASP directory lookup and beneficiary collection form into your address-save flow. Test against the sandbox environment during the migration window.
  </Step>

  <Step title="Sandbox: backfill existing saved addresses">
    For addresses already saved in your system, decide whether to re-prompt end users or bulk-update with best-effort data. Addresses without metadata will be blocked at enforcement.
  </Step>

  <Step title="Production: roll out before October 2026">
    Target production rollout by end of September 2026. This gives a one-month buffer before enforcement to catch edge cases.
  </Step>

  <Step title="November 30, 2026: enforcement begins">
    Above-threshold transfers to addresses without Travel Rule metadata are rejected. Monitor for `403 Travel Rule Information Required` errors and ensure your retry flow (Pattern B) is wired up if used.
  </Step>
</Steps>