EMI Onboarding for VASPs in the United Kingdom: The Regulated Path to Fiat Rails
For a VASP (virtual asset service provider) seeking sterling or multi-currency banking in the United Kingdom, the question is not simply whether a bank will take the account. The question is whether the VASP's own registration status, compliance posture and structural design satisfy the risk-appetite and due-diligence standards that every EMI (electronic money institution) in the UK applies before opening fiat rails. Operating without the right foundation risks enforcement, frozen rails and lost banking at precisely the moment the business needs them most. This page maps the regulated path: what the FCA requires of EMIs, what EMIs consequently require of VASPs, and where the onboarding process typically breaks down.
The direct answer: a VASP seeking EMI-provided fiat rails in the United Kingdom must hold a current FCA cryptoasset registration under the Money Laundering Regulations, demonstrate a documented AML/KYC programme that meets the FCA's standards, and present a corporate structure the EMI can underwrite. No single offshore licence substitutes for this. The FCA's financial-promotion rules add a second layer: any VASP marketing to UK persons must also comply with the applicable cryptoasset financial-promotion regime, which EMIs will scrutinise independently before onboarding.
The sections below walk through the regulatory basis, the practical onboarding sequence, common failure points, and the cross-border structuring decisions that determine whether a VASP can access UK fiat infrastructure at all.
The FCA Registration Baseline: Why It Defines the EMI Relationship
Every EMI operating in the United Kingdom holds its own authorisation from the Financial Conduct Authority (FCA), and that authorisation carries direct AML obligations. An EMI that onboards a VASP is onboarding a higher-risk business client. Under the UK's anti-money-laundering rules, the EMI must treat the VASP as a business relationship requiring enhanced due diligence. The most efficient signal the VASP can give that it is not a regulatory liability is proof of its own FCA cryptoasset registration under the Money Laundering Regulations.
The FCA's cryptoasset register is public and actively maintained. EMI compliance teams check it as a first-pass screen. A VASP that does not appear – because it operates on a foreign licence, because its registration lapsed, or because it never applied – immediately triggers an elevated risk-assessment that most EMIs resolve by declining the application. We have seen this outcome repeatedly: a well-capitalised exchange, confident in its offshore licence, approaches a UK EMI and is turned away before the application reaches a relationship manager.
The financial-promotion regime compounds this. The FCA's cryptoasset financial-promotion rules require that any communication inviting UK persons to engage with crypto investments or services is either issued or approved by an FCA-authorised person, or falls within a specific exemption. EMIs read marketing materials as part of their onboarding review. A VASP whose website or app promotes services to UK users without a proper approval structure is a compliance problem the EMI must solve – and the usual solution is to decline rather than manage it.
For a scoped assessment of your FCA registration position and how it reads to a UK EMI, 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 considerably. Map your options
What Do EMIs Actually Require From a VASP Applicant?
EMI onboarding for VASPs in the United Kingdom follows a structured due-diligence sequence that goes well beyond presenting a licence certificate. Based on our cross-border practice, the standard package an EMI expects includes at minimum: a full corporate structure chart, the entity's regulatory status in every jurisdiction where it holds clients or processes transactions, a current AML policy and associated procedures, evidence of a functioning compliance function (including the name and background of the MLRO), business-line descriptions showing how fiat and crypto flows interact, and a client-risk-assessment methodology.
EMIs also carry out adverse-media and sanctions screening on the VASP itself, its directors and its ultimate beneficial owners. A jurisdiction associated with elevated FATF risk in the corporate chain – even a holding company, not the operating entity – frequently triggers manual escalation or an outright decline. This is a structural problem, not a documentation problem, and it cannot be resolved by adding more pages to the compliance manual.
The Travel Rule (the obligation under FATF Recommendation 15 to transmit originator and beneficiary data alongside virtual-asset transfers) has become a specific checkpoint. EMIs increasingly ask how the VASP captures, transmits and stores Travel Rule data, which counterparty VASPs it transacts with, and whether those counterparties are themselves registered in a FATF-aligned jurisdiction. A VASP without a credible Travel Rule compliance story will find that UK EMIs – themselves under FCA supervision on financial-crime standards – will treat the gap as disqualifying.
Where Does the Onboarding Process Break Down?
The failure points in UK EMI onboarding for VASPs are well-documented in our practice. They cluster around four categories, and all four are addressable before the application is submitted.
The first is registration status. Relying on an EU MiCA authorisation, a BVI VASP Act registration, a VARA licence from Dubai, or a CIMA-supervised Cayman structure does not substitute for UK FCA registration when the VASP serves UK persons or processes UK payments. Each regime is respected in its own jurisdiction; none satisfies the FCA's domestic gatekeeping function for UK-nexus business.
The second is corporate-structure opacity. A multi-layered group where the operating entity sits three levels below the UBO, with intermediate holding companies in non-transparent jurisdictions, is a consistent reason for decline. UK EMIs carry their own FCA obligations; they cannot onboard a client whose ownership they cannot trace and evidence.
The third is compliance-programme maturity. A VASP at early stage often has a compliance framework drafted by a consultant but not yet embedded in the operation. EMIs ask for evidence of real-world operation: transaction monitoring logs, SAR filing data (in aggregated, anonymized form), staff training records. The absence of operational evidence – not just policy documents – signals that the programme exists on paper only.
The fourth is financial-promotion status. As noted above, a VASP that promotes to UK persons without a proper FCA approval structure is presenting the EMI with a regulatory exposure it cannot price. Resolving this before the onboarding application – either by obtaining a financial-promotion approval arrangement with an FCA-authorised firm or by geo-restricting UK access – removes a significant barrier.
How Does Cross-Border Structure Affect UK EMI Access?
The cross-border reality for most VASPs seeking UK fiat rails is that the operating entity, the custody function, the user base and the treasury often sit in different jurisdictions. This matters enormously for UK EMI onboarding because the EMI's obligation is to understand and underwrite the entire business relationship – not just the UK-incorporated subsidiary.
In our practice, we regularly advise on the sequencing question: should the VASP establish a UK-registered entity first, obtain FCA registration for that entity, and use the UK entity as the gateway to UK EMI services? Or can an existing foreign-licensed entity access UK EMIs directly? The answer depends on the scale of UK-nexus activity, the nature of the services, and how the relevant EMI's own risk policy draws the line between "sufficient UK substance" and "UK-user exposure through a foreign entity."
A VASP that sits primarily in the EU under MiCA authorisation but processes payments for UK users through a UK EMI account held by the EU entity is presenting a hybrid structure. Some EMIs will accept this with strong documentation; others require a UK legal presence. The MiCA passporting regime does not extend to the United Kingdom post-Brexit, so the MiCA CASP authorisation gives no regulatory comfort to a UK EMI making its own risk assessment under UK law.
For VASPs structured across the Gulf – with a VARA licence covering Dubai and an ADGM/FSRA authorisation covering Abu Dhabi – the UK EMI question typically arises when the business wants sterling settlement for institutional clients. The VARA and FSRA frameworks are well-regarded by UK EMI compliance teams, but they do not replace the need for a UK compliance posture. Structural advice here is most valuable before the VASP commits to a group architecture, because unwinding a holding structure after an EMI decline is expensive.
A Matter: Recovering a Stalled EMI Application
In a recent onboarding engagement, a payments-focused VASP had been declined by two UK EMIs on identical grounds: its parent holding company was incorporated in a jurisdiction flagged in the relevant EMI's geographic-risk policy, and the VASP's compliance documentation described its AML programme but provided no operational evidence of its functioning. The VASP held a valid registration in its home jurisdiction and had substantial transaction volume. On instruction, we conducted a structural review, mapped the UBO chain, identified the holding-company problem as the primary obstacle, and advised on a restructuring that placed a UK-incorporated entity in the operating position for UK-nexus activity. We also worked with the VASP's in-house team to prepare an operational compliance pack – including evidence of transaction-monitoring activity and Travel Rule implementation – that addressed the specific questions the EMIs had raised. The reapplication proceeded to an account-opening within an operationally acceptable period. No outcome is guaranteed; the facts of each application are different.
What Does Client-Money Safeguarding Require at the EMI Level?
An EMI holding client funds in the United Kingdom must comply with the safeguarding requirements applicable under the UK's Payment Services Regulations. These rules require that relevant funds – the sterling or other currency value representing e-money issued or payment transactions in progress – be held in a designated safeguarding account, segregated from the EMI's own funds, with a custodian bank that meets the applicable eligibility criteria.
For a VASP using an EMI for fiat settlement, this has a practical consequence. The VASP is the EMI's client; the safeguarding obligation runs from the EMI to the VASP (and, in some structures, to the VASP's own end-clients if the VASP is itself a payment intermediary). EMIs will ask the VASP to describe how end-client fiat balances are held at the VASP level. If the VASP commingles client fiat with its own treasury, the EMI faces a question about whether the overall structure meets the spirit of the safeguarding regime – even if the technical obligation falls on the EMI, not the VASP.
In our cross-border practice, we regularly see VASPs surprised by this inquiry. The EMI is not being obstructive; it is managing its own regulatory exposure. A VASP that can demonstrate its own client-money segregation practice – even where not technically required – substantially improves the onboarding outcome.
Decision Matrix: Which VASPs Are Positioned to Onboard With a UK EMI?
Profile A – UK-registered VASP with current FCA cryptoasset registration, documented AML programme and no geographic-risk flags in the corporate chain. This profile is positioned for standard-track onboarding with most UK EMIs. The process typically runs from initial submission to account opening in a matter of weeks to a few months, depending on the EMI's internal review load and any follow-up queries. The primary risk is documentation gaps at the operational evidence stage.
Profile B – EU-incorporated VASP with MiCA CASP authorisation seeking UK sterling rails, no UK FCA registration. This profile will encounter friction at every UK EMI. The MiCA passport does not extend to the UK. The EMI's risk assessment will turn on whether UK-nexus activity is substantial, whether a UK presence can be established, and whether the EU entity's AML programme aligns to FCA expectations. Timeline is longer; outcome depends on structural choices made before application.
Profile C – Offshore-licensed VASP (BVI, Cayman, VARA, ADGM) with no FCA registration and a UK user base. This profile faces the hardest path. Without FCA registration, the VASP is offering services to UK persons without the domestic licence that UK EMIs are designed to service. The structural fix – establishing a UK entity, registering it with the FCA, and demonstrating UK operational substance – is achievable but takes time. An application submitted before this work is done is likely to be declined.
Profile D – Early-stage VASP with a compliance framework in draft, no operational compliance history, seeking a UK EMI account to launch. This profile should pause and build the operational compliance record before approaching EMIs. A declined application leaves a record. A better sequence is: obtain FCA registration, operate compliance processes for a demonstrable period, compile the operational evidence pack, then apply.
To map the licence, banking and compliance stack for your specific profile, write to OBOLUS at info@oboluslaw.com. If a prior application stalled or an account was closed, a second structural review can surface the specific reason and the route back. Map your options
Related at OBOLUS
- Banking, Payments and EMI Onboarding for Digital Asset Businesses – how we map the full fiat-rail and payment-licence stack for VASPs globally
- De-Risking and Account Closure Defence in Canada – structuring and legal response when a bank or EMI closes a crypto business account
- Digital Asset Licensing in El Salvador: What Businesses Need to Know – an alternative jurisdiction perspective for operators reviewing their group structure
FAQ
Why do banks close crypto company accounts?
Banks and EMIs close crypto company accounts primarily for two reasons: unresolved compliance gaps and geographic-risk policy. A VASP that cannot demonstrate a functioning AML programme, that holds corporate structures in flagged jurisdictions, or that lacks the domestic regulatory registration the institution expects will be assessed as a liability. The closure is usually a risk-management decision, not a judgment on the underlying business. The fix is structural and documentation-led, not a matter of changing banks.
How can a VASP onboard with an EMI?
A VASP seeking EMI onboarding in the United Kingdom should first secure FCA cryptoasset registration under the Money Laundering Regulations, then build an operational compliance pack – AML policy, transaction-monitoring evidence, Travel Rule implementation, MLRO background and UBO documentation. The application should present the full corporate structure, explain every jurisdiction in the chain, and address financial-promotion status for UK users. Preparation reduces the risk of a declined application that becomes part of the VASP's regulatory history.
What does client-money safeguarding require?
Under the UK's Payment Services Regulations, an EMI must hold relevant client funds in a designated safeguarding account, segregated from the EMI's own money, at an eligible custodian institution. VASPs using EMIs for settlement should understand that EMIs will ask about the VASP's own client-fiat segregation practices. A VASP that commingles end-client fiat with treasury creates a compliance concern for the EMI. Demonstrating internal segregation – even where not technically mandated at the VASP level – materially supports the onboarding process.
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, and we act only for businesses. We map the licence stack across operating, custody and payment layers before you commit – so your banking architecture is built to withstand EMI due diligence from the outset. To discuss your situation, contact info@oboluslaw.com or message us at t.me/oboluslaw.
By Victor Olsen, Regulatory & Compliance Analyst – specialist in FCA registration pathways, AML programme design and cross-border compliance structuring for VASPs seeking UK and EU fiat-rail access.
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.