Skip to content

Post-transaction Travel Rule flows

Understand how post-transaction processing works for outgoing crypto transfers.

Teams often ask whether they may broadcast a transfer before the beneficiary VASP has acknowledged the Travel Rule payload. EU Regulation (EU) 2023/1113 requires the specified information to be submitted in advance of, or simultaneously or concurrently with, the transfer. Check the requirements that apply to your VASP and counterparties, including your own release and monitoring controls.

When to choose the post-transaction flow

Use the post-transaction flow when your applicable timing requirements and release controls allow you to dispatch with broadcast, especially if AML and release decisions already run outside CryptoSwift.

Implementation summary

Capture the required Travel Rule data before broadcast. Send the message as the transfer is broadcast and the hash becomes available, then monitor delivery and responses. The API request examples and webhook/polling details live in Outgoing transactions.

In the post-transaction flow, the synchronous response gives you message data and status context. The transfer has already been broadcast when the Travel Rule record is created; final on-chain confirmation need not have occurred.

Regulatory obligations for post-transaction flows

Outgoing transactions: coordinate message and transfer

Article 14(4) of the EU Transfer of Funds Regulation (EU) 2023/1113 requires the specified information to be transmitted "in advance of, or simultaneously or concurrently with, the transfer of crypto-assets." It sets a dispatch timing requirement, without stating that a beneficiary response must precede broadcast. Your operating procedure should cover these points:

  • The required Travel Rule information leaves the originator VASP in the time window required by the applicable rule.
  • The originator VASP records dispatch evidence, including its transaction ID and timing relative to broadcast.
  • Subsequent responses from the beneficiary VASP can arrive later via webhook, and you should route them to compliance teams for review.

The API does not require a beneficiary response before the originator broadcasts a transfer. Your VASP's applicable requirements and risk controls determine whether to wait, release, or escalate; later declines and delivery failures still need review.

Designing a controlled post-transaction flow

Put the regulatory guidance into an operational plan by ensuring that:

  • Outgoing flows capture the Travel Rule payload and dispatch timing alongside the blockchain submission.
  • Your pre-broadcast AML and release controls decide whether to pause a payout. Use the pre-transaction flow if a CryptoSwift risk or Rule Engine result must inform that decision.
  • If you later need CryptoSwift to automate those decisions before funds move, introduce the pre-transaction workflow and the Rule Engine only for the cases that need it.

Further reading

Next steps

See also