For an established crypto operator, losing fiat rails is not a compliance headache – it is an existential event. Exchanges, custodians and payment businesses that have successfully licensed their core activity routinely discover that the fiat on/off-ramp banking ban (the refusal or termination of banking by institutions unwilling to service digital-asset businesses) strikes without warning and without a clear path back. The legal question is precise: what structural and jurisdictional conditions must an operator meet before a bank or EMI (electronic money institution) will accept the relationship – and how do you rebuild fiat rails after they have been severed?
Fiat on/off-ramp banking access for established operators turns on the alignment of three layers: the operator's own licence stack, the counterparty bank's or EMI's internal risk appetite under its own regulatory obligations, and the cross-border compliance posture the operator presents. A business that has solved the first layer but ignored the second and third will find accounts closed regardless of its regulatory status. This page sets out the regulated basis, the practical process, the common structural mistakes and a decision framework for operators who are ready to move.
Why Fiat Rails Break – and What the Law Actually Requires
Fiat rails break because banks and EMIs bear direct regulatory liability for the customer relationships they maintain, and most major supervisors – the FCA in the United Kingdom, the Bank of Lithuania, MAS in Singapore and, under MiCA, the network of EU/EEA national competent authorities – require financial institutions to conduct enhanced due diligence on digital-asset businesses as a category of higher-risk customer. That obligation sits at the institution level, not the operator level. The operator cannot waive it. The operator can only make itself easy to accept.
The regulatory baseline is the FATF Recommendation 15 posture adopted across every flagship jurisdiction: virtual asset service providers are subject to the same AML/CFT expectations as other regulated financial intermediaries, and the institutions that bank them inherit a correspondent-risk profile that must be managed. A bank's refusal of a crypto account is therefore not arbitrary – it is typically a decision that the compliance cost of onboarding that specific entity exceeds the revenue it would generate.
In our practice, the operators who experience account closures most frequently are those whose entity structure does not map cleanly onto the institution's internal categorisation system. A holding company that owns a licensed VASP, but that itself holds no licence and is incorporated in a jurisdiction the bank treats as elevated-risk, will almost always fail onboarding – even if the licensed subsidiary is impeccably regulated. The institution sees the entity, not the group structure, unless the operator presents the full picture coherently.
The implication is clear: the legal work that makes fiat rails possible begins before the banking conversation starts. It begins with the operator's own licence and entity architecture.
For a scoped assessment of your current entity structure and what changes would materially improve your banking prospects, 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. Map your options.
The Regulatory Perimeter: What Licences Actually Open Doors
Not every licence opens every door. The practical authority of a licence with a banking or EMI counterparty depends on the jurisdiction's standing in the counterparty's own risk framework – a point that operators who hold a single offshore registration frequently discover too late.
Under MiCA, a CASP (crypto-asset service provider) authorisation granted by a competent authority in one EU member state carries passporting rights across the entire EU/EEA. For a European bank, that authorisation is a known, supervised credential from a regulator the bank's own compliance team can assess against a published rulebook. The result, in practice, is a materially shorter enhanced-due-diligence process than a bank faces when it evaluates an operator licensed in a jurisdiction whose regulatory standards it cannot independently verify.
The VARA regime in Dubai occupies a comparable position for the Gulf and broader MENA markets. An operator holding a VARA licence – with its activity-specific authorisations covering exchange, custody, transfer and other services – presents a compliance posture that the major UAE banks and their international correspondents can evaluate. The same applies, at the other end of the risk spectrum, to an operator holding a licence from MAS under Singapore's Payment Services Act framework, or from the SFC in Hong Kong under the VASP licensing regime for virtual asset trading platforms.
The myth that a single offshore registration is sufficient to access global banking persists because it was partially true in an earlier period of the market. It is not true now. A BVI or Cayman VASP registration – legally valid in its home jurisdiction and meaningful for certain structuring purposes – does not carry the same counterparty weight as an EU CASP authorisation or a MAS licence when approaching a tier-one institution. Operators we advise regularly maintain a primary regulated entity in a tier-one hub for banking purposes, alongside lighter-touch registrations in other jurisdictions for market access. The two functions require different instruments.
Separately, an EMI licence (a licence authorising the issuance of electronic money and the provision of payment services) is itself a fiat-rails solution, not merely a supplement to one. An operator group that holds an EMI licence – or partners with an EMI on a programme basis – can issue IBANs, hold client funds and execute fiat settlements without routing every transaction through a correspondent bank. This architecture is increasingly common among established operators who want operational independence from bank risk appetite.
How Does EMI Onboarding Work for a VASP?
EMI onboarding for a VASP is a structured commercial and compliance process that typically proceeds through several defined stages, each of which presents a distinct failure point if the operator is not prepared.
The first stage is pre-qualification. The EMI will assess the operator's regulatory status, jurisdiction of incorporation, beneficial ownership structure, AML/KYC programme, transaction volumes and the nature of the fiat flows it expects to route. An operator that cannot produce a current AML policy, a documented sanctions-screening procedure and a clear articulation of its customer base will not advance past this stage regardless of its licensing credentials.
The second stage is commercial terms negotiation. EMIs price crypto-business relationships to reflect the compliance overhead. The operator should expect tiered pricing structures, volume-based fee arrangements and, in many cases, a requirement for a pre-funding or reserve deposit. These terms are negotiable, but only by an operator that understands the EMI's own regulatory obligations and can demonstrate why its specific risk profile warrants more favourable treatment.
The third stage is legal documentation. Programme agreements, safeguarding arrangements and data-sharing protocols require legal review. The safeguarding obligation – the requirement under the relevant payment institution rules that client funds held by the EMI are segregated and protected against the EMI's own insolvency – is a point operators frequently underestimate. The documentation must reflect that obligation correctly, and the operator must understand what it means for its own balance-sheet treatment of client funds.
The fourth stage is technical integration and ongoing monitoring. Once the relationship is live, the EMI will monitor transaction flows against the parameters agreed at onboarding. Unusual patterns – a sudden increase in high-value transfers, a change in the jurisdictions of counterparties, a spike in return rates – will trigger review. Operators that cannot respond promptly and with documented rationale will find the relationship at risk.
In a recent matter, a licensed exchange sought to migrate its fiat operations from a correspondent banking arrangement to a direct EMI programme following the sudden closure of its existing account. We conducted a gap analysis of the operator's AML documentation against the EMI's published onboarding criteria, identified three structural deficiencies in the operator's transaction-monitoring framework, and advised on remediation before the formal application was submitted. The application progressed without a request for additional information – a result that, in our experience, is only achievable when the legal and compliance work precedes the commercial approach.
The Cross-Border Reality: Where the Entity Sits vs. Where the Money Moves
The most persistent structural error in fiat-rail architecture is the mismatch between where the operating entity is domiciled, where its users are located and where its fiat flows are denominated. These three coordinates rarely align naturally, and the gaps between them create compliance friction that banks and EMIs treat as risk.
An operator incorporated in a common-law offshore jurisdiction, licensed in a Gulf hub and serving European retail customers through a euro IBAN will face questions from its banking counterparty about why the entity, the licence and the customer base are in three different regulatory spaces. The answer may be entirely legitimate – regulatory arbitrage across functional layers is standard practice for sophisticated operators – but it must be articulated coherently, in advance, with supporting documentation.
The Travel Rule adds a further dimension. The obligation to pass originator and beneficiary data with virtual asset transfers – a FATF standard now implemented in some form across all flagship jurisdictions, with threshold levels that vary and that operators must verify in each market – means that an operator's technical infrastructure must be capable of satisfying Travel Rule obligations in every jurisdiction where it routes transactions. An EMI or correspondent bank reviewing a potential crypto-business customer will assess this capability. Operators that cannot demonstrate compliant Travel Rule implementation will face a harder onboarding conversation.
For operators with a US nexus – whether through US-person customers, US-dollar settlement or a US entity in the group – the picture is more complex again. Federal AML/CFT obligations administered by FinCEN, state money-transmitter licensing requirements and, where relevant, the NYDFS BitLicense framework, each impose their own expectations. A European EMI onboarding a US-nexus operator will conduct its own assessment of that US regulatory footprint. We regularly advise on the US-layer question as part of a broader multi-jurisdiction banking strategy.
If a prior application stalled or an account was closed without explanation, a structural review can identify the jurisdictional mismatch driving the decision and map the route back. To discuss your situation, write to info@oboluslaw.com or Map your options.
What Are the Most Common Mistakes Established Operators Make?
The most common mistake established operators make when pursuing fiat banking is presenting the application as a commercial request rather than a compliance proposition. Banks and EMIs are not evaluating whether they want the revenue – they are evaluating whether they can manage the risk of the relationship under their own regulatory obligations. An operator that opens with revenue projections and closes with a VASP registration certificate has misread the process entirely.
A second common mistake is structuring the banking application around the wrong entity. The licensed operating entity, the holding company, the treasury vehicle and the custody entity each have different risk profiles in the eyes of an onboarding institution. Using the wrong entity – typically the holding company, which holds no licence and whose activity description is opaque – is the single most avoidable reason a well-licensed group fails banking onboarding.
A third error is applying to multiple institutions simultaneously without a coordinated strategy. Banks share adverse information about customer applications through mechanisms that vary by jurisdiction. An operator that receives a rejection from one institution and immediately approaches three others without understanding and addressing the reason for the original rejection will accumulate a rejection history that makes subsequent approaches harder, not easier.
A fourth mistake is underestimating the weight of the UBO (ultimate beneficial owner) disclosure requirement. The beneficial ownership of a crypto-business – particularly where there are multiple individual founders, early investors or complex holding structures – must be documented to the standard the institution requires, not to the minimum required by the operator's home jurisdiction. In our cross-border practice, we have seen applications that were substantively strong in every other respect fail at the UBO stage because the operator produced its corporate registry filing rather than a purpose-built UBO pack.
A fifth, and perhaps most consequential, error is treating the initial onboarding as the end of the process. The relationship with a bank or EMI requires active maintenance: periodic reviews, prompt responses to compliance queries, advance notice of material changes to the business and consistent communication about transaction volumes and patterns. Operators that go quiet between account opening and the next compliance review find that the institution fills the silence with assumptions – and those assumptions are rarely favourable.
Decision Matrix: Which Banking Architecture Fits Which Operator Profile?
The right fiat-rail architecture depends on the operator's scale, regulatory footprint, user geography and risk tolerance. The following profiles describe the most common configurations we advise on.
Profile A – Licensed EU operator, primarily European user base, euro-denominated flows. The instrument of choice is direct account onboarding with a tier-two European bank or a licensed EMI under MiCA's passporting regime, supported by the operator's CASP authorisation. The timeline for onboarding, once documentation is complete, is typically measured in weeks rather than months – though this varies materially by institution and by the completeness of the operator's compliance pack. The key risk is the completeness of the AML programme: EU-licensed EMIs apply a detailed assessment framework, and gaps in transaction-monitoring documentation are the most frequent cause of delay.
Profile B – VARA-licensed operator with Gulf and international flows. The instrument is a combination of a UAE-based banking relationship for local-currency settlement and an international EMI or programme bank for USD and EUR rails. The VARA licence is strong currency with Gulf institutions. International correspondent banking requires a more detailed compliance narrative. The timeline is harder to predict and typically longer. The key risk is the operator's US-dollar settlement chain: correspondent banks in the USD clearing system apply heightened scrutiny to crypto-business flows.
Profile C – Multi-jurisdictional operator with US-nexus exposure. This profile requires a layer-by-layer approach: US entity with FinCEN-compliant AML programme and relevant state MTL coverage for the US layer; a separate licensed entity in an EU or Asian hub for non-US flows; and an EMI programme for retail-facing fiat operations. The timeline is the longest of the three profiles. The key risk is the interaction between the US regulatory layer and the non-US banking relationships – each institution in the chain will assess the US-nexus exposure independently.
No single architecture is universally correct. We map the licence, banking and tax stack for each operator before recommending a structure, because the wrong architecture is not merely inconvenient – it can produce regulatory exposure in jurisdictions the operator did not intend to engage.
A Common Assumption: "Our Licence Is Enough"
A common assumption among operators who have invested in obtaining a primary licence is that the licence itself resolves the banking problem. It does not. A licence demonstrates regulatory approval of an activity. It does not obligate any bank or EMI to accept the licensee as a customer. The institution retains full discretion over its customer acceptance policy, subject only to anti-discrimination law, which does not extend to commercial risk decisions of this kind.
The gap between holding a licence and holding a bank account is filled by the compliance presentation: the AML policy, the transaction-monitoring framework, the Travel Rule implementation, the UBO documentation and the coherent narrative about what the business does, for whom, in which jurisdictions and with what safeguards. We map the licence stack across operating, custody and payment layers before any banking approach is made, precisely because this preparation is what converts a licence into a bankable proposition.
There is a related assumption worth addressing: that EMI relationships are a substitute for bank relationships. They are not substitutes – they are complements. An EMI can provide IBANs, hold safeguarded client funds and execute payment transactions. It cannot provide credit facilities, correspondent relationships with non-EU counterparties in many cases, or the institutional credibility that a tier-one banking relationship provides to counterparties assessing the operator's financial standing. The full fiat-rail architecture for an established operator typically requires both layers.
Self-Assessment: Is Your Business Ready for EMI or Bank Onboarding?
Before approaching any banking or EMI counterparty, an established operator should be able to answer the following questions affirmatively. If any answer is uncertain, that uncertainty represents a material onboarding risk.
Is the entity applying for the account the correct entity – the one that holds the relevant licence, not a holding company or treasury vehicle? Is the AML policy current, documented and implemented by a named MLRO (money laundering reporting officer) whose appointment is properly recorded? Has the Travel Rule been implemented, and is the operator able to produce evidence of its implementation on request? Is the UBO structure documented to the standard required by the counterparty institution, not merely to the minimum required by the home jurisdiction? Has the operator identified and addressed any jurisdictional mismatch between its incorporation, its licence, its customer base and the currencies it settles in?
Has the operator reviewed and addressed any prior adverse banking history – account closures, rejected applications or compliance-triggered restrictions – before approaching new institutions? And has the operator designated internal responsibility for the ongoing management of the banking relationship, including the periodic compliance reviews the institution will require?
Operators who cannot answer each of these questions confidently should treat the gap as a legal and compliance matter to be resolved before the commercial banking conversation begins. The cost of preparation is a fraction of the cost of a failed application – and a failed application creates a record that complicates every subsequent approach.
Related at OBOLUS
- Banking, Payments and EMI Onboarding for Digital-Asset Businesses – the full practice overview covering account access strategy across jurisdictions
- PSP and Acquiring Agreements in Canada – payment service provider structuring and acquirer access under the Canadian regime
- VAT Treatment of Crypto Services in Canada – indirect tax analysis for crypto businesses operating across the Canadian market
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts primarily because they cannot manage the compliance cost of the relationship under their own regulatory obligations. Digital-asset businesses are treated as higher-risk customers under AML/CFT frameworks adopted across the major jurisdictions, including the FCA's regime in the UK and the AML requirements applicable under MiCA in the EU. When the operator's compliance documentation is incomplete, its entity structure is opaque, or its transaction patterns are difficult to categorise, the institution will exit the relationship rather than absorb the supervisory risk. The closure is typically a risk-management decision, not a judgment on the operator's legality.
How can a VASP onboard with an EMI?
A VASP can onboard with an EMI by presenting a compliance package that satisfies the EMI's own regulatory obligations as a payment institution. That package typically includes a current AML policy, evidence of Travel Rule implementation, a documented UBO structure, the operator's primary licence credentials, and a clear articulation of the fiat flows – volumes, currencies, counterparty jurisdictions – that the EMI will be processing. The EMI will conduct its own enhanced due diligence before accepting the relationship. Pre-qualification conversations, conducted before a formal application, are standard practice and allow the operator to identify and address gaps before the formal process begins.
What does client-money safeguarding require?
Client-money safeguarding, as required under payment institution rules across the major regulated hubs, requires an operator or its EMI partner to segregate client funds from the institution's own funds and to protect those funds against the institution's insolvency. In practice this means maintaining funds in a designated safeguarding account at a credit institution, or covering them with an insurance or guarantee policy meeting the regulatory standard. The specific mechanics vary by jurisdiction – the FCA's safeguarding rules, the EU's payment institution requirements, and the MAS regime in Singapore each set their own conditions. Legal documentation between the operator and the EMI must accurately reflect the safeguarding arrangement and the operator's rights in the event of the EMI's failure.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit to a structure – because the wrong architecture creates regulatory exposure that a licence alone cannot cure. To discuss your banking and EMI onboarding situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory and Compliance Analyst – specialises in cross-border digital-asset licence strategy and banking onboarding for established VASP 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.