Skip to content
Last updated

Compliance

The Travel Rule Protocol (TRP) helps Virtual Asset Service Providers (VASPs) comply with global regulatory requirements for transmitting customer information during virtual asset transfers.

This page provides an overview of the key regulatory standards and explains how TRP ensures full compliance while keeping integration simple and secure.

What is the Travel Rule?

The Travel Rule is a regulatory requirement defined by:

  • FATF Recommendation 16
  • FinCEN Funds Travel Rule
  • EU Transfer of Funds Regulation (TFR)
  • UK Travel Rule Regulations
  • Singapore PSA Notice PSN02
  • Other jurisdictional AML/CFT frameworks

The rule mandates that VASPs must collect, verify, and transmit originator and beneficiary information when processing virtual asset transfers.

TRP Compliance Features

TRP is designed to simplify and automate Travel Rule compliance.
The platform ensures that all required information is exchanged securely between VASPs.

✔ Required Information Exchange

TRP supports the transmission of all mandatory FATF R.16 attributes, including:

  • Originator

    • firstName (required)
    • lastName (required)
    • walletAddress (required)
    • accountNumber / nationalId (optional)
    • residential information (optional)

  • Beneficiary

    • firstName (required)
    • lastName (required)
    • walletAddress (required)
    • externalId (optional, for VASP internal tracking)

All data is structured according to the IVMS101 standard.

Secure Inter-VASP Data Exchange

TRP uses encrypted, tamper-resistant communication between VASPs:

  • End-to-end encryption of all identity data
  • Zero-knowledge approach for wallet attribution
  • Identity exchange only after VASP–VASP validation
  • No sharing of unnecessary personal data
  • Strict payload validation to avoid incomplete or non-compliant transfers

Travel Address & Identity Binding

TRP generates a Travel Address, a secure token that binds:

  • beneficiary identity
  • wallet address
  • externalId (optional)
  • VASP identity

This allows the originator VASP to initiate a Travel Rule transfer without handling raw beneficiary PII at the first step.

Status Callbacks for Full Transparency

To meet regulatory reporting requirements, TRP:

  • notifies the originator VASP of all transfer status changes
  • provides APPROVED, REJECTED, and error details
  • includes a callback URL for submitting the blockchain txId

This ensures traceability and satisfies AML/CFT audit requirements.

Audit Logging

TRP maintains encrypted records of:

  • data exchanged between VASPs
  • timestamps
  • transfer statuses
  • txId linkage
  • error or rejection causes

These logs support internal audits and regulatory inspections.

Jurisdictional Coverage

TRP is designed to support compliance across all major markets:

  • United States
  • European Union
  • United Kingdom
  • Singapore
  • Hong Kong
  • Australia
  • Switzerland
  • UAE
  • and others following FATF R.16

Local differences (thresholds, optional fields, reporting rules) can be handled at the VASP level while TRP ensures the core compliance workflow.

Summary

TRP provides VASPs with:

  • Fully automated Travel Rule compliance
  • IVMS101-compatible identity exchange
  • Secure Travel Address generation
  • Mandatory info validation
  • Complete traceability & audit support
  • Seamless integration with existing KYC/AML systems

By integrating TRP, your VASP meets global Travel Rule requirements with minimal engineering overhead.

Previous page
Next page