A customer withdraws €50 worth of crypto. The amount is small. The platform still needs to handle the required sender and recipient information.
Under the EU’s revised Transfer of Funds Regulation, covered crypto transfers have no general minimum-value exemption from Travel Rule information requirements. A transfer below €1,000 remains within those requirements. Council of the EU’s explanation of the rules.
For crypto platforms, that changes where compliance belongs in the product. Information collection, counterparty identification and exception handling need to work throughout the everyday deposit and withdrawal journey.
The implementation question is straightforward: can the platform process a small transfer with the required information and a clear record of the decision?
What the EU’s zero-threshold Travel Rule covers
The crypto provisions of Regulation (EU) 2023/1113 have applied since 30 December 2024. They cover transfers where the originator’s or beneficiary’s crypto-asset service provider, including an intermediary, is registered in the EU.
Direct person-to-person transfers without a crypto-asset service provider are excluded. A transfer between a regulated platform and a self-hosted address is a different case.
Required information must be submitted securely before or alongside the transfer. It does not need to be written onto the blockchain itself. Transfer of Funds Regulation, Articles 2, 14 and 40.
This distinction matters for platform architecture. Asset movement and information exchange may use separate technical channels, but their records need to remain connected.
A transaction hash establishes that an on-chain transaction occurred. The platform also needs evidence that the accompanying information was handled correctly.
Why the FATF $1,000 threshold causes confusion
FATF’s guidance allows jurisdictions to adopt a USD/EUR 1,000 de minimis threshold for virtual asset transfers. Below that threshold, fewer requirements may apply.
Even then, the guidance calls for providers to collect the originator’s and beneficiary’s names, together with their wallet addresses or a unique transaction reference. Customer information should be verified where suspicious money laundering or terrorist financing circumstances arise. FATF guidance, paragraphs 191–192.
Describing this as a blanket “$1,000 exemption” can lead to incorrect product logic.
A team might build a withdrawal flow that starts collecting counterparty information only after the amount reaches $1,000. That design would leave a gap for EU-covered transfers.
For a platform operating across markets, the applicable jurisdiction should determine the information workflow. A generic threshold in a vendor’s example configuration cannot establish the legal requirements for every deployment.
Why €1,000 still matters for self-hosted wallets
The EU’s zero-threshold approach does not remove every monetary distinction.
For transfers exceeding €1,000 to or from a self-hosted address, the relevant provider must take adequate measures to assess whether that address is owned or controlled by its own customer. This assessment is additional to the underlying transfer information requirements. Transfer of Funds Regulation, Articles 14(5) and 16(2).
Product teams should keep these decisions separate:
- Applicable information requirements: What information is required for this transfer?
- Wallet classification: Is the address hosted by a provider or self-hosted?
- Ownership or control assessment: What evidence is needed about the customer’s relationship with the address?
- Transaction risk review: Do the available findings require further action?
A platform also needs a correction path. An address that is not recognised as belonging to a provider may still be hosted.
Finhost’s unhosted wallets management documents ownership-related checks and lets customers identify the actual provider when a wallet has been classified incorrectly. The service requires separate enablement, and the verification method needs to fit the deployment’s requirements.
A completed wallet check supplies evidence about the address relationship. Transaction risk still requires its own assessment.
Travel Rule legislation reached 83% of surveyed jurisdictions
The EU operates within a growing international framework.
In its 16 July 2026 targeted update, FATF reported that 83% of surveyed jurisdictions had passed legislation implementing the Travel Rule, up from 73% in 2025. That represents an increase of ten percentage points. A further 11 jurisdictions reported that implementation was under way. FATF’s July 2026 targeted update.
These figures measure legislative adoption. They do not establish how many providers exchange complete information successfully or how many transfers meet the requirements in practice.
FATF also highlighted continuing gaps in supervision and enforcement.
For platform teams, the operational implication is to assess actual counterparty readiness. A provider may operate in a jurisdiction with Travel Rule legislation while using different messaging infrastructure or handling information requests inconsistently.
Counterparty testing should therefore cover successful exchanges, unavailable connections, incomplete responses and follow-up procedures.
Build the information workflow into ordinary transfers
A useful implementation starts when the customer creates the transfer.
The platform should identify the relevant counterparty, determine what information is needed and check which details are already available. Customers should receive a focused request for anything outstanding.
Finhost’s crypto travel rule compliance describes transfer outcomes including approved, requires action, on hold and failed. Its documented workflow connects customer information requests and compliance review to the transaction.
For an EU deployment, teams should validate that the configured workflow applies the required information checks to covered transfers of every value. Finhost’s published page includes FATF threshold examples; those examples should not be treated as the EU rule.
The acceptance test should include small amounts from the start. A €50 withdrawal is a useful case because it exposes any logic that incorrectly bypasses information requirements below a monetary threshold.
Make missing information and technical failures distinguishable
Consider a €75 withdrawal to another crypto platform. The customer provides the recipient’s name, but the receiving provider cannot be reached through the configured messaging service.
Asking the customer to enter the same name again will not resolve the connection problem.
The platform needs to identify the reason the transfer cannot progress and direct the case to the appropriate next step.
- Customer information is missing: Make clear which details are required and how to submit them.
- Counterparty connection is unavailable: Identify which team owns the investigation and follow-up.
- Received information is incomplete: Specify what needs clarification from the counterparty.
- Wallet classification is uncertain: Explain how the customer or reviewer can correct it.
- A risk finding requires review: Identify who will assess the case and record the outcome.
These are implementation recommendations. The decision to execute, suspend, reject or otherwise resolve a transfer must follow the applicable requirements and the operator’s approved procedures.
Retries also need to remain linked to the original case. Otherwise, staff may see several requests without being able to establish which response belongs to the transfer.
Treat blockchain receipt and customer availability separately
Incoming transfers create a different operational challenge: assets may arrive on-chain while information checks remain unresolved.
A single “completed” status can hide that distinction.
The internal record should let staff identify whether assets have been received, whether required information is complete and whether the funds are available to the customer.
The customer-facing explanation should reflect the actual state. If information is missing, the customer needs a clear request. If the case is under review, support needs an accurate explanation of what is happening.
A practical test is to send an incoming transfer with incomplete information and ask:
- Can the reviewer identify exactly what is missing?
- Is there a defined follow-up process?
- Can support explain the status accurately?
- Is the release decision recorded?
- Can the team reconstruct the full sequence afterwards?
Connect Travel Rule checks with transaction monitoring
Travel Rule information and transaction monitoring contribute different evidence.
The information workflow establishes details about the parties to a transfer. Monitoring assesses activity and risk. Complete sender and recipient details do not resolve a suspicious transaction, and a favourable screening result does not supply missing information.
Teams evaluating Finhost’s AML & Transaction Monitoring (KYT) should review how screening outcomes connect with Travel Rule cases and the execution process.
For example, a transfer may have complete counterparty information but require compliance review because of a risk finding. Another may have no identified risk signal while still awaiting mandatory details.
Both need an understandable status, an assigned next action and a recorded decision.
For reviewers, the aim is a transaction record that brings the relevant evidence together. For customers, it is a clear explanation of what happens next.
What crypto platforms should review now
Start with every rule that uses transaction value to activate or bypass information checks.
Then test the main paths separately: a small provider-to-provider withdrawal, a self-hosted wallet transfer, an incoming deposit with missing information and an unreachable counterparty.
For each case, establish:
- Which jurisdictional requirements apply.
- What information and verification evidence are required.
- Which enabled service or integration handles each step.
- Who resolves exceptions.
- What record supports the final decision.
Once the workflow is operating, measure how often transfers need customer action, how long cases remain unresolved and which counterparties create repeated exceptions. Those measures help teams identify where the product needs clearer requests, better connectivity or more review capacity.
The EU’s zero-threshold Travel Rule makes small transfers part of the same operational responsibility. A working implementation connects the required information, the movement of assets and the evidence behind the decision—even when the customer is sending only €50.
Top comments (0)