The travel rule is simple to state and demanding to build. When value moves between institutions, certain information about the parties must travel with it. FATF Recommendation 16 sets the principle, and for digital-asset transfers it is the obligation builders meet first. Implementing it well comes down to what you capture at the point of the operation, and how it is attached to the transfer.

The obligation

The data that must accompany each operation is fixed in advance, not improvised per transaction. In a reliance-based network this is part of the multilateral agreement each participant signs, so the requirement is the same for everyone rather than negotiated corridor by corridor.

What to implement

A practical checklist for builders:

  • Capture originator and beneficiary information at the point the operation is created.
  • Tie every operation to a principal — the person or company legally standing behind it.
  • Register the agent and its mandate, so the executor is never anonymous.
  • Record the policy version in force when the operation ran, so the rule applied is auditable.

Because the ledger attributes each operation to principal, agent and policy version, the travel-rule data is attached to something traceable rather than to a bare message.

Digital assets and agent protocols

Stablecoin transfers and agent protocols both sit at the edge of this obligation. SUPA's rail adapters treat stablecoins and agent protocols (x402, ACP, AP2/UCP, MPP) as paths to be evaluated alongside others. The travel rule does not change because the rail is new; it changes what the adapter must hand over.

That is why the requirement belongs in the architecture rather than in a single integration. If the data is captured at the point of the operation and attached to the ledger entry, every adapter inherits compliance instead of reinventing it. Builders then wire up a rail without re-solving the same question each time.

This article is general information, not legal, tax or financial advice.

In short

  • Recommendation 16 requires information to travel with the operation.
  • Fix the required data once, in the participation agreement.
  • Tie operations to principal, agent, mandate and policy version.
  • New rails inherit the same obligation through their adapters.

Build with the interface at /developers/.