The travel rule — the requirement that information about the originator and the beneficiary travels with a payment — was written for wire transfers and extended, in the FATF standards, to virtual assets. The digital-asset legs of cross-border operations are now expected to carry identifying data with them. The practical question is how that information travels when the operation itself is assembled from several rails.

Information, not just value

FATF Recommendation 16 sets out the information that must accompany a transfer. In SUPA's reliance agreement — signed by each participant on joining — that requirement becomes concrete: the agreement fixes the data that must accompany each operation, alongside who is responsible for what, access to KYC documents on request, a minimum standard for KYC, KYB and monitoring regardless of jurisdiction, and the rules governing the agent layer.

That structure matters because digital-asset legs rarely stand alone. A payment may begin as bank money, be netted internally, and settle over a stablecoin rail with the remainder routed elsewhere. If information travels only on the final leg, the record is incomplete. If it travels with the operation from the first layer, the digital-asset leg inherits it.

Where the hub helps

In SUPA's six-layer architecture, legitimacy validation runs before an operation reaches any rail: reliance confirmation, sanctions screening, agent mandate, client-profile fit and network anomaly signals. AI routing then selects a path by cost, settlement time, reliability and regulatory fit. Because the ledger records every movement in double entry, attributed to principal, agent and policy version, the information attached to an operation remains traceable to the parties behind it — including the agent acting for a principal, since agent identities are revocable and never anonymous.

In short

  • The travel rule requires information to move with value.
  • Digital-asset legs should inherit that information, not generate it in isolation.
  • Reliance agreements make the data requirements explicit.
  • Validation should happen once, before routing.
  • The ledger should tie every leg to principal, agent and policy version.

This is general information, not legal, tax or financial advice. For how supervision observes the network, see /institutions/