Electronic money institutions – EMIs (licensed entities that issue electronic money and hold client funds) – have become the critical banking layer for virtual asset service providers. Without a functioning fiat rail, a VASP (virtual asset service provider) cannot process deposits, settle withdrawals or pay counterparties. And yet, EMI onboarding for VASPs remains one of the most consistently obstructed pathways in digital-asset practice. With financial regulators across the EU, the UK and the major offshore hubs applying ever-tighter standards to the clients their supervised institutions may serve, the compliance burden has shifted decisively onto the VASP itself.
This analysis addresses that burden in full: what EMIs require, why applications stall, where the cross-border structure can break the logic of an otherwise clean application, and how a VASP's operator profile should drive its approach to fiat rails and payment infrastructure.
Why Do VASPs Struggle to Open EMI Accounts?
The short answer is that a VASP's risk profile sits at the intersection of every category of financial-crime concern that a compliance officer is trained to escalate. High transaction volumes, pseudonymous counterparties, cross-border flows, and asset classes that remain incompletely classified under national law combine to produce what EMI compliance teams call an "elevated inherent risk" profile. That classification triggers enhanced due diligence, extended review timelines, and – in a material number of cases – a flat refusal that is rarely reasoned in writing.
The structural dynamic is worth understanding. An EMI operates under a licence issued by a national regulator – the Financial Conduct Authority in the UK, a national competent authority under the MiCA regime in the EU, or an equivalent body in Singapore, Malta, or the Baltic states. That licence carries conditions, and one of the most commercially consequential is the obligation to maintain an adequate AML/CFT program. An EMI that onboards a VASP and later faces a regulatory examination will be asked to demonstrate that it understood the VASP's business, its own exposure to that business, and the controls it applied. The reputational and financial cost of getting that wrong is not abstract.
In our cross-border practice, we consistently observe that EMIs are not uniformly hostile to the sector. A well-licensed VASP, operating under a regime the EMI's compliance team recognizes, with documented controls that mirror their own obligations, stands a materially better chance of a favorable outcome than an operator presenting an offshore registration of uncertain standing. The single most consequential factor is rarely the VASP's underlying business – it is the quality of the compliance documentation presented at onboarding.
The compliance burden is real, but it is not uniform. How a VASP structures its approach to EMI onboarding determines whether the process takes weeks or becomes a multi-year source of instability.
To map the EMI onboarding requirements for your structure, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts – the entity, the user base, the banking – change the analysis entirely.
What Do EMI Compliance Teams Actually Require From a VASP?
An EMI's onboarding checklist for a VASP applicant is substantially longer and more demanding than the equivalent for a conventional payments business. The core document set is predictable: corporate structure, ownership chain, beneficial ownership declarations, the VASP's own licence or registration certificate, AML/CFT policies, a business plan with transaction projections, and source-of-funds documentation for founders. What separates a successful application from a stalled one is the quality of the second layer.
That second layer includes the VASP's Travel Rule compliance framework – the obligation, under FATF Recommendation 15 and its local implementations, to pass originator and beneficiary data alongside a virtual asset transfer. An EMI operating under the EU's transfer-of-funds regulation will ask its VASP applicant to demonstrate that it can satisfy the Travel Rule on every qualifying transaction, and that it has a tested process for handling gaps where the receiving VASP cannot reciprocate. Incomplete answers at this stage are a common reason for rejection.
The EMI will also review the VASP's token scope. A VASP that operates a spot exchange limited to the largest liquid assets presents a different risk profile from one offering derivatives, staking products, or an asset-referenced token. The nature of the assets a VASP handles bears directly on the EMI's own exposure to market risk, settlement risk, and regulatory classification questions. Operators we advise routinely underestimate how granular this inquiry becomes in practice.
Three additional areas generate disproportionate friction:
- Counterparty chains. The EMI wants to understand not just who the VASP's clients are, but who those clients transact with on-chain. A VASP that cannot produce a coherent account of its on-chain exposure – supported by a credible transaction monitoring program and a documented approach to high-risk wallet clusters – will face extended review or refusal.
- Jurisdictional footprint. A VASP licensed in one jurisdiction but serving clients across multiple jurisdictions creates a cross-border compliance question the EMI must answer. Which rules govern the relationship? Is the VASP acting in compliance with each market it touches? An entity with a single Bank of Lithuania-issued CASP authorization serving clients across the EU triggers a different analysis from one with a VARA licence in Dubai serving institutional clients in the Gulf.
- Custody and client-money separation. Where a VASP also holds fiat on behalf of its clients, the EMI will want evidence that the VASP is not commingling its own operational funds with client money. Safeguarding regimes apply to the EMI side of the relationship; the VASP's own practices are scrutinized as an extension of that obligation.
The Cross-Border Dimension: Where Structures Break
The most damaging structural error we see is a mismatch between the jurisdiction of the VASP's operating entity, the jurisdiction in which its clients are located, and the jurisdiction of the EMI account. Each of those three nodes has its own regulatory logic, and a structure that is coherent at one node can be unlawful – or simply unacceptable to an EMI's compliance team – when viewed across all three.
Consider a VASP incorporated in the Cayman Islands under the CIMA virtual asset service providers regime, operating a platform marketed to clients across the EU, and seeking to hold its fiat float at an EMI licensed under MiCA in Ireland or Estonia. The EMI will immediately ask whether the Cayman entity is passportable into the EU, whether it is subject to equivalent AML/CFT supervision, and whether MiCA's own provisions on third-country access permit the relationship. None of those questions has a clean affirmative answer on those facts.
The reverse structure creates different friction. A VASP with a MiCA CASP authorization seeking to bank at an EMI domiciled in a jurisdiction without equivalent standards may find that the EMI's own correspondent banking relationships preclude it from maintaining accounts for entities with exposure to certain asset types or client geographies. Correspondent banks – the tier-one banks that fund EMIs' own settlement rails – apply their own risk criteria, and those criteria flow downstream.
In our practice, we have seen multiple structures that looked legally compliant on paper fail at the EMI onboarding stage because the operator had not stress-tested the structure against the EMI's own prudential and reputational constraints. A structure designed for regulatory arbitrage is, almost by definition, a structure an EMI's compliance team will flag. The more commercially durable approach is to design the operating structure with banking in mind from the outset – not as an afterthought once the licence has been issued.
The cross-border interaction between the VASP's own licence, the jurisdictions of its clients, and the EMI's supervisory position should be analyzed as a single question. Treating them separately is the most reliable way to build a structure that cannot be banked.
How Does the MiCA Transition Change the EMI Onboarding Calculus?
The full application of MiCA across the EU has materially shifted the onboarding calculation for VASPs targeting European clients. The transition from the prior national VASP registration regimes – most notably in Lithuania, Malta, and Germany – to a harmonized CASP authorization framework has, for the first time, produced a standardized reference point that EMI compliance teams in the EU can use to assess a VASP applicant's regulatory standing.
For a VASP operating under a legacy national registration – issued under a regime that preceded MiCA – the onboarding position is now more precarious. ESMA and the national competent authorities have made clear that grandfathering windows are finite and that operating on a pre-MiCA registration after the relevant transition period may constitute unlicensed provision of regulated services. An EMI that onboards a VASP in this position faces its own regulatory exposure. In our practice, we have seen EMIs in Germany, the Netherlands, and Spain close or freeze accounts for VASPs that had not completed the transition to MiCA-standard authorization.
The MiCA CASP authorization framework also creates new obligations that are directly relevant to EMI onboarding. A CASP must maintain a minimum level of own funds, must comply with governance and organizational requirements, and must satisfy the fit-and-proper assessment for its management body. These requirements create a compliance profile that is, at least conceptually, legible to an EMI. An authorized CASP presenting a current authorization certificate, a current AML program aligned with the applicable MiCA provisions, and a documented Travel Rule process is in a substantially better position than an entity presenting a registration certificate issued under a pre-MiCA regime.
The practical implication: for a VASP whose primary client market is the EU, the single most important banking-preparation step is completing the MiCA CASP authorization process. The licence is not just a regulatory requirement; it is, at this point, the principal trust signal that EU-licensed EMIs use to evaluate a VASP applicant.
The VARA and ADGM Positions: A Contrasting View
Outside the EU, the two Gulf hubs – VARA in Dubai and the FSRA within ADGM in Abu Dhabi – offer a materially different EMI onboarding environment for VASPs that hold the relevant local licences. EMIs operating within those ecosystems, or EMIs in jurisdictions with established correspondent relationships to the Gulf, apply a different risk logic: one that is more familiar with VASP clients and, in practice, more responsive to structured applications.
VARA operates an activity-based licensing model. A VASP licensed under the VARA regime for exchange or custody activities has been through a thorough regulatory vetting process. That process – including a fit-and-proper assessment of the management team, a review of the technology and custody infrastructure, and ongoing supervisory engagement – produces a compliance record that an EMI can review directly. In our practice, operators with a current VARA licence in good standing have found the EMI onboarding process in the DIFC ecosystem, and at selected European EMIs with Gulf exposure, more tractable than operators with equivalent businesses in less-scrutinized regimes.
The ADGM/FSRA regime operates along similar lines within the Abu Dhabi free zone. The FSRA's virtual asset framework requires that regulated entities demonstrate the full suite of AML/CFT controls, and the free zone's common-law underpinning means that the compliance concepts translate more readily to counterparties in common-law banking jurisdictions, including the UK.
The contrast with offshore registration-only vehicles is stark. A VASP registered under the BVI FSC's virtual asset service providers framework or under the CIMA regime in Cayman has a recognized registration, but those regimes do not impose the same depth of ongoing supervisory scrutiny as VARA, the FSRA, or an EU national competent authority under MiCA. EMI compliance teams are aware of the difference, and it is reflected in the onboarding process.
If a prior application stalled or an account was closed, a second review of the regulatory and structural position can surface the reason – and the route back. Write to us at info@oboluslaw.com to discuss.
Decision Matrix: Which VASP Profile Should Choose Which Approach?
Not every VASP faces the same EMI onboarding problem. The right approach depends on the operator's licence position, its client geography, its transaction profile, and – critically – the urgency of its banking requirement. The following profiles describe the most common situations we encounter.
Profile A: EU-authorized CASP targeting European retail and institutional clients. This operator should lead with its MiCA authorization at every EMI conversation. The MiCA CASP certification, combined with a current Travel Rule compliance attestation, a documented AML program, and a clear account purpose statement, constitutes the strongest possible documentation package for an EU-licensed EMI. Timeline from completed documentation to account opening typically runs from several weeks to a few months, depending on the EMI's own queue and risk appetite for the VASP's token scope. The primary risk is an EMI that is itself in regulatory transition and has informally frozen onboarding of new VASP clients.
Profile B: VARA-licensed exchange targeting Gulf-based and international institutional clients. This operator should prioritize EMIs with established presence in the DIFC ecosystem or with a demonstrated track record of VASP onboarding in the Gulf. The VARA licence is the primary trust signal. The cross-border risk arises when the operator also needs a European fiat rail: the VARA licence does not substitute for MiCA authorization in the eyes of an EU-licensed EMI, and a parallel European entity or a correspondent relationship through a third-country EMI may be required.
Profile C: Cayman or BVI-registered VASP building infrastructure for a global client base. This operator faces the hardest onboarding path. Neither the CIMA nor the BVI FSC registration is, on its own, likely to satisfy the AML due-diligence standard of a Tier 1 EU or UK EMI. The most commercially realistic pathway involves either re-domiciling an operating entity to a higher-scrutiny jurisdiction – completing a MiCA CASP authorization, a VARA licence, or a MAS DPT service licence under Singapore's Payment Services Act – or restricting the immediate fiat-rail requirement to EMIs in jurisdictions where the registration standard is accepted. Neither path is fast, and the cost of inaction is continued banking instability.
Profile D: Early-stage VASP with a registration but no institutional client base yet. This operator's onboarding position is primarily a documentation problem rather than a structural one. The absence of a transaction history and an established AML operational record makes it harder to satisfy an EMI's forward-looking risk assessment. In this profile, the most effective preparation is building the compliance infrastructure – Travel Rule tooling, transaction monitoring, a written risk appetite statement – before the EMI conversation begins.
Micro-Matter: Restructuring a Blocked Fiat Rail
In a recent engagement, a European exchange operator approached us after its EMI account – held at a mid-tier EMI in the Baltic states – was closed without detailed explanation following a routine regulatory examination of the EMI's own client portfolio. The operator held a pre-MiCA national VASP registration and had not yet initiated the CASP authorization process. Its Travel Rule compliance program existed as a written policy but had not been operationalized across its primary settlement flows.
We mapped the immediate exposure: the operator was processing fiat settlements through a single EMI account, and the closure left it without a functioning fiat rail for institutional client withdrawals. We identified two parallel workstreams. The first was an emergency EMI application to an alternative institution in a different EU member state – one with a documented VASP onboarding program and a higher risk appetite for the operator's token scope, supported by a rebuilt documentation package that addressed the Travel Rule gap and reframed the operator's institutional client base in terms the new EMI's compliance team could assess. The second was the initiation of the MiCA CASP authorization process, with the understanding that the authorization – once complete – would fundamentally change the operator's EMI onboarding position on a durable basis.
The emergency EMI application succeeded within a matter of weeks. The CASP authorization process remains ongoing. The experience illustrated a pattern we have seen repeatedly: the banking instability that appears acute is almost always the downstream consequence of a structural decision – here, the failure to transition to MiCA-standard authorization – made earlier in the business's development.
Client-Money Safeguarding: What the EMI Requires
Safeguarding is the EMI-side mechanism by which client funds are protected from the EMI's insolvency risk. Under the applicable EMI licensing regimes – including the relevant provisions of the EU's payment-services framework, the UK's equivalent under FCA supervision, and comparable regimes in Singapore and elsewhere – an EMI must either ring-fence client funds in a designated account at an authorized credit institution or hold them in specified liquid assets.
For a VASP using an EMI account, the safeguarding obligation has direct operational implications. The EMI will require the VASP to distinguish between client funds – amounts the VASP holds on behalf of its own end users – and the VASP's own operational treasury. Commingling is not merely a compliance failure; it is a structural defect that will cause an EMI to decline or terminate the relationship.
Where a VASP also engages in custody of digital assets alongside the fiat-holding function, the safeguarding question becomes more complex. Regulators in the leading hubs increasingly expect that a VASP's custody of client digital assets and its management of client fiat balances operate under consistent governance frameworks. An EMI that is asked to hold fiat associated with a VASP's custody operations – where the VASP's clients hold both digital and fiat balances through a single interface – will apply additional scrutiny to the flow of funds between the two balance types.
The practical requirement for most VASP applicants is a documented account structure that segregates client money from operational funds, a clear description of how client fiat flows into and out of the EMI account, and evidence that the VASP has its own client-money policy that is consistent with the safeguarding obligations its EMI is operating under. Regulators in the leading hubs increasingly expect these policies to be operationally implemented – not merely described in a document.
Common Myths About EMI Onboarding for VASPs
A common assumption in the market is that a single offshore licence – typically a registration in a low-cost offshore jurisdiction – is sufficient to establish the compliance credibility needed to open an EMI account in a major financial center. That assumption is incorrect, and it is expensive when tested in practice. An EMI in the UK, the EU, or Singapore does not evaluate a VASP's regulatory standing in the abstract: it evaluates whether the VASP's licence and compliance infrastructure satisfy the EMI's own risk management obligations. An offshore registration that does not require a rigorous AML program, ongoing supervisory engagement, or a fit-and-proper assessment of the management team does not satisfy that standard.
A second common assumption is that having previously been rejected by one EMI is a permanent disqualification. It is not. Rejection is often a function of timing – the EMI's own risk appetite at the point of application – and of documentation quality rather than of the VASP's fundamental business. We have seen operators successfully onboard with a second or third EMI after a first rejection, where the second application was accompanied by materially improved documentation and a structural adjustment that addressed the specific concern the first rejection indicated.
A third assumption is that the banking problem can be deferred until the product is live. In our experience, this is the single most common structural error in digital-asset business planning. The EMI onboarding process takes time. It runs in parallel with product development, not after it. A business that goes live on its technical infrastructure without a confirmed fiat rail is operating with a fundamental dependency that cannot be resolved quickly under commercial pressure.
Related Practices at OBOLUS
Related at OBOLUS
- Banking, Payments & EMI Onboarding for Digital Asset Businesses – overview of the full banking and payment-infrastructure practice for VASPs and crypto operators.
- Payment Institution Licensing for Established Operators – analysis of the PI licence route as an alternative to reliance on third-party EMI accounts.
- EMI Onboarding for VASPs: Institutional Clients – the specific documentation and structural requirements for institutional-grade VASP onboarding mandates.
FAQ
Why do banks close crypto company accounts?
Banks and EMIs close or decline accounts for VASPs primarily because the VASP's compliance documentation does not satisfy the institution's own AML risk-management obligations. Common triggers include an unrecognized or low-scrutiny licence, an incomplete Travel Rule program, undocumented transaction monitoring, or a business model that spans multiple jurisdictions without a clear regulatory basis in each. The closure is rarely about the underlying crypto business; it is almost always about the compliance record the VASP presents to the institution's onboarding team.
How can a VASP onboard with an EMI?
A VASP can materially improve its EMI onboarding prospects by holding an authorization from a recognized, high-scrutiny regulator – such as a MiCA CASP authorization or a VARA licence – and by presenting a complete compliance documentation package that addresses the EMI's own AML obligations. That package should include a current AML/CFT policy, evidence of an operational Travel Rule program, a documented account structure that segregates client funds from operational treasury, and a business plan that accurately describes the client base and transaction profile. Engaging counsel to prepare and sequence the application materially reduces the risk of a first-round rejection.
What does client-money safeguarding require?
Under the EMI licensing regimes applicable in the EU, the UK, Singapore, and comparable jurisdictions, an EMI must segregate client funds from its own assets – either by ring-fencing them in a designated account at an authorized credit institution or by holding them in specified liquid assets. For a VASP using an EMI account, the practical requirement is a documented account structure that separates client fiat from operational funds, consistent governance across fiat and digital-asset custody if the VASP combines those functions, and a written client-money policy aligned with the EMI's own safeguarding obligations.
To structure your EMI onboarding approach and map the licence, banking and compliance stack for your business, write to OBOLUS at info@oboluslaw.com. Alternatively, reach us via t.me/oboluslaw.
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, banking and compliance stack as one mandate – not as three disconnected workstreams – so that the structure a client builds is one an EMI can actually bank. To discuss your situation, contact info@oboluslaw.com.
By Lydia Brennan, Tax & Structuring Analyst – specializing in cross-border payment infrastructure, EMI onboarding strategies and the banking-compliance interface for digital-asset operators.
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.