EST · MMXXVI
Home/Services/Compliance, AML & Travel Rule/Sanctions Compliance for Crypto Businesses
Compliance, AML & Travel Rule

Sanctions Compliance for Crypto Businesses

Sanctions Compliance for Crypto Businesses. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagements. Talk to O

An exchange processing withdrawals to a sanctioned address discovers the transaction forty-eight hours after settlement. The compliance desk flags the counterparty – a mixer that appeared on OFAC's SDN list three weeks earlier – but the screening rule had not updated. The regulator's inquiry arrives within days, and the questions turn immediately to the firm's sanctions architecture: what was screened, when the list was refreshed, who approved the override and why the designation change was not caught in real time.

Sanctions compliance for a digital-asset business is not a static checklist. It is a continuous process of screening wallets and counterparties against evolving lists, tracking mixer exposure across on-chain hops, managing designation updates as they are published and escalating hits through a documented decision path. The exposure sits at three pressure points: the customer onboarding gate, the transaction monitoring layer and the counterparty due-diligence refresh. A gap at any of the three exposes the business to regulatory action, payment-rail suspension and reputational damage that can close banking relationships before an explanation is filed. In our cross-border practice, operators who treat sanctions as an add-on to KYC – rather than a parallel, equally rigorous control – discover the cost when a single missed designation triggers a regulator review or a correspondent bank freezes the operating account.

This page sets out the sanctions-compliance framework a digital-asset business needs: the screening architecture, the wallet and counterparty controls, the mixer and chain-hop risk model, the designation-change workflow and the escalation protocol that turns a potential breach into a documented, defensible response. It addresses the regime expectations across OFAC, EU sanctions, UN designations and the jurisdiction-specific lists that apply when a business serves users or banks in multiple territories. It is written for general counsel, compliance officers and founders building or pressure-testing the program before a regulator audit or a banking due-diligence review surfaces a structural weakness.

What sanctions compliance means for a crypto business

Sanctions compliance for a digital-asset operator means maintaining real-time controls that prevent the firm from transacting with designated persons, entities or addresses and from facilitating transfers that touch sanctioned wallets or jurisdictions. The obligation arises under the sanctions regimes of the jurisdictions where the business is licensed, where it banks and where its users sit. For a VASP licensed in the EU and banking in Switzerland while serving customers across Asia and the Middle East, that means parallel compliance with EU sanctions, OFAC's Specially Designated Nationals (SDN) list, UN Security Council designations and the national lists of any jurisdiction material to the user base or the banking relationship.

The screening obligation extends beyond the customer. A compliant program screens the customer at onboarding, the beneficiary and originator of every transaction under the Travel Rule, the counterparty wallets the platform interacts with and the intermediate addresses a chain-analysis tool reveals in the transaction graph. Where an address has interacted with a mixer, a sanctioned exchange or a wallet on a public blacklist, the compliance function must assess the exposure, decide whether to block or escalate and document the rationale. Regulators expect this analysis to happen before settlement, not after.

In our practice advising exchanges and custodians across the major licensing hubs, we see three recurring structural gaps. First, the sanctions-screening rule set is updated manually rather than through an automated feed, leaving a window where newly designated entities are not caught. Second, the chain-analysis integration stops at the immediate counterparty rather than tracing exposure through mixers or layered hops. Third, the escalation protocol lacks a documented decision matrix, so a compliance officer facing a potential hit has no clear authority threshold or approval path. Each of these gaps is discoverable in a regulator audit and each has led to enforcement action in recent cases across multiple jurisdictions.

The applicable sanctions regimes

The sanctions landscape for a cross-border digital-asset business is a composite of overlapping frameworks. OFAC administers U.S. sanctions and publishes the SDN list, which applies to any transaction touching the U.S. financial system, any U.S. person and, under secondary sanctions, to non-U.S. persons transacting with designated parties in certain programs. The EU maintains its own consolidated sanctions list, which binds EU-licensed VASPs and any entity operating within EU member states. The UN Security Council issues designations under country-specific and thematic programs; member states transpose these into domestic law. National regulators – FINMA in Switzerland, MAS in Singapore, the FCA in the United Kingdom – expect compliance with their own lists in addition to OFAC and UN designations where those apply.

For a VASP, the governing set is determined by three factors: the licensing jurisdiction, the banking jurisdiction and the user base. A Dubai-licensed exchange banking in the UAE but serving European customers must screen against UAE federal sanctions, OFAC (if any transaction chain touches U.S. correspondent banks) and EU sanctions (because the users sit in the EU). The safest model is a union set – screen against all material lists – but this requires list-management infrastructure that can update in near-real-time as designations are published.

The Travel Rule adds a second layer. When a VASP transmits originator and beneficiary data under the Travel Rule, it must screen both parties not only at the moment of the transaction but on an ongoing basis if the relationship is recurring. A beneficiary wallet that was clean at the time of the first transfer may appear on a sanctions list weeks later; the compliance function must retroactively assess whether the relationship should be terminated and whether a suspicious-activity report is required. This retroactive screening obligation is explicit in the FATF guidance and in the supervision expectations of regulators in the EU, Singapore and Hong Kong.

Screening architecture: real-time, automated and layered

A defensible sanctions-screening architecture for a digital-asset platform operates at three gates. The first gate is customer onboarding: every applicant is screened against the sanctions lists and against adverse-media and PEP databases before the account is approved. The second gate is transaction initiation: every withdrawal, deposit and transfer is screened at the moment the user submits it, before it reaches the blockchain. The third gate is ongoing monitoring: customer records and counterparty wallets are rescreened on a defined cadence – daily for high-risk customers, weekly for standard accounts – and immediately when a designation change is published.

The screening logic must be automated and must draw from a maintained feed of the applicable sanctions lists. Manual updates – downloading a list from OFAC's website each week and uploading it to the compliance platform – create a gap between the designation date and the screening update. Regulators expect same-day or next-day incorporation of new designations. The architecture we design for clients integrates a commercial sanctions-data provider that pushes list updates to the screening engine in near-real-time, with a backup manual check on the day a major designation is announced.

The screening must be layered to account for obfuscation techniques. A designated person may use a variant name, a transliterated alias or a corporate vehicle not explicitly listed but controlled by the designated entity. The screening engine must employ fuzzy matching, alias expansion and beneficial-ownership lookthrough where the customer is a legal entity. Where the platform accepts fiat on-ramps or off-ramps, the bank-account holder must be screened separately from the platform account holder; a mismatch is a red flag for a potential sanctions evasion or a layering scheme.

For wallet-to-wallet platforms and DeFi protocols with a compliance layer, the challenge is address-based screening. A wallet address does not carry a name. The compliance function must screen the address itself against public sanctions lists – OFAC's SDN digital-currency addresses, Chainalysis's sanctions tags, Elliptic's risk scores – and must trace the transaction graph to identify mixers, sanctioned exchanges and high-risk jurisdictions in the flow. This requires integration with a blockchain-intelligence provider and a rule set that defines the exposure threshold: one hop from a mixer, two hops from a sanctioned exchange, cumulative inflow from high-risk sources over a defined period. The rule set is jurisdiction-specific; a VASP operating in the EU under MiCA will face stricter exposure limits than one operating in a jurisdiction with a principles-based AML regime.

If your screening architecture was designed before the recent mixer designations or before the Travel Rule took effect in your licensing jurisdiction, a compliance audit can surface the gap before a regulator does. For a scoped assessment of your sanctions controls and the integration roadmap, contact OBOLUS at info@oboluslaw.com.

Mixer exposure and chain-hop risk

The designation of Tornado Cash by OFAC and the enforcement actions against mixers in multiple jurisdictions have created a new compliance question: how many hops away from a mixer must a transaction sit before it is acceptable? A wallet that received funds directly from Tornado Cash is clearly exposed. A wallet that received funds from another wallet that had received from Tornado Cash – a two-hop separation – presents a judgment call. The compliance function must define the exposure policy in writing, apply it consistently and document every decision where the transaction is approved despite a mixer link.

The policy we recommend to clients is a tiered model. Direct interaction with a designated mixer – funds into or out of the mixer within the transaction history – is an automatic block. One-hop separation triggers a manual review: the compliance officer examines the counterparty's profile, the transaction size, the frequency of the relationship and the business rationale. If the exposure is incidental – the counterparty is a known exchange and the mixer-touched wallet is one of thousands in a hot-wallet pool – the transaction may proceed with documented approval. Two or more hops are generally acceptable unless other risk factors are present, but the decision threshold and the approval authority must be codified in the compliance manual.

Chain analysis must trace not only the immediate counterparty but the upstream and downstream flows. Where a user deposits from a wallet that has interacted with mixers, the compliance function assesses whether the deposit represents proceeds of a scheme to obscure origin. Where a user withdraws to a wallet that subsequently sends to a mixer, the question is whether the platform facilitated a sanctions-evasion step; this retroactive assessment is why ongoing monitoring is critical. The blockchain-intelligence provider's risk score is a starting input, but it cannot replace the judgment call. A score of sixty out of one hundred means nothing without a documented policy on what score triggers escalation, to whom and under what timeline.

Designation-change workflow

Sanctions lists change constantly. OFAC publishes updates every few weeks. The EU adds or removes entities on a rolling basis. A compliance program that does not incorporate designation changes within twenty-four hours of publication will miss a newly sanctioned counterparty if that counterparty transacts the day the list updates. The workflow must be automated where possible and must include a human escalation step for high-impact changes.

The workflow we implement for clients has four stages. First, the sanctions-data feed pushes the updated list to the screening engine the same day OFAC or the EU publishes it; the system rescreens the entire customer base and the known counterparty wallet set overnight. Second, any match is flagged for the compliance officer by morning. Third, the officer reviews the match, determines whether it is a true positive or a false positive and, if true, freezes the account or the transaction. Fourth, the officer files a suspicious-activity report with the relevant financial-intelligence unit and, if the customer is a legal entity, investigates beneficial ownership to identify other accounts that may be controlled by the same party.

The escalation protocol must define the approval authority. A low-value account frozen due to a sanctions match may be handled by the compliance officer alone. A high-value account or a counterparty wallet used by multiple customers requires executive sign-off and, in some cases, external counsel review before the account is terminated. The decision matrix – dollar thresholds, customer categories, escalation levels – must be written into the compliance manual and must be followed every time. A regulator reviewing the sanctions log will check for consistency; ad-hoc decisions raise questions about whether the program is risk-based or reactive.

Counterparty due diligence and ongoing screening

A VASP that transacts with other VASPs, liquidity providers or institutional counterparties must treat those entities as customers for sanctions purposes. Counterparty due diligence at the start of the relationship includes verifying the entity's registration or licence, screening its beneficial owners against sanctions lists and assessing the jurisdiction risk if the counterparty sits in a high-risk or non-cooperative territory. The due diligence must be refreshed annually at minimum and immediately if adverse information surfaces – a regulatory action, a change in beneficial ownership, a press report linking the counterparty to sanctioned parties.

The ongoing screening obligation applies equally to counterparties. If a liquidity provider is added to a sanctions list, every open position with that provider must be reviewed and, where required, closed or hedged. If a correspondent VASP in a foreign jurisdiction loses its licence or is subject to enforcement action, the relationship must be reassessed for AML and sanctions risk. The compliance function must maintain a counterparty risk register that tracks the refresh date, the last screening result and the next review deadline for every material relationship. A missed refresh is a gap a regulator will find when it audits the sanctions program.

Escalation protocol and breach response

A potential sanctions breach – a transaction that reached settlement before a sanctions match was identified – requires immediate escalation. The protocol must define the internal reporting line (compliance officer to general counsel to the board), the timeline for investigation (typically twenty-four to forty-eight hours for an initial assessment) and the disclosure obligations to regulators and, where applicable, to law enforcement. In most jurisdictions, a suspected sanctions breach must be reported to the financial-intelligence unit and, if the transaction involved a U.S. nexus, to OFAC's reporting office.

The response we guide clients through has five steps. First, freeze any remaining balance in the customer account and any pending transactions. Second, investigate the transaction: who initiated it, what was the purpose, was there a screening failure or a false negative in the engine. Third, file the required reports with the regulator and the financial-intelligence unit, using the timeline set by the applicable framework. Fourth, remediate the control gap: update the screening rule, retrain the compliance team, enhance the chain-analysis integration. Fifth, document the entire sequence in the compliance log, including the root-cause analysis and the corrective action, so that a regulator reviewing the matter six months later can see that the firm responded appropriately.

Where the breach is material – a large transaction, a repeat counterparty, a designated person of particular concern – external counsel should be engaged immediately. The firm's internal investigation may be privileged if conducted under legal advice, and counsel can manage the disclosure strategy to minimize the risk of cascading enforcement actions across multiple jurisdictions. A breach disclosed to OFAC may trigger parallel inquiries from the EU and from the licensing regulator; the disclosure language must be coordinated to avoid inconsistent statements that undermine the firm's position.

If a screening failure has occurred or if a regulator has requested your sanctions logs, the response timeline is short and the stakes are high. For immediate guidance on breach response and regulatory disclosure, contact OBOLUS at info@oboluslaw.com.

Cross-border sanctions conflicts and the blocking problem

A VASP operating across multiple jurisdictions faces the possibility of conflicting sanctions obligations. A customer may be sanctioned under OFAC but not under EU sanctions, or vice versa. A jurisdiction may prohibit compliance with extraterritorial sanctions – so-called blocking statutes – making it illegal for a locally incorporated entity to enforce OFAC sanctions on non-U.S. transactions. The compliance function must navigate these conflicts with a jurisdiction-by-jurisdiction analysis and, where necessary, a legal opinion on the applicable priority of laws.

The approach we take for clients with multi-jurisdictional operations is to apply the strictest standard unless a blocking statute legally prevents it. If an entity is sanctioned under OFAC but not under EU sanctions, and the VASP has any U.S. nexus – dollar clearing, a U.S. subsidiary, U.S. investors – the safest course is to freeze the relationship globally and file with OFAC. If the VASP has no U.S. nexus and operates entirely within a jurisdiction with a blocking statute, the decision turns on the risk appetite of the board and the willingness to accept that the firm will be cut off from U.S. correspondent banking if OFAC later takes enforcement action.

The blocking problem is most acute for entities incorporated in the EU but with U.S. investors or U.S.-licensed subsidiaries. The EU blocking statute prohibits compliance with certain extraterritorial U.S. sanctions, but a U.S. investor or a Delaware parent company may impose contractual obligations that require OFAC compliance. The conflict must be resolved at the entity-structure level before the first customer is onboarded; attempting to navigate it on a case-by-case basis when a sanctions match arises is too late.

What regulators look for in a sanctions audit

When a regulator audits a VASP's sanctions-compliance program, the review focuses on five areas: the comprehensiveness of the screening lists, the frequency of list updates, the quality of the risk assessment for borderline cases, the completeness of the escalation documentation and the speed of response when a designation change affects an existing relationship. The auditor will pull a sample of customer files, a sample of transactions and the sanctions-hit log for the prior twelve months. The auditor will test whether the screening engine catches a known sanctions match when fed a test case. The auditor will interview the compliance officer to assess whether the escalation protocol is understood and whether the officer has the authority and the tools to make real-time decisions.

The gaps that trigger enforcement action are rarely outright failures to screen. More often, the issue is a stale list, a missed designation update, a poorly documented decision to approve a transaction despite a mixer link or an escalation path that bypassed the compliance function. The regulator's expectation is that every decision is documented in writing at the time it is made, not reconstructed months later when the audit notice arrives. The compliance manual must be a living document, updated each time the screening rule changes, each time the mixer policy is revised and each time a new sanctions regime is added to the union set.

Common mistakes and how to avoid them

The most common mistake in sanctions compliance for digital-asset businesses is treating it as a subset of KYC rather than a parallel control with its own infrastructure. Sanctions screening requires real-time list feeds, chain-analysis integration and a retroactive review process that KYC onboarding does not demand. A second mistake is applying a binary block-or-allow rule without a documented risk-assessment step for borderline cases. A mixer-touched wallet is not automatically sanctioned, but approving the transaction without a written rationale and a named approver is a control failure. A third mistake is failing to screen counterparty wallets and intermediate hops; the compliance obligation does not stop at the customer.

A fourth mistake is assuming that a commercial screening tool eliminates the need for human judgment. The tool provides a risk score and a match probability, but the compliance officer must interpret the result in the context of the customer's profile, the transaction size and the jurisdiction risk. A high score on a small-value transaction from a low-risk customer may be a false positive; a medium score on a large-value transaction from a corporate customer in a high-risk jurisdiction may require escalation. The decision matrix must be codified, and the training program must ensure that every compliance officer understands when to escalate and to whom.

A fifth mistake is delaying the integration of designation changes. If OFAC designates a mixer on Monday and the screening engine is not updated until Friday, every transaction that week is potentially non-compliant. The update process must be automated with a manual fallback for the day a major designation is published. The compliance officer must monitor regulatory announcements daily – not weekly – and must trigger an ad-hoc rescreen of the customer base when a high-impact designation is published.

Building sanctions compliance into the tech stack

Sanctions compliance for a digital-asset platform is as much an engineering question as a legal one. The screening engine must integrate with the customer-onboarding workflow, the transaction-processing layer, the chain-analysis API and the compliance-log database. The integration must be real-time: a transaction should not reach the mempool until the screening check returns a pass result. The compliance function must have a dashboard that shows the screening status of every customer and every transaction, the date of the last list update and the number of pending escalations.

The architecture must be designed with auditability in mind. Every screening event – pass, fail, escalation, override – must be logged with a timestamp, a user identifier and a rationale field. The log must be tamper-evident and must be retained for the period required by the licensing jurisdiction, typically five to seven years. The compliance function must be able to produce the log in a regulator-readable format within twenty-four hours of a request; a system that requires manual extraction or restructuring of the data is not audit-ready.

Where the platform serves users in multiple jurisdictions or offers cross-border payments, the tech stack must support jurisdiction-specific screening rules. A transaction between two EU users may require only EU sanctions screening, while a transaction involving a U.S. counterparty or a U.S. dollar leg requires OFAC screening as well. The rule engine must apply the correct list set based on the transaction parties and the settlement chain, and the logic must be reviewable by the compliance function and by external auditors.

Self-assessment checklist

Before a regulator audit or a banking due-diligence review, a digital-asset business should verify that its sanctions-compliance program meets the following baseline:

  • The screening engine draws from an automated feed of OFAC, EU, UN and applicable national sanctions lists, with updates incorporated within twenty-four hours of publication.
  • Every customer is screened at onboarding and rescreened on a defined cadence; high-risk customers are rescreened daily.
  • Every transaction is screened before settlement; wallet addresses are screened against sanctions tags and chain-analysis risk scores.
  • The mixer-exposure policy is written, with defined thresholds for direct exposure, one-hop exposure and multi-hop exposure, and with a named approval authority for borderline cases.
  • Counterparty entities are treated as customers for sanctions purposes; beneficial owners are screened and the relationship is refreshed annually.
  • The escalation protocol defines the reporting line, the investigation timeline and the disclosure obligations for a potential sanctions breach.
  • Every screening decision – pass, block, escalation, override – is logged in a tamper-evident system with a timestamp and a rationale.
  • The compliance manual is updated each time the screening rule changes, and the team is trained on the new rule within forty-eight hours.

If any of these elements is missing or implemented only partially, the program has a material gap. The gap is discoverable in a regulator audit, and the cost of remediation after an enforcement action is significantly higher than the cost of building the control correctly from the start.

Related at OBOLUS

FAQ

What does this regime require from a VASP?

The sanctions regime requires a VASP to screen every customer, transaction and counterparty wallet against the applicable sanctions lists before the account is approved or the transaction settles. The screening must occur at onboarding and on an ongoing basis, with immediate rescreening when a designation change is published. The VASP must maintain a documented escalation protocol for potential matches, must trace mixer exposure and chain-hop risk through blockchain-intelligence tools and must file suspicious-activity reports when a sanctions breach is suspected. The obligation extends to the beneficial owners of legal-entity customers and to the intermediate wallets in a transaction chain where chain analysis reveals exposure to designated addresses.

Who must act as MLRO for a crypto firm?

The Money Laundering Reporting Officer role must be held by a senior individual within the VASP who has the authority to make compliance decisions, to escalate to the board and to file reports with the financial-intelligence unit without requiring executive approval. In most licensing jurisdictions, the MLRO must be an employee of the licensed entity, must reside in the licensing jurisdiction or be readily available to the regulator and must hold a professional qualification or demonstrated experience in AML and sanctions compliance. Some jurisdictions permit the MLRO role to be outsourced to a compliance service provider, but the accountability remains with the licensed entity. The MLRO must have direct access to the customer data, the transaction logs and the screening results, and must be named in the licence application or the regulatory filings.

How do regulators audit crypto AML programs?

Regulators audit a VASP's AML and sanctions program by reviewing the compliance manual, the screening logs, the escalation records and the suspicious-activity reports filed over a defined lookback period. The auditor will test the screening engine by feeding it a known sanctions match and will verify that the engine flagged the match and that the compliance function escalated it appropriately. The auditor will pull a sample of customer files and will check that the KYC documentation is complete, that the sanctions screening occurred at onboarding and that the customer was rescreened on the required cadence. The auditor will interview the MLRO to assess whether the escalation protocol is understood and whether the MLRO has the tools and the authority to make real-time decisions. The audit report will identify gaps and will require the VASP to remediate them within a defined timeline, typically thirty to ninety days depending on severity.

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 seventy-plus jurisdictions, on disputes and on-chain asset recovery across twenty-five-plus forums and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. Operators we advise routinely face the challenge of building compliance programs that satisfy regulators in multiple jurisdictions while remaining operationally feasible for a business processing thousands of transactions daily. 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 sanctions-compliance architecture or to pressure-test your program before a regulator audit, contact info@oboluslaw.com.

By Victor Olsen, Regulatory & Compliance Analyst – Victor specializes in AML, sanctions and Travel Rule implementation for digital-asset businesses operating across multiple licensing and banking jurisdictions.

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.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours