Crypto Travel Rule in Switzerland: FATF Compliance for Digital Asset Transfers

The travel rule represents one of the most operationally complex compliance requirements facing digital asset service providers in Switzerland. Originating from the Financial Action Task Force (FATF) and implemented through Swiss anti-money laundering legislation, the rule requires virtual asset service providers (VASPs) to share identifying information about the originator and beneficiary of digital asset transfers. While conceptually straightforward, implementing this requirement for blockchain-based transfers presents unique technical and operational challenges.

What Is the Travel Rule?

The travel rule — formally FATF Recommendation 16 — requires financial institutions to include originator and beneficiary information with funds transfers. Originally designed for wire transfers in traditional banking, the FATF extended this requirement to virtual asset transfers in 2019, recognising that digital asset transfers present similar money laundering and terrorist financing risks.

For Swiss digital asset businesses, the travel rule is implemented through the Anti-Money Laundering Act (AMLA) and supplemented by FINMA guidance. The rule applies to all VASPs operating in Switzerland, including exchanges, custodial wallet providers, and OTC desks.

Swiss Implementation

Threshold

Under Swiss implementation, the travel rule applies to digital asset transfers exceeding CHF 1,000. This threshold is lower than the EUR 1,000 threshold adopted by the European Union under MiCA, reflecting Switzerland’s historically conservative approach to AML thresholds.

Transfers below the CHF 1,000 threshold are not exempt from all compliance — they remain subject to general transaction monitoring obligations and may trigger enhanced scrutiny if part of a suspicious pattern.

Required Information

For qualifying transfers, the originating VASP must transmit the following information to the beneficiary VASP:

Originator information:

• Full name (or entity name for legal persons)
• Account number or wallet address
• Address, date of birth, or national identity number (at least one)

Beneficiary information:

• Full name (or entity name)
• Account number or wallet address

Timing

The required information must be transmitted immediately and securely to the beneficiary VASP, either simultaneously with the blockchain transfer or through a separate secure channel. The beneficiary VASP must not make the transferred funds available to the recipient until it has received and verified the required information.

Technical Implementation Challenges

Identifying the Counterparty VASP

The first challenge in travel rule compliance is determining whether the counterparty address is controlled by another VASP. When a customer initiates a withdrawal to an external address, the originating VASP must establish:

1. Is the receiving address controlled by a VASP or is it a self-hosted wallet?
2. If it is a VASP, which VASP controls it?
3. What travel rule protocol does that VASP support?

This identification process may involve:

• Database lookups against known VASP address registries
• Customer attestation (declaring whether the receiving address is at a VASP or self-hosted)
• Blockchain analytics to identify exchange-controlled address clusters

Secure Information Transfer

Once the counterparty VASP is identified, the travel rule information must be transmitted through a secure channel. The challenge is that no single, universally adopted protocol exists for this purpose. Multiple competing solutions have emerged, creating interoperability challenges.

Self-Hosted Wallets

Transfers to self-hosted wallets (also known as unhosted or personal wallets) present a particular compliance challenge. There is no counterparty VASP to receive travel rule information. Swiss VASPs must instead:

• Verify that the customer controls the receiving address through wallet verification procedures
• Conduct risk assessment on the transfer based on available information
• Apply enhanced due diligence for higher-risk transfers
• Maintain records of the verification process

Travel Rule Solutions

Notabene

Notabene has emerged as one of the leading travel rule compliance platforms, providing a network for VASP-to-VASP information exchange. The platform supports multiple travel rule protocols and provides tools for counterparty VASP identification, information exchange, and compliance workflow management.

For Swiss VASPs, Notabene offers specific support for Swiss regulatory requirements, including CHF 1,000 threshold implementation and FINMA-aligned workflow configurations.

OpenVASP

OpenVASP is an open-source protocol for travel rule compliance developed with significant Swiss involvement. The protocol defines a peer-to-peer messaging standard for VASP-to-VASP communication, using a decentralised registry for VASP discovery and public key distribution.

The open-source nature of OpenVASP provides transparency and avoids vendor lock-in, making it attractive to Swiss VASPs that value these characteristics. Several Swiss digital asset businesses have adopted OpenVASP as their primary travel rule protocol.

TRISA

The Travel Rule Information Sharing Architecture (TRISA) provides a compliance network based on certificate authorities and mTLS (mutual transport layer security) connections. VASPs obtain digital certificates from TRISA directory service and use these for secure peer-to-peer communication.

Sygna Bridge

Sygna Bridge offers a travel rule compliance solution with particular strength in the Asian market. Swiss VASPs with significant Asian counterparty exposure may use Sygna Bridge to complement other solutions.

Interoperability

The existence of multiple travel rule protocols creates interoperability challenges. A Swiss VASP using OpenVASP may need to communicate with a counterparty using TRISA or Notabene. Solutions to this challenge include:

• Multi-protocol support — Platforms that support multiple travel rule protocols, translating between them as needed
• Protocol bridging — Gateway services that connect different travel rule networks
• Standardisation efforts — Industry initiatives to develop common data formats and messaging standards

Compliance Workflows

Outgoing Transfers

When a Swiss VASP customer initiates a transfer:

1. Threshold check — Determine whether the transfer exceeds CHF 1,000
2. Counterparty identification — Establish whether the receiving address is at a VASP or self-hosted
3. VASP discovery — If the counterparty is a VASP, identify it and determine its travel rule capabilities
4. Information assembly — Compile the required originator and beneficiary information
5. Information transmission — Send the travel rule data through the appropriate protocol
6. Confirmation — Verify receipt and acceptance by the beneficiary VASP
7. Transaction execution — Broadcast the blockchain transaction
8. Record keeping — Maintain complete records of the compliance process

Incoming Transfers

When a Swiss VASP receives a transfer:

1. Travel rule data receipt — Receive and validate incoming travel rule information
2. Threshold check — Determine whether the transfer exceeds CHF 1,000
3. Information verification — Verify the accuracy and completeness of received information
4. Sanctions screening — Screen originator information against sanctions lists
5. Risk assessment — Evaluate the transfer based on originator profile and transaction characteristics
6. Fund release — Make funds available to the beneficiary only after satisfactory compliance checks
7. Record keeping — Maintain complete records

Rejected Transfers

If a beneficiary VASP cannot verify received travel rule information or identifies sanctions or compliance concerns, the transfer must be rejected or held pending resolution. Clear communication protocols between VASPs are essential for handling rejected transfers efficiently.

Record Keeping

Swiss VASPs must retain all travel rule records for a minimum of 10 years, consistent with general AML record-keeping requirements. Records should include:

• All originator and beneficiary information exchanged
• Counterparty VASP identification and verification records
• Risk assessment documentation
• Any sanctions screening results
• Communication records with counterparty VASPs
• Wallet verification records for self-hosted wallet transfers

Integration with Existing Compliance

Travel rule compliance should be integrated with the broader compliance technology stack rather than treated as a standalone requirement. Key integration points include:

• Customer onboarding — Collecting travel rule-required information as part of the KYC process
• Transaction monitoring — Incorporating travel rule data into transaction monitoring analysis
• Sanctions screening — Using travel rule information for real-time sanctions checks
• Reporting — Including travel rule compliance metrics in regulatory reporting

Cross-Border Challenges

Jurisdictional Differences

Travel rule thresholds, required data fields, and implementation timelines vary across jurisdictions. Swiss VASPs must navigate these differences when transacting with counterparties in jurisdictions with different requirements. Key variations include:

• Thresholds — Ranging from zero (full application) to USD 3,000 (US) to EUR 1,000 (EU)
• Data fields — Different jurisdictions may require additional or fewer data elements
• Self-hosted wallet treatment — Varying approaches to transfers involving non-VASP addresses
• Enforcement — Different levels of regulatory enforcement and compliance expectation

Sunrise Problem

The travel rule’s effectiveness depends on broad adoption by VASPs globally. When a Swiss VASP attempts to transmit travel rule information to a counterparty that has not implemented the rule, the information cannot be delivered. This asymmetric adoption creates compliance challenges for early adopters.

Swiss VASPs should establish policies for handling transfers to non-compliant counterparties, balancing customer service with regulatory compliance. Risk-based approaches that adjust due diligence intensity based on counterparty compliance status are consistent with FINMA expectations.

Future Developments

The travel rule landscape continues to evolve:

• Protocol convergence — Industry efforts towards standardisation may reduce interoperability challenges
• Regulatory expansion — More jurisdictions are implementing travel rule requirements, improving global coverage
• Technology advancement — Privacy-preserving compliance solutions that satisfy regulatory requirements without exposing unnecessary personal data
• DeFi application — Extending travel rule concepts to decentralised protocol interactions
• Automation — Increased automation of travel rule workflows reducing operational burden

For Swiss VASPs, travel rule compliance is a non-negotiable regulatory obligation that requires investment in technology, processes, and counterparty relationships. The maturity of a VASP’s travel rule implementation increasingly serves as a signal of overall compliance quality to regulators and institutional counterparties alike.

Donovan Vanderbilt is a contributing editor at ZUG TRADING, a digital asset trading and exchanges intelligence publication by The Vanderbilt Portfolio AG, Zurich. His analysis covers institutional market structure, OTC liquidity, and regulatory developments across Swiss and global digital asset markets.