Rollout & Enforcement

Availability dates, enforcement timeline, and migration guidance.

Timeline

Phase	Date	What happens
Available	Mid-July 2026	Travel Rule fields available on PUT /v2/transfer/crypto-destination-address. GET /v2/travelrule/vasps directory endpoint live. Fields are accepted and stored but not enforced — existing flows continue to work without Travel Rule metadata.
Migration window	Mid-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 /transfer/crypto-withdrawals is no longer accepted.

What changes at enforcement

• POST /transfer/crypto-withdrawals — the beneficiary field is removed. Travel Rule data must be on the saved destination address.
• POST /transfer/fees/crypto-withdrawal — identity_id is now used to resolve the destination address and enforce Travel Rule requirements at fee-quote time.
• PUT /transfer/crypto-destination-address — travelrule_metadata is required for addresses used in above-threshold transfers.
• POST /orchestration/orchestrations and POST /orchestration/rules — destination is now addressed by (crypto_network, address) or identity_id; address_id / crypto_address_id are deprecated.

Recommended migration steps

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

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

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

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