Regulatory update · Published in regulation MiCA payments digital-assets

EMI and CASP infrastructure: connecting euro payments and digital-asset settlement

How e-money and crypto-asset permissions differ, why one licence does not cover every service, and why mapping the legal perimeter matters.

Businesses that move both euro and crypto often assume that a single licence will cover everything they want to do. In practice, euro payments and crypto-asset services sit under different regimes with different permissions, and a firm’s authorisation defines a perimeter that must be respected. Understanding that perimeter is the difference between a coherent operating model and one that quietly exceeds its authorisation.

Two regimes, two sets of permissions

At a high level, electronic money and payment services in the EU are governed by the e-money and payment services frameworks, while crypto-asset services are governed by the Markets in Crypto-Assets Regulation (MiCA). These are separate regimes.

E-money and payments

An electronic money institution (EMI) can issue e-money and provide related payment services — holding balances, executing transfers, making payouts. The scope is defined by the authorisation and the specific payment services listed.

Crypto-asset services

MiCA introduces the concept of a crypto-asset service provider (CASP), with distinct services such as custody, exchange between crypto-assets and funds, and the operation of a trading platform. Each service is a separate permission.

The key point is that holding one authorisation does not automatically grant the other. An EMI permission does not confer the right to provide crypto-asset services, and a CASP permission does not confer the right to issue e-money.

One licence does not cover every service

Even within a single regime, permissions are granular. A payment authorisation lists specific services; a CASP authorisation lists specific crypto-asset services. A firm authorised for one service is not thereby authorised for another. This granularity is deliberate: each service carries its own risks and obligations.

For a business that genuinely needs both euro payments and digital-asset settlement, the implication is that the operating model must be mapped to the actual permissions held — potentially across more than one authorisation or, in some models, through arrangements with authorised partners.

Where payments and e-money tokens overlap

MiCA also introduces e-money tokens (EMTs), a type of crypto-asset that references a single official currency. EMTs sit at the intersection of the two worlds: they are crypto-assets, but their issuance is closely aligned with e-money concepts. This overlap is exactly the kind of area where a careful perimeter analysis matters, because the same instrument can touch both regimes depending on what is being done with it.

The practical message is not to assume. Whether a given stablecoin, token or flow falls under one regime, the other, or both is a question to be worked through deliberately, with reference to the primary legislation and appropriate advice.

Operational benefits of coordinated controls

When a firm does operate across both worlds — within its permissions — there are real operational benefits to coordinating fiat and crypto controls rather than running them as separate silos:

  • a single view of a customer across euro and crypto activity;
  • consistent screening and monitoring applied to both sides of a conversion;
  • reconciliation that ties fiat movements to crypto movements;
  • one decision trail that regulators and auditors can follow.

Fintech Meta’s intended design keeps fiat and crypto on separate ledgers for integrity, while reconciling them into a single operating view. Conversion is treated as a controlled workflow with supported-asset policy, counterparty rules and monitoring — not as an unrestricted feature.

The most common failure mode is drift: a firm gradually offers services just beyond its authorisation because a product “felt adjacent”. Mapping the legal perimeter — writing down exactly which services are authorised, under which regime, and where partners are relied upon — turns that risk into an explicit, managed decision. It also makes the operating model legible to counterparties, banking partners and regulators.

Practical takeaways

  • Treat e-money/payments and crypto-asset services as separate regimes with separate permissions.
  • Do not assume one authorisation covers another, or that one service covers another within a regime.
  • Analyse EMT and stablecoin flows specifically; overlaps are real.
  • Coordinate fiat and crypto controls operationally, but keep the legal perimeter explicit.

Fintech Meta is developing this coordinated model. The capabilities described are planned and subject to the relevant authorisations and partner approvals.

This article is for general information only and does not constitute legal, regulatory or financial advice. Refer to the primary legislation and qualified advisers for your specific situation.

Sources: General references: EMD2 (Directive 2009/110/EC); MiCA (Regulation (EU) 2023/1114). Consult the primary texts and your advisers for specifics.

This article is for general information only and does not constitute legal, investment, tax or financial advice. It describes planned capabilities of Fintech Meta UAB, which is currently pre-authorisation; regulated services will only become available after the required authorisations and approvals are obtained.

Share this article:

Related insights

January 12, 2026

Built for regulated complexity: why generic payment infrastructure fails complex digital businesses

Why the blanket label “high risk” is inadequate, and how evidence-based assessment serves complex digital businesses better than generic rails.

March 09, 2026

Payment infrastructure for licensed gambling operators

Market-by-market licensing, approved domains, player fund separation, third-party deposits, velocity, white-label and affiliate risk — and why a payment licence is not a gambling licence.

March 23, 2026

Stablecoin settlement and corporate crypto treasury under MiCA

Fiat-to-crypto workflows, supported-asset policy, compliant stablecoins, reserve and settlement discipline, and why a narrow asset list is the responsible starting point.