A crypto exchange processing transfers for EU customers learns that every transaction – regardless of value – now carries an obligation to collect, verify and transmit originator and beneficiary information under the EU Transfer of Funds Regulation. The zero-threshold Travel Rule means that a single EUR 10 USDT withdrawal from a self-hosted wallet triggers the same counterparty due-diligence and record-keeping duties as a six-figure institutional settlement. For platforms operating across borders, the practical question is not whether to comply, but how to automate data collection, manage self-hosted wallet verification and handle missing-information scenarios without pausing business.
The EU Transfer of Funds Regulation, as it applies to crypto-asset service providers (CASPs) under MiCA, removes the de-minimis threshold found in many Travel Rule implementations elsewhere. This guide walks through the obligations step by step: what data must travel with each transfer, how to verify a self-hosted wallet address, when a transfer may proceed despite incomplete counterparty information, and what records the regulator expects. Each step reflects the regime as interpreted by ESMA and national competent authorities across the European Economic Area. The cross-border reality – where user wallets sit in one jurisdiction, liquidity in another and the entity itself in a third – shapes every compliance decision.
What the zero-threshold Travel rule means
Under the EU Transfer of Funds Regulation, a CASP facilitating a crypto-asset transfer must obtain and transmit full originator information (name, account identifier or wallet address) and full beneficiary information to the beneficiary's service provider, irrespective of the transaction value. The zero-threshold design reflects the EU's risk-based AML posture: digital assets move globally, instantaneously and pseudonymously, so the legislator declined to set a floor below which data may be omitted. In our cross-border practice, operators initially licensed in jurisdictions with USD 1,000 or EUR 1,000 thresholds discover that serving EU customers imposes the stricter EU standard across the entire user base, because segregating compliance by customer domicile mid-transaction is operationally impractical.
The data set for each transfer comprises the originator's full name (or the registered name of a legal entity), the originator's wallet address or account identifier, and equivalent details for the beneficiary. Where the originator or beneficiary is a customer of the CASP, the provider must have verified that information during onboarding under the usual KYC framework. Where the counterparty is not a customer – typically when a user withdraws to a self-hosted wallet or receives from an external address – the CASP must collect the information from its own customer and apply risk-based verification measures to the extent the counterparty's identity can be established.
Regulators in the leading MiCA hubs increasingly expect CASPs to demonstrate automated data-capture workflows, not manual form-filling for every withdrawal. The technical implementation – embedding originator/beneficiary fields into transaction messaging, API handshakes with counterparty VASPs, on-chain metadata layers – varies by platform architecture, but the legal obligation is uniform: the data must be accurate, complete and transmitted in real time or as close to real time as the settlement rail allows.
When a transfer involves a self-hosted wallet
A withdrawal to a self-hosted wallet poses the compliance challenge: the CASP's customer provides a destination address, but the wallet itself has no institutional custodian to receive Travel Rule data. The regulation addresses this by requiring the originating CASP to collect a declaration from its customer identifying the beneficial owner of the destination wallet and to conduct risk-based verification of that declaration. Verification does not mean the same level of documentary proof as onboarding a new customer, but it does mean more than accepting a typed name at face value.
In practice, we see three verification tiers. For low-risk customers (retail users, small balances, established transaction history), a signed declaration that the destination wallet is self-controlled may suffice, combined with a proof-of-control step such as signing a message with the destination address's private key. For higher-risk profiles – new customers, large withdrawals, customers flagged by transaction monitoring – the CASP may request additional evidence: a screenshot of the wallet interface showing the address, a video call where the customer demonstrates control, or corroborating on-chain history showing the address previously received funds from a known exchange under that customer's name.
When a customer receives a transfer from a self-hosted wallet, the beneficiary CASP must obtain the originator's information from its own customer (who ostensibly knows whose wallet sent the funds) and assess whether that information is plausible. National competent authorities accept that perfect verification of an external self-hosted originator is often impossible, but they expect the CASP to document the attempt, to apply enhanced due diligence where the amount or pattern raises concern, and to file a suspicious activity report if the customer cannot or will not provide credible originator details.
Collecting and transmitting the required data
The originating CASP collects the data at the point the customer initiates the transfer. For a platform-to-platform transfer (exchange A to exchange B), the workflow mirrors correspondent banking: the originating CASP embeds the data in the transaction instruction, typically via a SWIFT-like messaging layer (the crypto industry has adopted the InterVASP Messaging Standard and the Travel Rule Universal Solution Technology as common protocols) or, where both parties support it, as on-chain metadata.
The data must include the originator's full name, date and place of birth (for natural persons) or registration number and registered address (for legal entities), the originator's wallet address or account number, and the beneficiary's name and wallet address or account identifier. The beneficiary CASP, upon receipt, verifies that the incoming data matches its own customer record or, if the beneficiary is not its customer, assesses the plausibility of the declaration. The regulation permits the beneficiary CASP to reject or pause a transfer if the data is incomplete or implausible; in that scenario the originating CASP must decide whether to recall the transaction or to proceed after obtaining further information from its customer.
Where technical interoperability does not yet exist – some smaller VASPs lack Travel Rule messaging infrastructure – the fallback is manual communication: the originating CASP sends an email or secure message to the beneficiary institution with the required data, and both parties log the exchange. Regulators tolerate interim manual methods but expect automated solutions to be in place as the market matures. For an operator launching now, building Travel Rule messaging into the core transaction engine is not optional.
The missing-information rule and when a transfer may proceed
The regulation permits a CASP to execute a transfer even when complete beneficiary information is unavailable, provided three conditions hold: the CASP has made reasonable efforts to obtain the information from its customer; the CASP has assessed and accepted the money-laundering and terrorist-financing risk; and the CASP documents both the missing data and the risk assessment. This carve-out recognises that requiring perfect data on every transaction would freeze legitimate business where a user genuinely cannot identify a counterparty (for example, receiving an unsolicited payment from an unknown address).
Reasonable efforts means at least one request to the customer, with a clear explanation of what is required and why. If the customer does not respond or provides implausible information, the CASP may still proceed if the transaction amount, the customer's profile and the destination address collectively present low risk. However, a pattern of missing-information transfers from the same customer, or a large-value transfer to an address associated with high-risk jurisdictions or mixing services, will not qualify for the carve-out. In those cases the CASP must either obtain the information or decline the transaction.
National competent authorities audit missing-information logs during supervision visits. A CASP that routinely executes transfers without beneficiary data, citing the carve-out, will face questions about the adequacy of its risk assessment and the genuineness of its collection efforts. Operators we advise typically set internal thresholds: below EUR 500 and low-risk customer, proceed with documented effort; above EUR 500 or any elevated-risk indicator, pause until information is provided.
Record-keeping and what the regulator audits
The CASP must retain, for at least five years, a complete record of every transfer: the originator and beneficiary information transmitted or received, the date and time, the amount and type of crypto-asset, the wallet addresses, the risk assessment (if any), and any communication with the customer or the counterparty CASP regarding missing or incomplete data. These records must be retrievable within a reasonable timeframe – typically 24 to 48 hours – in response to a competent authority request or a law-enforcement query.
During a compliance audit or an on-site inspection, the regulator will sample transactions and trace each one through the Travel Rule workflow: did the platform capture the data at initiation? Was it transmitted to the beneficiary institution? If information was missing, was the risk-assessment procedure followed? If the transfer involved a self-hosted wallet, what verification steps were taken? A gap in any of these steps – particularly a pattern of zero-verification self-hosted withdrawals or a failure to log missing-information decisions – is a supervisory finding and, depending on severity, may trigger an enforcement action or a licence condition.
The record-keeping obligation extends to rejected transactions. If a CASP declines a transfer because the customer will not provide beneficiary information or because the destination address appears on a sanctions list, that decision and its basis must be documented. The absence of a transaction from the blockchain does not relieve the record-keeping duty; the regulator expects to see the decision trail for every customer instruction, executed or not.
Cross-border interaction: when EU and non-EU rules collide
A CASP licensed in Malta under MiCA may have customers across the EU/EEA, a banking relationship in Switzerland and a liquidity provider in Singapore. Each leg of that structure sits under a different AML and Travel Rule regime. The EU zero-threshold rule applies to the transfers the CASP facilitates for its EU customers, but the Swiss bank (if it handles fiat legs) is subject to FINMA's AML framework, and the Singapore liquidity provider operates under MAS rules. Where a single transaction crosses multiple jurisdictions, the strictest standard governs the entire flow – which, in most cases involving the EU, means zero-threshold compliance even if the other jurisdictions allow a de-minimis carve-out.
In our cross-border practice, operators initially assume they can segregate compliance by the customer's declared residency. That assumption breaks down in two scenarios. First, residency for AML purposes is not always where the customer says they live; it can turn on habitual residence, the location from which the customer accesses the platform or the jurisdiction of the underlying bank account. Second, applying different data-collection standards to different customer cohorts within the same platform risks operational error and regulatory arbitrage. The safer model, and the one we see adopted by exchanges scaling into the EU, is to implement zero-threshold Travel Rule across the entire user base and to design the transaction engine so that every transfer, regardless of origin or destination, collects and transmits the full data set.
Where a counterparty VASP in a non-EU jurisdiction cannot or will not accept Travel Rule data (because its domestic regime does not yet mandate it, or because the technical integration is incomplete), the EU CASP must still collect the information from its own customer and retain it. The regulation does not permit a CASP to bypass data collection simply because the receiving institution lacks the infrastructure to process it. In practice, this means EU CASPs must either limit counterparty relationships to VASPs with Travel Rule capability or accept that certain transfers will require manual data logging until the global standard converges.
Technology integration and the InterVASP protocols
The technical backbone of Travel Rule compliance in the crypto industry rests on two open protocols: the Travel Rule Universal Solution Technology (TRUST) and the InterVASP Messaging Standard (IVMS). Both provide standardised message formats for originator and beneficiary data, and both integrate with existing transaction workflows via APIs. A CASP adopting one of these protocols can exchange Travel Rule data with any other CASP on the same protocol without building bespoke integrations for each counterparty.
Implementation begins with registering the CASP's wallet addresses or account identifiers in a shared directory, so that when an outbound transaction reaches one of those addresses, the originating CASP can query the directory, identify the beneficiary institution and route the Travel Rule message accordingly. The message travels in parallel with the on-chain transaction (or, for custodial-to-custodial transfers, in the same API call that instructs the transfer), and the beneficiary CASP's system automatically ingests the data, compares it to the customer record and either approves or flags the transaction for manual review.
In our advisory work, we see CASPs underestimate the internal lift: integrating a Travel Rule protocol is not merely a matter of enabling an API. It requires mapping the platform's customer database to the IVMS data model, training the compliance team to interpret risk flags generated by automated screening, and establishing fallback procedures for scenarios where the protocol handshake fails or times out. The regulator's expectation is that, once integrated, the system runs without manual intervention for the majority of transfers, and that manual overrides are logged and reviewed.
For a scoped assessment of your Travel Rule workflows and counterparty VASP due diligence, contact OBOLUS at info@oboluslaw.com. We map the technology stack, the compliance logic and the record-keeping procedures that national competent authorities audit, and we pressure-test the solution against the zero-threshold standard before it goes live.
What happens when compliance fails
A CASP that processes transfers without collecting or transmitting the required originator and beneficiary information, or that routinely executes transactions despite red flags in the missing-information assessment, faces administrative penalties under the national AML framework and potential licence suspension under MiCA. National competent authorities have the power to impose fines calculated as a percentage of annual turnover, to require the appointment of an external compliance monitor and, in severe cases, to withdraw the CASP authorisation.
Beyond regulatory enforcement, non-compliance creates operational risk. Banks providing fiat rails to crypto platforms conduct their own due diligence on the platform's AML controls; a pattern of Travel Rule gaps discovered during the bank's audit is grounds for account closure. We have seen situations where a CASP lost its euro banking relationship because the bank's internal review identified that the platform was executing large-value withdrawals to self-hosted wallets without any verification of the destination wallet owner – a clear breach of the zero-threshold rule. Recovering from that closure – finding a new banking partner willing to onboard a platform with a recent compliance failure – takes months and often requires migrating to a different jurisdiction with a stricter supervisory sign-off process.
For retail customers, the consequence of a CASP's non-compliance is delayed or rejected transactions. If a platform cannot provide Travel Rule data to the beneficiary institution, that institution may refuse to credit the transfer, leaving the funds in limbo until the originating CASP recalls the transaction or provides the missing information. Customers attribute the friction to the platform, not to the regulation, and the reputational damage accumulates.
Self-assessment checklist for zero-threshold compliance
A CASP preparing for zero-threshold Travel Rule compliance, or auditing an existing implementation, can work through the following diagnostic steps. Each question reflects a line item that national competent authorities examine during supervision.
- Does the transaction initiation interface (web, mobile, API) capture the beneficiary's full name and wallet address for every withdrawal or transfer, before the transaction is broadcast?
- For transfers to self-hosted wallets, does the workflow require the customer to declare the wallet owner's identity and to provide proof of control (message signature, screenshot or other verification)?
- Is there a documented risk-assessment procedure for scenarios where the customer cannot or will not provide complete beneficiary information, and does that procedure include clear thresholds for when a transaction may proceed and when it must be declined?
- Does the platform integrate with a Travel Rule messaging protocol (TRUST, IVMS or equivalent) to transmit data to institutional counterparties, and is the integration tested against major exchanges and custodians in the EU?
- Are Travel Rule data fields and risk-assessment decisions logged in a retrievable format, with retention for at least five years, and can those records be produced within 48 hours in response to a regulator's request?
- Has the compliance team received training on the zero-threshold standard, on the verification tiers for self-hosted wallets and on the regulatory expectation around missing-information transfers?
- Is there a fallback procedure for transfers where the beneficiary VASP lacks Travel Rule infrastructure, and does that fallback include manual data logging and supervisory reporting if the pattern becomes significant?
A "no" answer to any of these questions is a gap. The earlier the gap is identified – ideally during the build phase, not after the first supervisory inspection – the lower the remediation cost and the faster the platform can scale with confidence that the compliance foundation will hold under regulatory scrutiny.
Common mistakes and how operators get it wrong
The most frequent error is treating the zero-threshold rule as a technical checkbox rather than a business-process redesign. A platform that bolts a Travel Rule form onto the withdrawal screen, but does not train customer-support staff to explain what the form is for or why certain withdrawals are paused pending verification, will see user friction and complaint volume spike. The compliance obligation is not merely to collect data; it is to collect accurate data and to verify it to a standard the regulator will accept.
A second mistake is underestimating the self-hosted wallet verification burden. Operators initially assume that a typed declaration – "I confirm this wallet is mine" – satisfies the requirement. It does not. National competent authorities expect risk-based verification, which, for anything beyond the smallest retail transactions, means some form of proof that the customer controls the destination address and that the declared identity is plausible. Platforms that skip this step discover the gap during a supervisory inspection, often too late to retrofit verification into thousands of historical transactions.
A third error is failing to document missing-information decisions. When a customer initiates a transfer and cannot provide beneficiary details, the platform must log not only the missing data but also the reason the transaction was permitted to proceed (low value, low-risk customer, reasonable efforts made) or the reason it was declined. An audit log that shows dozens of missing-information transfers approved without any documented risk assessment is, to a regulator, evidence of a non-functioning AML programme.
Finally, some CASPs mistakenly believe that passporting within the EU means they can ignore national variations in Travel Rule interpretation. While the legal standard is uniform across MiCA, national competent authorities retain discretion in supervision and enforcement priorities. A CASP authorised in one member state but serving customers in another must monitor supervisory guidance from both authorities and, where the guidance diverges, apply the stricter standard. Operators we advise routinely encounter this when the home-state regulator is pragmatic about interim manual processes, but a host-state authority in a major financial centre expects full automation from day one.
When to engage counsel
A CASP should bring in legal counsel at three points: during the licence application, when designing the Travel Rule workflow, and when a supervisory finding or a banking-relationship issue surfaces a compliance gap. At the application stage, counsel maps the obligations under the Transfer of Funds Regulation to the platform's technical architecture, identifies the gaps and recommends the integration path – protocol-based, manual or hybrid – that fits the business model and the budget. This front-end work prevents the scenario where a platform launches, scales to significant volume and only then discovers that its Travel Rule implementation does not meet the national competent authority's expectations.
During the design phase, counsel works with the engineering and compliance teams to draft the customer-facing disclosure (what the form says, what happens if the customer does not complete it), to define the risk-assessment logic (which scenarios permit missing-information transfers, which do not) and to structure the record-keeping so that every decision is auditable. This is also the stage at which cross-border questions are resolved: if the platform will serve both EU and non-EU customers, does it apply zero-threshold globally or attempt geographic segmentation? The answer shapes the entire transaction engine, and getting it wrong means a costly rebuild.
When a compliance issue arises post-launch – a supervisory letter, a bank threatening account closure, a pattern of customer complaints about frozen withdrawals – counsel conducts a gap analysis, provides a remediation roadmap and, where necessary, engages with the regulator on the platform's behalf. Regulators are more receptive to a platform that identifies a gap proactively, presents a credible fix and implements it on a committed timeline than to one that waits until enforcement to acknowledge the problem.
To map the licence, banking and compliance stack for your platform before you commit, write to OBOLUS at info@oboluslaw.com. We scope the work to the stage you are at – pre-launch design, post-launch audit or supervisory-response – and we deliver fixed-fee advisory tied to the decisions you need to make, not open-ended hourly engagement.
How this regime fits into the broader MiCA framework
The zero-threshold Travel Rule under the Transfer of Funds Regulation is one pillar of the AML obligations that MiCA imposes on CASPs; it sits alongside the customer due-diligence requirements at onboarding, the ongoing transaction-monitoring duty and the suspicious-activity-reporting obligation. Together, these elements form a compliance programme that regulators audit as a whole. A CASP cannot compensate for weak Travel Rule processes with strong onboarding KYC, and vice versa; the regulator expects each component to function at a consistently high standard.
The regime interacts with MiCA's operational and prudential requirements in two ways. First, the appointment of a money-laundering reporting officer (MLRO) – a person responsible for the CASP's AML programme – is mandatory under MiCA. That officer oversees Travel Rule implementation, reviews missing-information logs and serves as the point of contact for the national competent authority on AML matters. The MLRO's role is not merely administrative; supervisors expect that individual to have the technical understanding to assess whether the Travel Rule workflow captures the required data accurately and the authority within the organisation to pause or reject transactions that present unacceptable risk.
Second, MiCA's requirement that a CASP maintain sufficient own funds and professional-indemnity insurance extends to AML compliance. If a CASP suffers a regulatory penalty or loses a banking relationship because of Travel Rule failures, the financial impact must be absorbed without jeopardising the platform's solvency or its ability to meet customer-withdrawal obligations. In practice, this means that compliance risk is not only a regulatory matter but also a capital-adequacy matter, and the CASP's board must treat it accordingly.
Related at OBOLUS
- Compliance, AML & Travel Rule for Digital-Asset Businesses – the OBOLUS practice overview for AML, transaction monitoring and Travel Rule implementation across operating jurisdictions
- MiCA Level 2 and Level 3 Measures: What Applies and When – tracking the regulatory technical standards and implementation timelines that shape CASP obligations under MiCA
- KYC and Onboarding Framework in South Africa – a comparative view of customer due-diligence requirements in another emerging digital-asset jurisdiction
FAQ
What does this regime require from a VASP?
The EU Transfer of Funds Regulation requires a CASP to collect, verify and transmit full originator and beneficiary information for every crypto-asset transfer, regardless of value. This includes the names, dates of birth (for natural persons) and wallet addresses of both parties. Where a transfer involves a self-hosted wallet, the CASP must obtain a declaration from its customer identifying the wallet owner and must apply risk-based verification to that declaration. The regime also mandates record-keeping for at least five years and imposes a duty to assess and document the risk when complete information is unavailable.
Who must act as MLRO for a crypto firm?
Under MiCA, a CASP must appoint a money-laundering reporting officer (MLRO) who is responsible for the design, implementation and oversight of the firm's AML programme, including Travel Rule compliance. The MLRO is the point of contact for the national competent authority on AML matters, reviews transaction-monitoring alerts and missing-information logs, and has the authority to pause or reject transactions that present unacceptable money-laundering or terrorist-financing risk. National competent authorities expect the MLRO to have both technical expertise in digital-asset operations and sufficient seniority to enforce compliance decisions across the organisation.
How do regulators audit crypto AML programs?
National competent authorities audit a CASP's AML programme through a combination of desk-based reviews, on-site inspections and transaction sampling. During an inspection, the regulator will select a sample of transactions and trace each through the Travel Rule workflow: was the originator and beneficiary data collected at initiation, was it transmitted to the counterparty VASP, was risk assessment applied where information was incomplete, and are the records retrievable? The regulator also reviews the CASP's policies and procedures, tests the transaction-monitoring system's ability to flag high-risk patterns, and interviews the MLRO and compliance staff to assess their understanding of the obligations. Gaps identified during the audit may result in supervisory findings, required remediation or, in severe cases, administrative penalties or licence conditions.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we pressure-test compliance workflows – including Travel Rule implementation – against the standards national competent authorities enforce during supervision. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in MiCA implementation, AML frameworks and cross-border Travel Rule workflows for crypto-asset service providers.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.