An exchange operating out of Lithuania discovers its Singapore users are routed through a custody partner in Switzerland, and its settlement bank sits in New York. The regulator in each jurisdiction expects the Travel Rule – the obligation to pass originator and beneficiary data with every transfer – to be enforced at a different point in the transaction chain, under different thresholds, for different asset types. Within a single day, three supervisory letters arrive. The question is no longer whether the Travel Rule applies; it is which version applies, where, and how a business reconciles five overlapping regimes without fragmenting its operational stack.
The Travel Rule is Financial Action Task Force (FATF) Recommendation 15, extended in 2019 to virtual assets. Every FATF member committed to transpose it into domestic law. But implementation diverged. Some jurisdictions set the threshold at 1,000 USD; others at zero. Some require full beneficiary verification before transmission; others permit a post-transmission data exchange. Some apply the rule to stablecoin transfers only; others to every on-chain movement including DeFi interactions. And enforcement – the moment a regulator converts the written obligation into a fine, a licence suspension or a frozen correspondent account – varies more than the law itself. This tracker maps where the Travel Rule is in force, where enforcement has moved from policy to action, and how a multi-jurisdiction VASP builds a compliant data flow when the rules conflict.
The Travel Rule baseline: FATF Recommendation 15 and what it requires
FATF Recommendation 15 requires that originators and beneficiaries of wire transfers be identified, and that the relevant information travel with the transaction. In June 2019, FATF amended the Interpretive Note to Recommendation 15 to make clear that the obligation extends to transfers of virtual assets – defined broadly to include any digital representation of value that can be digitally traded or transferred and used for payment or investment purposes. The baseline expectation is that a VASP (virtual asset service provider) must obtain, hold and transmit to the next VASP in the chain specified originator and beneficiary data.
That data includes, at minimum, the originator's name, account number (or equivalent transaction reference) and physical address or national identity number; and the beneficiary's name and account number. The threshold at which the obligation applies was left to national transposition, but FATF's own guidance suggested that jurisdictions should apply the rule to transfers above 1,000 USD or EUR, consistent with the traditional wire-transfer threshold. The mechanics of compliance – how data is passed, in what format, and whether it must be verified before transmission or may be validated afterward – were also left to domestic regulators, creating immediate divergence.
In our cross-border practice, the first compliance question is never "do we comply with the Travel Rule" but rather "which Travel Rule." A VASP licensed in Malta under the prior Virtual Financial Assets framework, passporting into Germany under the transitional regime, and holding custody relationships in Singapore and Switzerland, faces four distinct transposition regimes. Each interprets "account number" differently (a blockchain address, a customer reference, an internal ledger ID). Each sets a different data standard (some accept the InterVASP Messaging Standard; others require bilateral API integrations). And each enforces at a different operational layer – some at the point of customer onboarding, some at the transaction broadcast, some at settlement.
Where the Travel Rule is law: transposition status across flagship hubs
As of early 2026, the Travel Rule has been transposed into enforceable law or binding regulation in every major licensing jurisdiction for digital assets. The divergence is in scope, threshold and enforcement mechanism. The European Union implemented the rule through the Fifth and Sixth Anti-Money Laundering Directives and, from late 2024, through the AML Regulation that sits alongside MiCA. Under that regime, the Travel Rule applies to transfers of crypto-assets from the first euro, with no de-minimis threshold for the data obligation – though member states retain discretion on the threshold at which enhanced due diligence is required.
In the United Arab Emirates, VARA's AML/CFT rulebook for virtual-asset service providers in mainland Dubai adopted FATF Recommendation 15 with a threshold tied to the dirham equivalent of the FATF baseline, and the expectation that data travels with the transaction in real time. The ADGM, under FSRA supervision, applies a parallel regime within the Abu Dhabi financial free zone, with slightly different data-field definitions but equivalent enforcement expectations. Singapore's Payment Services Act requires Digital Payment Token service providers to comply with the Travel Rule for transactions above a specified threshold; enforcement has been active since mid-2023, with the Monetary Authority of Singapore conducting thematic reviews of transaction-monitoring systems and data-transmission capabilities.
Switzerland transposed the obligation through amendments to the Anti-Money Laundering Act and implementing ordinances; FINMA expects compliance across all token types, with particular scrutiny for stablecoin issuers and custodians. The United Kingdom applies the Travel Rule through the Money Laundering Regulations as amended; cryptoasset firms registered with the Financial Conduct Authority are subject to the same wire-transfer obligations as traditional money-service businesses, with enforcement focused on the quality of customer due diligence and the auditability of data flows. Hong Kong's VASP licensing regime under the Securities and Futures Commission includes the Travel Rule as a condition of the licence; failure to demonstrate compliant data transmission is a basis for licence suspension or revocation.
The zero-threshold problem: jurisdictions that apply the rule from the first unit
The sharpest operational challenge for a multi-hub VASP is the zero-threshold jurisdiction. Under the EU AML Regulation, the Travel Rule applies to every transfer of crypto-assets, regardless of value. There is no de-minimis carve-out for small retail transactions, no exemption for wallet-to-wallet movements within the same platform, and no concession for on-chain gas payments or staking rewards. Every movement that constitutes a "transfer" under the regulation triggers the data obligation. The effect is that a platform operating in the EU must, in principle, capture and transmit originator and beneficiary information for a 5-euro stablecoin payment, a 20-euro NFT purchase settled in ether, and a 100-euro withdrawal to a self-hosted wallet.
In practice, compliance at a zero threshold requires automated data capture at onboarding (full KYC for every customer, with no simplified due diligence), structured fields in the transaction API for originator and beneficiary data, and either bilateral integration with receiving VASPs or adoption of a common messaging standard such as the InterVASP Messaging Standard or the TRUST protocol. Where the beneficiary is a self-hosted wallet – an address not controlled by a regulated intermediary – the regulation permits the VASP to record the address and proceed, provided the customer declares ownership and the VASP conducts risk-based verification. But the data obligation does not fall away; it shifts to an attestation model.
Operators we advise routinely ask whether a zero-threshold regime is enforceable at scale. The answer is that it is enforceable selectively. Regulators focus enforcement on high-value transactions, on transactions to or from jurisdictions flagged by FATF as high-risk, and on patterns that suggest structuring (breaking a large transfer into multiple small ones to evade monitoring). A platform that can demonstrate systematic data capture, a functioning transaction-monitoring system, and a credible process for investigating alerts will survive a thematic review even if occasional low-value transfers fall through the net. A platform that cannot demonstrate the system – that treats the Travel Rule as a manual check on outbound wires above 10,000 euros – will not.
Enforcement in action: where regulators have moved from policy to sanction
Enforcement of the Travel Rule has, until recently, been confined to warning letters, requests for remediation plans, and the denial or delay of new licences. That changed in late 2023 and into 2024, when several regulators issued public sanctions. Singapore's Monetary Authority issued prohibition orders against individuals at VASPs that failed to implement transaction monitoring; the orders barred those individuals from holding compliance or senior-management roles at any regulated entity in Singapore. The message was that the Travel Rule is not a technical standard; it is a fitness test for the people running the business.
In the European Union, national competent authorities under the Fifth Anti-Money Laundering Directive issued administrative fines to exchange operators that could not demonstrate real-time data transmission to counterparty VASPs. The fines were not large – in the low six figures – but they were accompanied by public censure and enhanced reporting obligations, which together made the firms un-bankable in several member states. The reputational cost exceeded the monetary penalty by an order of magnitude. In the United Kingdom, the Financial Conduct Authority suspended the cryptoasset registration of a payments firm that routed transactions through an unregistered affiliate to avoid Travel Rule obligations; the suspension was lifted only after a full operational restructure and the resignation of two directors.
The United Arab Emirates has taken a different approach. VARA's enforcement to date has been prospective: firms that apply for a licence must demonstrate compliant Travel Rule processes before the licence is issued. An application without a functioning transaction-monitoring system and documented VASP counterparty agreements is rejected at the preliminary stage, with no appeal. The effect is that enforcement happens at the entry gate, not after the fact. For a business seeking to establish a Dubai hub, that means Travel Rule compliance is not a post-licence project; it is a condition of filing.
Conflicting thresholds and how to reconcile them in a single operational stack
A VASP licensed in Singapore (threshold at a specified level), with users in the EU (zero threshold), custody in Switzerland (FATF baseline threshold), and a settlement account in New York (threshold under the New York Department of Financial Services BitLicense) faces four different data obligations for the same transaction. The answer is to build to the strictest standard. If any leg of the transaction touches a zero-threshold jurisdiction, the data must be captured and transmitted for every transaction, regardless of value. The alternative – fragmenting the transaction flow by jurisdiction, with different data fields and different transmission rules for each – creates operational risk, audit risk, and the near certainty of a breach when a customer moves between jurisdictions or when a transaction is routed through an unexpected correspondent.
In practice, that means onboarding every customer to the EU standard (full KYC, proof of address, declared wallet ownership for self-hosted destinations), structuring the transaction database to hold FATF-compliant originator and beneficiary fields, and configuring the transaction API to pass those fields in a standardized format to every counterparty VASP. The cost is front-loaded: higher customer drop-off at onboarding, more rejected transactions where data is incomplete, and the engineering overhead of maintaining a structured data layer across the entire transaction stack. The benefit is that the business is defensible in every jurisdiction and can add new markets without re-engineering the core compliance architecture.
Where the receiving VASP is not Travel Rule-capable – a common situation with smaller exchanges in emerging markets – the originating VASP must decide whether to block the transaction or to proceed with documented risk acceptance. Several regulators permit the latter, provided the VASP records the attempt to transmit, logs the counterparty's inability to receive, and escalates the transaction for enhanced due diligence if it meets other risk indicators (large value, high-risk jurisdiction, beneficial-owner concern). The record is the defense. Without it, the transaction is a breach.
Self-hosted wallets and the unhosted-wallet problem: where the rule breaks down
The Travel Rule assumes a chain of regulated intermediaries. When a customer withdraws to a self-hosted wallet – an address not controlled by a VASP – the chain ends. The originating VASP must still collect beneficiary information (the customer's declaration that they own the address, and any supporting evidence the VASP's risk model requires), but there is no receiving VASP to accept the data transmission. The regulatory expectation varies. Under MiCA and the EU AML Regulation, the VASP must verify that the customer controls the address (typically through a signed message or a test transaction) and must apply enhanced due diligence if the transfer exceeds a specified threshold. Self-hosted transfers above that threshold trigger additional checks: source of funds, purpose of the transfer, and an assessment of whether the wallet has interacted with sanctioned addresses or mixing services.
In Singapore, the Monetary Authority's guidance permits self-hosted withdrawals but expects the VASP to conduct blockchain analytics on the destination address and to block the transaction if the address is linked to illicit activity. The VASP's defence in a subsequent review is not that it applied a risk score; it is that it used a credible analytics tool, documented the score and the decision, and escalated marginal cases to the money-laundering reporting officer. Switzerland and the United Kingdom apply similar frameworks, with the common thread that the self-hosted transfer is not exempt from the Travel Rule; it is simply a different compliance path.
For a business model that depends on customer self-custody – a non-custodial exchange, a DeFi interface, a wallet provider – the Travel Rule creates an existential tension. If every transfer to a self-hosted address requires full KYC and transaction-level verification, the user experience converges with that of a traditional custodial platform, and the non-custodial value proposition disappears. Several operators have responded by geo-blocking EU and Singapore users, routing those users to custodial subsidiaries, or restructuring as pure software providers with no direct customer relationship. Each path has legal and commercial risks; none is a long-term solution for a business seeking scale. The unhosted-wallet question remains the unsolved design problem at the centre of Travel Rule enforcement.
Stablecoins, CBDCs and other edge cases: when the asset type changes the rule
Not every digital asset is treated identically under the Travel Rule. Stablecoins – tokens designed to maintain a stable value against a reference fiat currency – attract heightened scrutiny in several jurisdictions because they are perceived as closer to e-money than to speculative crypto-assets. Under MiCA, e-money tokens (EMTs) are subject to the full AML/CFT regime, including the Travel Rule from the first euro, with no concessions for small-value payments. An issuer of an EMT licensed under MiCA must therefore implement Travel Rule processes not only for exchange-to-exchange transfers but for every on-chain redemption, every payment, and every wallet-to-wallet movement where the token is used as a means of payment. The operational model is closer to a payment-card network than to a cryptocurrency.
Central bank digital currencies (CBDCs) – where they exist in pilot or production – occupy an uncertain space. If the CBDC is retail (directly held by consumers) and permissioned (the central bank or its delegate knows the identity of every wallet holder), the Travel Rule may be satisfied by the underlying infrastructure, with no additional obligation on intermediaries. If the CBDC is wholesale (bank-to-bank) or permissionless (open-access but pseudonymous), the Travel Rule applies as it does to any other virtual asset. The latter model is rare; most CBDC designs centralise identity at the protocol layer, rendering the Travel Rule redundant for transactions within the system. Transfers between a CBDC and a non-CBDC asset – a retail CBDC sold for a stablecoin, for instance – fall squarely within the Travel Rule, with the exchange or OTC desk acting as the obligated VASP.
Non-fungible tokens (NFTs) are generally carved out of the Travel Rule in most transposition regimes, on the theory that an NFT transfer is more akin to the sale of a collectible than to a payment or investment. That carve-out fails when the NFT is fractionalized, when it represents a financial claim, or when it is used as collateral in a DeFi lending protocol. Regulators in the leading hubs increasingly expect VASPs to apply substance-over-form analysis: if the token functions as a payment instrument or a store of value, the Travel Rule applies, regardless of the label.
The messaging layer: IVMS, TRUST and how data moves between VASPs
The Travel Rule requires data transmission, but it does not specify the format. In the absence of a global standard, two protocols have emerged. The InterVASP Messaging Standard (IVMS), developed by an industry working group and published by the Financial Action Task Force, defines structured JSON fields for originator and beneficiary data and a message envelope for VASP-to-VASP communication. IVMS is transport-agnostic: the data can be sent by API, email, or any other secure channel, provided the format is consistent. The TRUST protocol, developed by CipherTrace and others, adds a discovery layer – a directory of VASPs and their messaging endpoints – and a certificate-based authentication mechanism.
Adoption has been slow. As of early 2026, fewer than half of the licensed VASPs in the major hubs support IVMS in production, and fewer still use TRUST. The gap is filled by bilateral integrations (direct API connections between large exchanges) and by manual data transfer (email or secure file upload) for smaller counterparties. For a VASP operating at scale, that means maintaining three parallel data paths: automated IVMS/TRUST for counterparties that support it, API integration for strategic partners, and a manual fallback for the long tail. The compliance cost is in the engineering and the ongoing testing: each path must be audited, each message format must be validated, and each failure must be logged and escalated.
Regulators do not mandate a specific protocol, but they increasingly expect interoperability. A VASP that can only communicate with counterparties using the same proprietary format is not Travel Rule-compliant; it is compliant only within a closed network. The audit question is whether the VASP can demonstrate successful data transmission to a statistically significant share of its transaction counterparties, across jurisdictions and platforms. The metric is not 100% coverage – that is impossible in a fragmented market – but it is coverage sufficient to capture the bulk of transaction value and to block high-risk flows.
Jurisdiction comparison: threshold, scope and enforcement posture
A side-by-side view of Travel Rule transposition in the flagship licensing hubs reveals three clusters. The strict cluster – the EU under MiCA and the AML Regulation, Singapore under the Payment Services Act – applies the rule from a low or zero threshold, expects real-time data transmission, and has issued public sanctions for non-compliance. These are the jurisdictions where Travel Rule capability is a licensing gatekeeper: an application without it is rejected outright. The baseline cluster – Switzerland, Hong Kong, the United Kingdom – applies the FATF threshold, permits some flexibility in data format, and enforces primarily through thematic reviews and remediation orders rather than immediate sanctions. These jurisdictions treat the Travel Rule as a mature AML obligation, equivalent to customer due diligence or suspicious-activity reporting.
The developing cluster – jurisdictions that have transposed the rule into law but have not yet built enforcement capacity or issued guidance on technical implementation – includes several offshore financial centres and emerging crypto hubs. The rule is on the books, but the regulator has not conducted a Travel Rule audit, has not published a list of approved transaction-monitoring vendors, and has not clarified whether a manual process suffices or whether automation is required. For a VASP considering these jurisdictions, the risk is not that the rule does not apply; it is that the standard of compliance is unknown until the first enforcement action, by which time it is too late to remediate.
The comparison is not static. Jurisdictions in the developing cluster are moving toward the baseline cluster as supervisory capacity builds and as the FATF conducts mutual evaluations. A jurisdiction that tolerated manual Travel Rule processes in 2023 may demand automated transaction monitoring in 2026. The planning question for a multi-hub VASP is not where the rule stands today but where it will stand in 24 months, because that is the timeline to engineer, test and deploy a new compliance architecture.
Building a compliant multi-jurisdiction stack: the decisions, the vendors, the internal controls
A Travel Rule-compliant VASP begins with the data model. Every customer onboarding flow must capture the fields required by the strictest jurisdiction in which the VASP operates: full name, date of birth, residential address, national identity number or equivalent, and (for self-hosted withdrawals) a declaration of wallet ownership. The data must be structured, not free-text: fields must map to IVMS specifications so that outbound messages can be generated automatically. Customer due diligence records must be retained for the longest retention period applicable across all jurisdictions (typically five to seven years post-relationship), and the data must be indexed to support regulator requests and internal investigations.
Transaction monitoring sits on top of the data layer. The monitoring system must screen every transaction against sanctions lists (OFAC, UN, EU, UK), score the transaction for typology risk (structuring, layering, rapid movement through multiple jurisdictions), and flag transactions to or from high-risk counterparties. The Travel Rule obligation is embedded in the monitoring logic: a transaction that fails to generate compliant originator and beneficiary data is blocked automatically, escalated to the compliance desk, and either completed after manual intervention or rejected. The record of the block, the reason, and the resolution is the audit trail.
Vendor selection is a risk decision. Several blockchain-analytics firms offer Travel Rule modules that integrate with exchange APIs, screen destination addresses, and generate IVMS-compliant messages. The vendors differ in coverage (how many blockchains they support, how many counterparty VASPs are in their directory) and in the quality of their sanctions screening. A false negative – a transaction to a sanctioned address that the vendor missed – is the VASP's liability, not the vendor's. The contract must allocate that risk, and the VASP's internal controls must include a secondary check (a different vendor or a manual review) for high-value or high-risk transactions.
The money-laundering reporting officer (MLRO) is the linchpin. In most jurisdictions, the MLRO must be an employee, not a contractor; must have direct access to the board; and must have authority to block transactions and to override commercial pressure. For a crypto VASP, the MLRO must also understand on-chain mechanics: how a mixer works, what a peel chain is, how layer-2 rollups complicate tracing. A traditional banking MLRO without crypto literacy will miss the red flags. Several regulators now expect the MLRO to hold a recognized AML qualification and to complete continuing education specific to virtual assets. The annual compliance attestation increasingly requires the MLRO to certify not only that policies exist but that they were tested under realistic scenarios during the reporting period.
Common mistakes that turn a Travel Rule gap into a regulatory crisis
The first mistake is treating the Travel Rule as a once-off implementation project. The rule is a moving target. Thresholds change, messaging standards evolve, and counterparty VASPs join or leave the network. A compliance architecture that was adequate in 2024 may be deficient in 2026 if it was not built for iteration. Operators we advise routinely discover that their transaction-monitoring vendor stopped updating its sanctions list, that their IVMS integration broke after a protocol upgrade, or that their bilateral agreements with counterparty VASPs lapsed and were never renewed. The absence of a quarterly compliance review – a structured check of the data flows, the vendor integrations, and the policy vs. practice gap – is the most common precursor to an enforcement action.
The second mistake is geographic complacency. A VASP that complies fully with the Travel Rule in its home jurisdiction but does not comply in the jurisdictions where its users sit, where its custody partner operates, or where its banking flows through is non-compliant in the eyes of the strictest regulator. Several enforcement actions have turned on this point: a European VASP passporting into Germany was sanctioned not for its conduct in the home state but for its failure to apply Travel Rule processes to transactions routed through a Swiss custodian. The legal theory was that the German regulator's jurisdiction extended to any transaction involving a German user, regardless of where the infrastructure sat. The defence – that Swiss law governed the custodian – failed because the VASP had contractual control over the data flow and chose not to exercise it.
The third mistake is assuming that a Travel Rule breach is self-curing. It is not. If a VASP discovers that it transmitted incomplete beneficiary data for six months, the regulator's expectation is that the VASP conducts a lookback, re-collects the missing data from customers (or from counterparty VASPs), resubmits the corrected records, and files a voluntary disclosure. The lookback is expensive, disruptive, and often impossible (customers have closed accounts, counterparty VASPs have no record, blockchain addresses have been abandoned). The alternative – silence – converts a remediable compliance gap into a cover-up and typically results in a sanction an order of magnitude larger than the original breach would have triggered.
When to engage counsel: before the licence, not after the audit
The optimal time to map Travel Rule obligations is before the VASP applies for a licence, not after the regulator opens a thematic review. A pre-licence assessment identifies the jurisdictions that matter (where the entity sits, where users are, where custody lives, where banking flows), maps the strictest standard across those jurisdictions, and designs the data and monitoring architecture to that standard. The cost is front-loaded: higher onboarding friction, longer time-to-market, and the need to contract with a transaction-monitoring vendor before revenue is flowing. The alternative cost – a failed licence application, a post-licence remediation order, or a sanction that closes correspondent banking – is larger and less predictable.
For a VASP already operating, the trigger to engage counsel is not a regulator notice but an internal control failure: a monitoring alert that was not investigated, a counterparty VASP that stopped accepting data, a high-value transaction that bypassed Travel Rule checks. These are the events that surface in a thematic review and that convert a technical compliance question into a fitness question. A voluntary disclosure, made before the regulator discovers the issue, changes the conversation. The disclosure demonstrates that the VASP's internal controls functioned (the issue was caught), that management took it seriously (counsel was engaged, a remediation plan was drafted), and that the business is committed to compliance (resources were allocated, timelines were set). The regulator's response to a voluntary disclosure is typically a request for quarterly progress reports, not a sanction.
The process above assumes known facts. If your transaction flows cross three regulators, if a recent audit surfaced gaps, or if a licensing application is pending and the Travel Rule chapter is incomplete, map it with counsel before you file. For a scoped assessment of where your stack stands today and what must change to survive the next thematic review, contact OBOLUS at info@oboluslaw.com.
The forward view: where Travel Rule enforcement is heading in 2026 and beyond
Three trends will define Travel Rule enforcement over the next two years. First, the zero-threshold model will spread. Jurisdictions that currently apply a 1,000-euro or 1,000-dollar threshold are under pressure from the Financial Action Task Force to lower it or eliminate it entirely, on the theory that structuring – breaking large transfers into sub-threshold pieces – is trivial on-chain and renders a high threshold meaningless. The EU's choice to go to zero is the template; other leading hubs will follow. The effect is that VASPs must build for zero-threshold compliance now, even if their home jurisdiction has not yet adopted it, because the cost of re-engineering later is prohibitive.
Second, regulators will shift from process enforcement to outcome enforcement. The question in a 2026 audit will not be whether the VASP has a Travel Rule policy; it will be whether the policy prevented illicit funds from moving through the platform. Regulators are beginning to measure effectiveness: the percentage of high-risk transactions that were blocked, the time between an alert and an investigation, the rate at which the VASP's monitoring system generates false positives. A VASP that can demonstrate a low false-positive rate, a high interdiction rate, and a credible process for investigating marginal cases will pass the review. A VASP that cannot produce those metrics – because the data was not logged, the alerts were not triaged, or the outcomes were not tracked – will not.
Third, cross-border coordination will intensify. Regulators in the major hubs are sharing information on VASP compliance through the Egmont Group, through bilateral memoranda of understanding, and increasingly through real-time data-sharing platforms. A compliance failure in Singapore may surface in a European supervisor's risk assessment within weeks. A sanctions breach in Switzerland may trigger a New York banking inquiry. The effect is that Travel Rule compliance is no longer jurisdiction-by-jurisdiction; it is a single global standard enforced by whichever regulator has the strongest interest in the transaction. The defence is to build to the highest standard everywhere, treat every jurisdiction as if its regulator has full visibility, and assume that a breach in one market will be known in all markets within the quarter.
Related at OBOLUS
- Compliance, AML & Travel Rule for Digital-Asset Businesses – The practice page for VASPs building or defending a compliant AML architecture across licensing, transaction monitoring and regulatory relationships.
- Self-Hosted Wallet Transfers Under the Travel Rule – Where the Travel Rule applies to withdrawals to unhosted wallets, what verification is expected, and how to structure the risk assessment.
- Regulator AML Audit Defence in British Virgin Islands – Preparing for and responding to a Financial Services Commission thematic review of AML controls at a BVI-licensed VASP.
FAQ
What does this regime require from a VASP?
The Travel Rule requires that a VASP obtain, hold and transmit to the next VASP in the transaction chain specified data on the originator and beneficiary. That data includes names, account numbers (or transaction references), and addresses or national identity numbers. The threshold at which the obligation applies varies by jurisdiction – from zero in the EU to a FATF-baseline level in most other hubs. The VASP must also screen transactions against sanctions lists, apply risk-based monitoring, and block or escalate high-risk flows. The mechanics – data format, messaging protocol, real-time vs post-transmission exchange – are set by the regulator in each market.
Who must act as MLRO for a crypto firm?
The money-laundering reporting officer must typically be an employee with direct board access and authority to block transactions. Most regulators require that the MLRO hold a recognized AML qualification and that they understand the specific risks of virtual assets – on-chain tracing, mixer typologies, cross-border flows through unregulated entities. A traditional banking MLRO without crypto training is unlikely to satisfy the regulator's fitness expectation. The MLRO is personally accountable for the annual compliance attestation and, in several jurisdictions, may face a prohibition order if the VASP's AML controls fail.
How do regulators audit crypto AML programs?
A thematic review typically requests the transaction-monitoring system's configuration, a sample of high-risk alerts and how they were resolved, evidence of Travel Rule data transmission to counterparty VASPs, and the MLRO's quarterly reports to the board. The regulator tests whether the system works under realistic scenarios – a transaction to a sanctioned address, a large withdrawal to a self-hosted wallet, a customer with a PEP flag. The audit is outcome-focused: not whether a policy exists but whether it prevented illicit flows. A VASP that cannot demonstrate a functioning system, with logs and metrics, fails the review regardless of how comprehensive the written policy is.
About OBOLUS
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 structure licensing, banking and tax as one mandate rather than three disconnected workstreams. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – Victor specializes in the interplay between AML/CFT obligations and licensing regimes for VASPs across the major hubs, with a focus on transaction monitoring and cross-border data flows.
Disclaimer: 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.