An EMI account for VASP operations can be a practical way to receive and send fiat payments when a bank will not support a crypto business. It may provide an IBAN, payment access and foreign exchange. For a crypto-asset service provider (CASP) authorised under MiCA, however, it is usually one part of the account structure, not a substitute for a bank.
The distinction matters most when the firm holds client funds. MiCA Article 70 sets a specific rule for where those funds must be placed. Firms planning VASP registration and MiCA compliance should design their payment flows around that obligation before applying to an EMI.
Why do crypto businesses approach EMIs?
Traditional banks may decline a VASP because they cannot get comfortable with its licensing position, customer jurisdictions, transaction monitoring or exposure to particular cryptoasset flows. A rejection does not necessarily mean that the business is prohibited. It may mean the bank’s risk appetite, systems or understanding of the proposed flows do not fit the application.
EMIs often offer a more workable route for day-to-day fiat payments. They still have regulatory obligations and risk limits, and they can reject a firm for the same weaknesses that concerned a bank. An EMI account for a crypto business is most useful when its role is clearly defined: operating payments, customer payment flows where permitted, or another documented use that the provider has agreed to support.
For more on the underlying bank concerns, see why banks decline crypto and gambling companies. The practical response is to address the risk behind a rejection, rather than send the same incomplete application to more providers.
What can an EMI account do, and where does it stop?
Depending on the provider, jurisdiction and approved use case, an EMI may offer named or allocated IBANs, SEPA transfers, SEPA Instant access and foreign exchange. Availability is not uniform. A provider may accept corporate operating payments but decline customer collections, third-party payments or flows involving particular countries.
An EMI is not a credit institution. Its e-money and payment services do not amount to an ordinary bank deposit account, and an EMI account does not provide ordinary bank lending under an EMI permission. Most importantly for an authorised EU CASP, it should not be presented as the bank account required for depositing relevant client funds under MiCA Article 70.
That does not make the EMI account unnecessary. It means the business needs to distinguish its operating rail from its client-funds safeguarding arrangement and from cryptoasset custody. The account agreement and flow-of-funds diagram should make those boundaries visible.
What does MiCA Article 70 require for client funds?
Under Article 70 of Regulation (EU) 2023/1114 (MiCA), a CASP holding clients’ funds other than e-money tokens must place those funds with a credit institution or a central bank by the end of the business day following receipt. The provision also requires appropriate arrangements to safeguard clients’ ownership rights and prevent the use of their funds for the CASP’s own account.
This is why an authorised CASP receiving relevant client fiat cannot simply point to an EMI operating account and say that safeguarding is covered. It needs an arrangement that satisfies Article 70’s placement requirement, typically involving a bank account, alongside procedures that keep client money identifiable and separate from the firm’s own funds.
The rule concerns the funds within Article 70’s scope. It should not be applied indiscriminately to every token, corporate balance or payment passing through the business. Map each flow and obtain advice on its treatment before deciding which account receives it.
What does the three-layer account setup look like?
| Layer | Primary purpose | Key boundary |
|---|---|---|
| EMI operating account | Permitted fiat collections, payments, settlement support and operational expenditure | Not a substitute for placing relevant client funds with a credit institution or central bank under MiCA Article 70 |
| Bank safeguarding account | Placement of relevant client funds and segregation from the CASP’s own money | Requires a bank willing to support the actual CASP model, jurisdictions and flows |
| Crypto custody | Safekeeping and administration of cryptoassets, where applicable | Separate controls and obligations from fiat safeguarding; it is not a fiat account |
The exact structure depends on what services the firm provides and whether it ever holds client fiat or cryptoassets. A business that only pays its own suppliers has different needs from an exchange receiving customer money before execution. Account labels alone do not establish compliance: contracts, reconciliations and the movement of funds must match the proposed structure.
For a fuller comparison of the payment and banking functions, see what an EMI and a traditional bank account each provide.
What will an EMI check when onboarding a VASP?
An EMI will generally want to understand both the legal basis for the activity and the transaction risk it is taking on. Requirements vary by provider and country, but an application should be ready to evidence the following:
- Regulatory status: the relevant registration or authorisation, services covered, legal entity and jurisdictions served. An offshore registration alone does not establish a right to provide services to EU clients.
- AML/CFT governance: a risk assessment, customer due diligence and monitoring procedures, escalation arrangements, and a named MLRO or equivalent responsible officer appropriate to the firm’s obligations.
- Travel Rule controls: how the firm meets Regulation (EU) 2023/1113, known as the Transfer of Funds Regulation (TFR), which has applied since 30 December 2024.
- Ownership and funding: the ownership chain, beneficial owners and source of funds of shareholders, particularly where holding companies or nominees are involved.
- Crypto controls: the blockchain analytics provider, how alerts are reviewed, and how the firm deals with higher-risk wallets and transactions.
- Commercial flows: expected volumes, payment corridors, client jurisdictions, counterparties and a diagram showing where fiat and cryptoassets enter, move through and leave the business.
For EU applicants, timing is material. MiCA’s transitional arrangements do not provide cover after 1 July 2026, and a national transitional period may end earlier. Check the applicable position under MiCA Article 143 rather than assuming an existing national registration remains sufficient. The distinction between registration and authorisation also affects the account application: the EMI needs to know what the entity is permitted to do now, not only what it intends to apply for.
Why do EMI applications get declined?
Common problems are an unregistered activity, an offshore-only licence used to justify service to EU clients, or an application that describes projected turnover without explaining transaction types and corridors. Complex or nominee-heavy ownership can also stall review if the people who ultimately own and fund the business are not clearly identified.
A missing named MLRO, generic AML policies or an unexplained gap between the website’s advertised services and the licence scope can undermine an otherwise credible application. So can a claim that an EMI account will safeguard all client fiat under MiCA without showing the required credit-institution or central-bank arrangement.
These are not always problems solved by adding more paperwork. The operating model may need to change: restrict a jurisdiction, revise a customer flow, appoint a responsible officer or arrange the bank layer before seeking an EMI account. The answer should be reflected consistently in the application, contracts, policies and flow diagram.
How should a VASP prepare before applying?
- Confirm the permission: identify the applicant entity, its current regulatory status, permitted services and every jurisdiction it serves. Do not treat an intended MiCA application as an authorisation already held.
- Separate the money flows: mark corporate funds, relevant client funds and cryptoassets on one diagram. State which entity controls each account and when transfers occur.
- Document controls: prepare the AML/CFT framework, MLRO details, TFR process, blockchain analytics arrangements and escalation procedures used in practice.
- Substantiate the forecast: provide reasoned expected volumes, typical transaction sizes, currencies, corridors and customer locations. Explain assumptions where the business has no trading history.
- Resolve ownership questions: assemble the ownership chart, beneficial-owner evidence and shareholders’ source-of-funds records before the provider asks for them.
- Identify the bank dependency: if MiCA Article 70 applies, plan how the credit-institution or central-bank placement will work. Do not assume an EMI approval resolves that requirement.
Send a coherent application rather than a large collection of unrelated documents. The reviewer should be able to follow one transaction from customer onboarding through fiat receipt, cryptoasset transfer where relevant, monitoring, reconciliation and final payout.
What changes after 2026?
From 10 July 2027, the EU Anti-Money Laundering Regulation, Regulation (EU) 2024/1624, applies. It treats CASPs as obliged financial institutions and requires customer due diligence from the start of a business relationship. EMIs assessing CASPs should be expected to examine onboarding controls and the quality of customer information closely.
A provider’s precise criteria will still depend on its licence, policies and appetite for particular risks. The sensible preparation is to make regulatory status and payment flows clear now, with evidence that AML and Travel Rule procedures operate in practice.
FAQ
Can an EMI be my safeguarding account under MiCA?
Not in place of the placement required by MiCA Article 70 for relevant client funds. Those funds must be placed with a credit institution or central bank by the end of the next business day. An EMI account may serve a separate payments or operating function.
Will EMIs onboard a VASP that is only registered offshore?
Some may consider an offshore-registered firm, depending on its activities, customer locations and their risk policies. Offshore registration alone does not authorise a firm to serve EU clients where MiCA authorisation is required. The EMI will need a defensible explanation of where and under what permission the business operates.
How long does EMI onboarding take?
It varies, but firms should plan for weeks rather than assume an account will open immediately. Completeness of the application, ownership checks, jurisdictions and the complexity of the payment flows all affect review time. Further questions or a change to the proposed model can extend it.
Do I need a UK or EU entity?
There is no universal entity requirement for every EMI application; it depends on the provider and intended account use. If the firm needs MiCA authorisation to provide CASP services in the EU, its EU authorisation position must be addressed. A UK entity or offshore registration by itself does not resolve that question.
What volumes and documents do EMIs ask for?
Expect to explain projected monthly volumes, transaction sizes, currencies, corridors and the countries where customers and counterparties are located. Typical supporting material includes incorporation and ownership documents, regulatory evidence, AML/CFT and Travel Rule procedures, MLRO details, shareholder source-of-funds evidence and a flow-of-funds diagram. Requests differ between providers.
How VMGlobals can help
VMGlobals can review the proposed account structure, regulatory status and onboarding file before a VASP approaches payment providers. Its payment strategy and banking access support helps firms distinguish EMI rails from the bank arrangements their model may also require, without assuming either application will be approved.