Required Travel Rule data

Travel Rule messages must include enough information for the beneficiary VASP to identify the originator and beneficiary, assess risk, and meet regulatory obligations. This page summarizes the minimum data requirements in plain language so compliance teams can align collection policies across product, KYC, and monitoring systems.

For the full technical schema and field names, see the Travel Rule data model.

The following summarizes the minimum required data elements for outgoing Travel Rule messages:

• Originator and beneficiary VASP details - Legal entity names and identifiers that allow counterparties to route or validate the message. When creating outgoing Travel Rule messages via CryptoSwift, the originator VASP details are automatically filled in by CryptoSwift, so you do not need to provide this data separately.
• Transaction data - Amount, asset, and blockchain identifiers (transaction hash when available).
• Wallet type - Whether the destination is custodial or self-hosted, which drives whether a VASP-to-VASP message is required.
• Originator and beneficiary data - The names and additional data about the involved end-customers. See the tables below for more details.

• Complete - All mandatory fields are present, even when collected across multiple systems.
• Accurate - Names and identifiers match KYC records and customer-submitted data.
• Consistent - The same identifiers are used across Travel Rule messages, screening tools, and case management systems.

• Ask customers for the beneficiary VASP name when they initiate a withdrawal; it materially improves routing success.
• Capture the wallet type explicitly (custodial vs self-hosted) because it cannot be derived reliably from the address alone.
• Store evidence of data collection and any backfill actions alongside the transaction for audit readiness.

• Travel Rule data model
• Improving data quality
• PII data handling