EST · MMXXVI
Home/Insights/Regulatory/Self-Hosted Wallet Transfers Under the Travel Rule
Compliance, AML & Travel Rule

Self-Hosted Wallet Transfers Under the Travel Rule

Self-Hosted Wallet Transfers Under the Travel Rule. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagements. T

A payment company running an exchange in the EU discovers that a user wants to withdraw stablecoins to a private wallet address the user controls – no intermediary, no counterparty VASP to receive originator data. The compliance desk asks: does the Travel Rule apply? If so, what data must we collect, how do we verify it, and what happens if the user refuses? Across MiCA, VARA, MAS and the FCA, regimes now expect VASPs to apply risk-based controls even when the counterparty is a self-hosted wallet. The legal question turns on what "obtain and hold" means when there is no regulated entity on the other side, and on whether asking a retail user for proof of control crosses into prohibited user surveillance. This analysis traces the three verification models in use, the privacy boundaries that constrain them, and the enforcement lens through which regulators assess your approach when a self-hosted transfer later surfaces in a sanctions or fraud investigation.

The Travel Rule – born as FATF Recommendation 15 – obliges VASPs and other obliged entities to pass originator and beneficiary information with each virtual-asset transfer. When both sender and receiver are VASPs, the obligation is bilateral and the technical plumbing exists: the TRUST framework, TRP, Notabene and similar messaging protocols transmit the data in parallel with the on-chain transaction. But when the counterparty is a self-hosted wallet – a user holding private keys on a hardware device or a non-custodial software wallet – there is no institution on the other side to receive the payload. Regulators nevertheless expect the originating VASP to collect and hold information sufficient to reconstruct the transaction chain, to assess the risk that the self-hosted address belongs to a sanctioned actor or represents a structuring attempt, and to file a suspicious-activity report if thresholds are met. Three models have emerged: the collect-and-hold approach (MiCA, Singapore, Hong Kong), the enhanced due-diligence escalation (VARA, the FCA), and the outright ban or ceiling on self-hosted transfers (proposed in some jurisdictions, not yet law). In our cross-border compliance practice, operators routinely face the intersection of these models when a user base spans multiple hubs and the VASP must reconcile conflicting requirements without losing customers or exposing the firm to a later enforcement finding that controls were insufficient.

What the Travel Rule requires – and where it stops

The Travel Rule requires that a VASP obtain and hold information about the originator and the beneficiary of a virtual-asset transfer. For originator data, this is straightforward: the sending VASP already holds KYC on its own customer. For beneficiary data when the recipient is another VASP, the obligation is to transmit the payload to that counterparty and confirm receipt. When the beneficiary is a self-hosted wallet, the transmission step becomes impossible because no regulated counterparty exists to acknowledge the data. FATF guidance recognizes this gap but stops short of prescribing a single global solution. Instead, it directs VASPs to take a risk-based approach: obtain beneficiary information "where feasible," assess the risk of the transaction, and apply enhanced due diligence or refuse the transaction if risk cannot be mitigated. National regimes have interpreted "where feasible" differently, producing a spectrum of compliance standards.

Under MiCA and the implementing regulations expected through ESMA's Level 2 measures, a VASP must collect the name and wallet address of the beneficiary for every outbound transfer, including transfers to a self-hosted wallet. The user declares this information, and the VASP holds it for at least five years. MiCA does not mandate cryptographic proof of wallet ownership for every transaction, but it does require that the VASP assess whether the declared address is plausible and whether the transaction profile – amount, frequency, destination – raises money-laundering or sanctions risk. If the beneficiary is the customer's own self-hosted wallet, the VASP may apply a simplified due-diligence standard after verifying ownership once, typically through a signature challenge or a test deposit. If the beneficiary is a third party, the VASP must obtain that third party's name and address from the customer and assess the consistency of the transaction with the customer's stated business purpose. This is the collect-and-hold model: no obligation to verify every claim in real time, but an obligation to document the data and act if red flags emerge.

Singapore's MAS and Hong Kong's SFC follow a similar line. MAS guidance on the Payment Services Act specifies that a DPT licensee must collect beneficiary information for self-hosted transfers and must verify it "on a risk-sensitive basis." Transactions over a stated threshold, or transactions exhibiting unusual patterns, trigger enhanced checks. The SFC's conduct standards for VATPs include parallel expectations: collect, hold, assess risk, escalate if warranted. Neither MAS nor the SFC prescribe a single verification method, allowing VASPs to deploy cryptographic proofs, chain analytics or manual document review depending on the risk tier.

VARA in Dubai takes a different tack. The VARA Compliance and Risk Management Rulebook requires that a licensed VASP "identify and verify" the beneficiary of a self-hosted transfer before execution. Verification must be commensurate with the money-laundering and terrorist-financing risk the transaction presents. For high-value or high-risk transfers, VARA expects cryptographic proof of wallet ownership – such as a signed message from the private key – or corroborating documentation that the declared beneficiary controls the address. For routine, low-value transfers to a customer's own wallet that the VASP has previously verified, a simplified check suffices. VARA has signaled in supervisory dialogue that it views unverified self-hosted transfers above a certain cumulative threshold as a compliance gap, even if no single transaction trips the wire.

The United Kingdom's FCA does not yet impose a full Travel Rule obligation – UK cryptoasset firms register under the Money Laundering Regulations rather than holding a payment-institution licence – but the FCA has stated in guidance that it expects registrants to assess the risk of self-hosted transfers and to apply enhanced due diligence where the transaction is inconsistent with the customer profile or involves a jurisdiction of concern. The FCA's approach mirrors the enhanced-due-diligence escalation model: no blanket rule, but a clear expectation that the firm can explain its risk assessment and the controls applied when a self-hosted transfer later appears in an enforcement or sanctions investigation.

To map the Travel Rule obligations that apply to your build – collecting across user jurisdictions, entity structure and payment rails – contact OBOLUS at info@oboluslaw.com. We pressure-test compliance programs against MiCA Level 2, VARA rulebooks and MAS guidance before you go live, not after a regulator flags a gap.

Verification methods: cryptographic proofs and their limits

Cryptographic proof of wallet ownership is the gold standard for self-hosted-transfer verification, and it is the method regulators point to when they want assurance that the declared beneficiary controls the address in question. The most common technique is the signature challenge: the VASP generates a random nonce, the user signs it with the private key of the self-hosted wallet, and the VASP verifies the signature on-chain or using a standard ECDSA or EdDSA verification library. A valid signature proves that the entity requesting the withdrawal holds the private key, establishing a link between the customer and the wallet. This method works well for withdrawals to the customer's own self-hosted wallet and is low-friction when the wallet software – Ledger Live, MetaMask, Trust Wallet – supports message signing natively.

The practical difficulty arises when the beneficiary is a third party. If a customer wants to send crypto to a business partner's self-hosted wallet, the VASP cannot demand that the third party interact with the VASP's verification system without creating a new customer relationship. The VASP must instead rely on the customer's declaration of the third party's identity and address, supplemented by documentary evidence if the amount or risk profile warrants it. This is where the collect-and-hold model acknowledges its limit: verification is feasible for own-wallet transfers, less so for third-party transfers, and the risk assessment becomes the primary control.

A second verification method is the test deposit: the VASP sends a small amount to the declared address and asks the customer to confirm receipt or return the amount, proving access. This method is slower – on-chain settlement can take minutes to hours depending on the blockchain – and it imposes a cost on the VASP or the customer. It is typically reserved for the first withdrawal to a new address or for high-value transactions where the VASP's risk policy demands corroboration beyond a signature.

Chain analytics firms – Chainalysis, Elliptic, TRM Labs – offer a third approach: address screening and clustering. The VASP submits the destination address to the analytics platform, which returns a risk score based on known associations with mixers, darknet markets, sanctioned entities or addresses flagged in prior investigations. If the address clusters with high-risk activity, the VASP can refuse the transfer or escalate to enhanced due diligence. This method does not verify that the customer controls the address, but it surfaces sanctions and fraud risk before the transaction executes. Most VASPs layer address screening on top of signature or test-deposit verification rather than using it in isolation.

The European Data Protection Board and national data-protection authorities across the EU have raised concerns about the privacy implications of mandatory wallet verification. Requiring a customer to disclose the addresses of self-hosted wallets – and potentially to prove ownership through a signature – creates a record linking the customer's real-world identity to on-chain activity. That record is personal data under the GDPR, and the VASP must process it lawfully, store it securely and limit retention to the prescribed AML period. Privacy advocates argue that wholesale verification of self-hosted wallets converts VASPs into surveillance nodes, chilling the use of non-custodial wallets and undermining the pseudonymity that is a design feature of many blockchains. The counterargument from regulators is that VASPs are obliged entities under the anti-money-laundering framework, and that the Travel Rule does not exempt self-hosted transfers simply because verification is inconvenient or privacy-sensitive. The tension remains unresolved in the Level 2 technical standards, and we expect continuing legal challenges to any regime that mandates cryptographic verification for every withdrawal without a risk-based carve-out.

What happens when a user refuses to provide beneficiary data

A VASP's Travel Rule policy must specify what happens when a customer refuses to provide beneficiary information or refuses to verify ownership of a self-hosted wallet. The legal default is that the VASP may refuse the transaction. MiCA, VARA and MAS all permit a VASP to decline a transfer that does not meet the firm's risk-management standards, and a customer's refusal to cooperate with due diligence is a legitimate basis for refusal. The question is whether the VASP must refuse or may allow the transaction under a higher-risk classification.

In practice, operators use tiered controls. For low-value withdrawals to an address the customer has used before, many VASPs will process the transaction even if the customer declines a fresh signature challenge, relying on the prior verification and the amount threshold to manage risk. For first-time or high-value withdrawals, refusal to verify typically results in the VASP blocking the transaction and, if the pattern repeats, exiting the customer relationship. The compliance rationale is that a customer who systematically refuses to cooperate with verification is either unsophisticated – unaware that the VASP is legally obliged to ask – or is structuring transactions to evade monitoring. Either way, the relationship presents heightened risk.

A customer who believes the VASP's verification request is unlawful or disproportionate may escalate to the regulator or to a data-protection authority. To date, such complaints have not resulted in findings against VASPs that apply verification in a risk-based manner, but the absence of enforcement does not mean the issue is settled. As MiCA's Level 2 standards take effect, we expect test cases in member states where privacy advocacy is strong – Germany, the Netherlands – and where a regulator's interpretation of "risk-based" may be more protective of customer autonomy than ESMA's baseline.

The transaction-monitoring overlay: when to file a SAR

Collecting and holding beneficiary data for a self-hosted transfer is step one. Transaction monitoring is step two. A VASP must assess whether the transaction, taken with the customer's profile and history, raises money-laundering, terrorist-financing or sanctions risk sufficient to trigger a suspicious-activity report. The monitoring rules do not change because the destination is a self-hosted wallet; if anything, regulators view self-hosted transfers as higher-risk because the absence of a counterparty VASP means reduced transparency downstream.

Common red flags for self-hosted transfers include: large or frequent withdrawals immediately after deposit (possible layering), withdrawals to addresses that cluster with known mixers or tumblers, withdrawals that fragment into multiple small amounts to different addresses (structuring), and withdrawals that follow a pattern inconsistent with the customer's declared business purpose. If the destination address appears on a sanctions list – OFAC's SDN list, the EU financial-sanctions list, the UK sanctions list – the VASP must block the transaction and file a report. If the address does not appear on a list but the analytics platform flags it as high-risk, the VASP must decide whether to refuse, delay for enhanced due diligence, or process and monitor. That decision must be documented, and the analysis must show that the VASP weighed the available information and applied a consistent standard.

Regulators audit AML programs by reviewing the VASP's policies, testing a sample of transactions and checking whether SARs were filed where the facts warranted. In enforcement actions arising from self-hosted transfers, the recurring finding is not that the VASP failed to collect beneficiary data, but that the VASP collected the data and then failed to act on obvious red flags. A signature alone does not discharge the duty to monitor; it proves the customer controls the wallet, not that the wallet is being used for legitimate purposes.

Cross-border conflicts: when one regime bans and another allows

Some jurisdictions have proposed outright restrictions on self-hosted transfers. Draft legislation in India and in certain EU member states at various times has included provisions that would prohibit VASPs from processing withdrawals to self-hosted wallets or that would cap such transfers at a low threshold. As of the latest verified information, none of these proposals has become final law at the national level, and MiCA itself does not ban self-hosted transfers. But the regulatory direction in some quarters is toward greater restriction, and operators must plan for the possibility that a ban becomes law in a jurisdiction where they have users.

If a VASP is licensed in a jurisdiction that allows self-hosted transfers but has customers in a jurisdiction that restricts or bans them, the VASP faces a conflict-of-laws problem. The licensing jurisdiction may permit the transaction, but processing it could expose the VASP to enforcement in the customer's home jurisdiction or could require the VASP to exit that customer base. The reverse conflict – licensed in a restrictive jurisdiction but serving customers in a permissive one – typically resolves in favor of the stricter rule: the VASP applies the home-state restriction to all customers to avoid licensing risk. These conflicts are a reason why the single-licence, serve-the-world model breaks down once a VASP reaches scale. The legal stack must be built jurisdiction by jurisdiction, and the compliance program must route transactions according to the applicable regime.

VARA, MAS, the MFSA and other leading regulators expect a licensed VASP to apply host-state rules to customers resident in that state, even if the VASP's home licence is more permissive. If a customer in a restrictive jurisdiction uses a VPN or a nominee to access a platform licensed elsewhere, the VASP's KYC and geofencing controls are the first line of defense. If those controls fail and the transaction processes, the VASP's risk is enforcement in the restrictive jurisdiction and potential loss of banking or correspondent relationships.

Practical program design: a four-tier model

A robust self-hosted-transfer policy structures controls by risk tier rather than applying the same verification standard to every transaction. The model we see in well-designed programs has four tiers, each with escalating checks.

Tier 1: own-wallet, previously verified, low value. The customer has verified ownership of the self-hosted address in a prior transaction, the cumulative withdrawal to that address over a rolling period remains below a stated threshold, and the transaction profile is consistent with the customer's KYC. No fresh verification required; the VASP processes the withdrawal with standard address screening. If the address now flags as high-risk, escalate to Tier 3.

Tier 2: own-wallet, first-time or periodic re-verification. The customer declares the address as their own, and the VASP requires a signature challenge or test deposit to confirm. Once verified, the address moves into the Tier 1 pool for future transactions. Re-verification may be required annually or after a prolonged period of inactivity.

Tier 3: third-party beneficiary, or high value. The customer declares that the destination address belongs to a third party, or the amount exceeds the high-value threshold for the jurisdiction. The VASP collects the third party's name and address, assesses the business purpose, runs enhanced chain analytics, and documents the decision to proceed. If the risk cannot be mitigated, refuse the transaction.

Tier 4: sanctions hit or persistent high-risk flags. The address appears on a sanctions list, clusters with a designated entity or exhibits a pattern consistent with structuring or mixing. Block the transaction, file a SAR if the threshold is met, consider exiting the customer relationship. Tiers 3 and 4 require MLRO sign-off before processing or refusal.

The firm's policy must define the value thresholds, the re-verification schedule, the chain-analytics risk score that triggers escalation, and the documentation standard for Tier 3 approvals. These definitions should align with the VASP's overall risk appetite and with the requirements of the licensing jurisdictions in which the VASP operates.

The MLRO function and accountability for self-hosted controls

Every VASP operating under MiCA, VARA, MAS or equivalent must appoint a money-laundering reporting officer (MLRO) or equivalent compliance officer. The MLRO is responsible for the design, implementation and testing of the AML program, including the self-hosted-transfer controls. When a regulator examines a VASP's Travel Rule compliance, the engagement begins with the MLRO: show us the policy, show us the training records, show us the transaction-monitoring alerts and the decisions made on escalated cases. If self-hosted transfers have been processed without adequate controls, the MLRO is the accountable individual.

The MLRO role cannot be outsourced in its entirety, but the technical verification steps – signature validation, chain analytics, sanctions screening – can be performed by third-party service providers under the MLRO's oversight. The MLRO must satisfy themselves that the provider's methodology is sound, that the data is current and that the risk scores align with the firm's policy. A common mistake is to adopt a chain-analytics platform and then fail to tune the alert thresholds to the VASP's customer base, resulting in either alert fatigue – hundreds of false positives a day – or under-detection. The MLRO's job includes that tuning and the periodic back-testing of the monitoring rules against known typologies.

Regulators increasingly expect the MLRO to be senior, independent and empowered to stop a transaction or exit a customer without needing board or commercial approval. In our compliance practice, we see this expectation codified in the licensing conditions for VASPs in VARA, the ADGM, Malta and Singapore. The person holding the MLRO designation must have direct access to the board, must report at least quarterly on ML/TF risk and control effectiveness, and must have a clear escalation path when commercial pressures conflict with compliance judgment.

When a self-hosted transfer surfaces in an investigation

The test of a VASP's self-hosted controls comes not during routine operations but when law enforcement or a regulator traces criminal proceeds or sanctions evasion through the firm's platform. A typical scenario: funds stolen from a DeFi protocol are laundered through a series of on-chain hops, one of which involves a deposit to the VASP, a brief hold, and a withdrawal to a self-hosted wallet. Months later, investigators issue a production order or a regulatory information request asking for the identity of the account holder, the beneficiary information for the withdrawal, and the VASP's assessment of the transaction at the time it was processed.

If the VASP collected beneficiary data, verified the wallet or documented a risk-based decision not to verify, and ran the transaction through its monitoring system, the firm can produce a complete record and demonstrate that it acted consistently with its policy. If the VASP did not collect beneficiary data – or collected it but stored it in an ad-hoc spreadsheet that no longer exists – the firm has a disclosure problem and an enforcement risk. The regulator's question will be: why was this transaction not flagged? Even if the firm's monitoring rules were reasonable at the time, the failure to document the decision makes it difficult to prove reasonableness after the fact.

In fraud and asset-recovery matters, the victim's lawyers often seek a Norwich Pharmacal or Bankers Trust disclosure order compelling the VASP to produce account and transaction records. The VASP's obligation is to comply with the order and to disclose what it holds. If the VASP did not collect beneficiary information for the self-hosted transfer, it cannot produce what it does not have, and the recovery chain may end at the VASP's platform. Regulators view this outcome as a systemic weakness: the absence of beneficiary data for self-hosted transfers creates a transparency gap that criminals exploit. The direction of regulatory policy is to close that gap, not to accept it as an inherent feature of non-custodial wallets.

Objection handler: won't verification requirements kill self-hosted adoption?

A common assumption is that imposing Travel Rule obligations on self-hosted transfers will drive users away from regulated VASPs and toward peer-to-peer trading, offshore platforms or DeFi protocols that do not collect KYC. The concern is that verification requirements conflict with the ethos of self-custody and that users who value privacy will exit the regulated ecosystem rather than submit to disclosure. This concern is not unfounded – there is evidence of users migrating to platforms with lighter KYC when compliance burdens increase – but it overstates the dilemma and misreads the regulatory objective.

Regulators are not trying to eliminate self-hosted wallets. They are trying to ensure that VASPs know their customers and can reconstruct the transaction chain when criminal activity is detected. A risk-based verification regime does not require proof of ownership for every transaction; it requires that the VASP assess the risk and apply controls commensurate with that risk. For most retail users making low-value withdrawals to their own wallets, a one-time signature challenge and periodic address screening is sufficient. For high-value or third-party transfers, enhanced checks are reasonable and consistent with the due diligence banks apply to wire transfers.

The alternative – no Travel Rule for self-hosted transfers – would create an unregulated off-ramp that criminals and sanctions evaders would systematically exploit. Regulators have made clear that they will not tolerate that outcome. The policy question is not whether to regulate self-hosted transfers, but how to do so in a way that is proportionate, technically feasible and privacy-respecting. The evidence from Singapore, the UAE and the EU is that a well-designed risk-based program can achieve those goals without driving legitimate users out of the regulated space. Operators who frame compliance as binary – either no controls or total surveillance – miss the middle ground where effective AML and user experience coexist.

If a prior registration stalled or an account was closed because your Travel Rule program did not cover self-hosted transfers, a structured gap-closure plan can bring the firm back into compliance and restore access to banking and payment rails. OBOLUS maps the gaps and builds the remediation roadmap before you re-engage the regulator or the bank. Write to info@oboluslaw.com.

Decision matrix: which verification method for which profile

Choosing a verification method depends on the customer profile, the transaction type, the risk appetite and the technical capabilities of the VASP's platform. The decision matrix we advise clients to use breaks down as follows.

Customer: retail, low-volume. Own-wallet withdrawals processed with a one-time signature challenge and standard address screening. No fresh verification for repeat withdrawals below a cumulative monthly threshold. Third-party beneficiary withdrawals require name and address declaration and enhanced analytics; refuse if the address flags high-risk.

Customer: institutional or high-net-worth. Own-wallet withdrawals require signature or test deposit at each new address, plus quarterly re-verification. Third-party beneficiary withdrawals require documentary evidence of the business relationship, enhanced analytics, and MLRO sign-off above a stated value. Tier-1 addresses (exchanges, known custodians) receive lighter treatment; unknown addresses receive the full Tier 3 process.

Jurisdiction: MiCA member state. Collect and hold beneficiary information for all withdrawals. Verify ownership on a risk-sensitive basis; document the basis for the risk assessment. Re-verify at least annually for high-value or high-frequency users. Apply enhanced checks if the customer is a PEP or the transaction involves a high-risk third country.

Jurisdiction: VARA (Dubai). Verify beneficiary information before execution for transactions above the relevant threshold or where risk is elevated. Use signature challenge or corroborating documentation. Refuse if verification cannot be completed. Document the decision in the transaction record.

Jurisdiction: Singapore (MAS). Collect beneficiary information and assess risk. Verify on a risk-sensitive basis; enhanced checks for major payment-institution licensees or for transactions that meet the suspicious-transaction criteria. Use chain analytics as primary screen; signature or test deposit for secondary corroboration.

Jurisdiction: offshore (BVI, Cayman). The local VASP regime may not yet specify self-hosted verification standards, but banks and correspondent institutions increasingly expect MiCA-equivalent controls. Apply a risk-based verification program aligned with FATF guidance to preserve banking relationships. If the customer base includes EU or US persons, apply the stricter of the home or host regime.

Related at OBOLUS

FAQ

What does this regime require from a VASP?

The regime requires that a VASP collect and hold originator and beneficiary information for every virtual-asset transfer, including transfers to self-hosted wallets. The VASP must verify beneficiary information on a risk-sensitive basis, apply transaction monitoring to detect money-laundering or sanctions risk, and file a suspicious-activity report if thresholds are met. The specific verification method – signature challenge, test deposit, documentary evidence – depends on the risk profile of the transaction and the requirements of the licensing jurisdiction. A VASP may refuse a transfer if the customer will not provide the required information or if the risk cannot be mitigated.

Who must act as MLRO for a crypto firm?

The money-laundering reporting officer must be a senior individual with compliance expertise, independence from commercial pressures, and direct access to the board. The MLRO is responsible for designing and testing the AML program, training staff, investigating alerts, filing suspicious-activity reports, and liaising with the regulator. The role cannot be outsourced entirely, though technical tasks such as transaction monitoring and chain analytics may be performed by third-party providers under the MLRO's oversight. Licensing regimes in VARA, Singapore, Malta and the EU require that the MLRO be approved by the regulator and that the individual meet fit-and-proper standards.

How do regulators audit crypto AML programs?

Regulators audit a VASP's AML program by reviewing policies and procedures, testing transaction-monitoring rules, examining a sample of customer files and escalated cases, and interviewing the MLRO and compliance staff. The auditor checks whether the firm's risk assessment is current, whether the monitoring thresholds align with the customer base and the risk appetite, whether SARs were filed where the facts warranted, and whether the firm acted on red flags in a timely manner. For self-hosted transfers, the auditor will ask to see the verification records, the chain-analytics reports, and the documentation for any high-risk transaction that was approved or refused. A finding that the firm collected data but failed to act on obvious indicators is more serious than a finding that the verification process was under-resourced but consistently applied.

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 entirety of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we pressure-test compliance programs against the latest regulatory guidance before you engage the regulator. To discuss your situation, contact info@oboluslaw.com.

By Victor Olsen, Regulatory & Compliance Analyst – Specialist in Travel Rule implementation, transaction-monitoring program design and cross-border AML compliance for virtual-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.

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