Timeline
What changes at enforcement
POST /v2/transfer/crypto-withdrawals— thebeneficiaryfield is removed. Travel Rule data must be on the saved destination address.POST /v2/transfer/fees/crypto-withdrawal—identity_idis now used to resolve the destination address and enforce Travel Rule requirements at fee-quote time.PUT /v2/transfer/crypto-destination-address—travelrule_metadatais required for addresses used in above-threshold transfers.POST /v2/orchestration/orchestrationsandPOST /v2/orchestration/rules— the crypto destination is specified byaddress+network(passidentity_idon the request for third-party scoping); the deprecatedcrypto_address_id/address_idfields should no longer be used.
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.