Back to Blog
Jurisdiction Conflicts2026-08-172 min read

Travel Rule Thresholds: Why US, EU, and Singapore Can't Agree

Three jurisdictions, three different Travel Rule thresholds, three different data requirements. Here's what cross-border transfers actually trigger — and how to comply with all three.

The conflict

The FATF Travel Rule requires virtual asset service providers (VASPs) to share originator and beneficiary information on transfers. Simple enough in theory. In practice, three major jurisdictions implemented it with incompatible thresholds and data requirements:

| | US (FinCEN) | EU (TFR) | Singapore (PSN02) | |---|---|---|---| | Threshold | $3,000 | €0 (zero threshold) | S$1,500 (~$1,100 USD) | | Data fields | Name, address, account number | Name, address, account number, LEI/national ID | Name, address, account number + transaction purpose + relationship | | Self-hosted wallets | No specific rule | Must verify ownership above €1,000 | Must collect purpose of transaction |

Why this creates operational conflict

If you're a VASP processing a $2,000 cross-border transfer from Singapore to the US:

  • Singapore says: Collect Travel Rule data (threshold is S$1,500)
  • US says: No Travel Rule obligation (threshold is $3,000)
  • EU says (if routed through EU): Collect Travel Rule data + verify wallet ownership if self-hosted

You end up collecting different data for the same transaction depending on the direction and the counterparty's jurisdiction.

The EU zero-threshold problem

The EU's Transfer of Funds Regulation (Regulation 2023/1113) applies to all transfers regardless of amount. This is the strictest implementation globally and creates friction with:

  • US VASPs that don't collect or transmit Travel Rule data below $3,000
  • Singapore VASPs that only trigger at S$1,500
  • Any self-hosted wallet interaction above €1,000 (requires wallet ownership verification)

Resolution approach

Superset compliance: Implement the strictest data collection (EU zero-threshold) globally, even when not legally required by the counterparty's jurisdiction.

  1. Collect full originator/beneficiary data on all transfers (satisfies EU)
  2. Add Singapore-specific fields (purpose, relationship) for all SG-related transfers (satisfies PSN02)
  3. Implement self-hosted wallet verification at €1,000 (strictest threshold, satisfies EU TFR)
  4. Transmit data to counterparty only when their jurisdiction's threshold is met (don't push unwanted data)

This approach over-collects but never under-collects — the safe default for AML compliance.

Risk score

  • Enforcement likelihood: 88/100 (active enforcement in all three jurisdictions)
  • Penalty severity: 80/100 (fines + license conditions)
  • Operational impact: 75/100 (systems integration required)
  • Weighted risk: 82/100 (high)

Run diff_jurisdictions("US", "EU", "travel_rule") to see the full conflict analysis with source citations. Start with a Conflict Snapshot →

AMLTravel RuleUSEUSingaporeFinCENMiCA