“Stablecoin payment processor” has become a working term in payments without ever being properly defined. It is used to describe everything from crypto on-ramps with a payout button to fully authorised electronic money institutions issuing their own tokens. The differences between them are material — and largely a function of which regulatory frameworks apply, and whether the processor sits inside or outside them. This explainer sets out what the category covers, how the two relevant European regulatory frameworks — MiCA and PSD2 — apply together, and why the distinction determines whether a business is operating on regulated or unregulated infrastructure.

What stablecoin payment processing involves

Before regulation, the mechanics. A stablecoin payment processor handles the lifecycle of a payment denominated in or settled through a stablecoin. That lifecycle typically has four stages:

  1. Collection — receiving the payment from the payer, whether in fiat (via bank transfer, card, or pay-by-bank) or in stablecoin (from an on-chain wallet).
  2. Conversion — where required, exchanging between fiat and stablecoin, or between stablecoins.
  3. Settlement — confirming the transaction on the blockchain and crediting the merchant's account.
  4. Payout — moving the resulting balance to its destination: a bank account in fiat, a wallet in stablecoin, or held in a multi-currency account for treasury purposes.

These stages can be performed by a single entity or split across several. Each engages different regulatory obligations. The entity that holds the funds at any point in the chain bears the regulatory responsibility for them — not the entity providing the user-facing interface.

Two different propositions sit behind the same label.

A traditional card processor sits on top of a regulated payment scheme. A stablecoin payment processor either sits on top of one, or is one.

Why “regulated” is not just a label

The unregulated version of this service exists. A company can build a checkout widget that accepts stablecoin payments, routes them through a custodial wallet, converts them, and pays the merchant out — without holding any licence at all, provided it manages to avoid the activities that trigger regulatory authorisation.

That kind of structure typically works by either (a) operating outside Europe and accepting the corresponding legal exposure, or (b) using a banking partner that does hold the relevant authorisations and treating itself as a software vendor. Neither model gives the merchant regulatory protection. If the processor fails, becomes insolvent, or is found to have been operating without required licences, the merchant’s funds are exposed in ways that a regulated relationship would have prevented.

“Regulated” therefore means something specific: the entity processing the payment holds the authorisations required to perform each of the activities in the payment chain. For stablecoin payments in Europe, that means two regulatory regimes apply together — and both must be satisfied.

The two regulatory frameworks — MiCA and PSD2

Two pieces of European legislation define the regulatory perimeter for stablecoin payments. They were drafted at different times, for different purposes, and apply in parallel rather than in sequence.

MiCA — the framework for the asset

The Markets in Crypto-Assets Regulation (MiCAR, Regulation (EU) 2023/1114) governs the crypto-asset itself. For payment-grade stablecoins, the relevant section is Title IV, which covers Electronic Money Tokens (EMTs) — crypto-assets that maintain a stable value by referencing a single official currency. EURSM, USDC, EURC, and Société Générale’s EURCV are EMTs under MiCA Title IV.

MiCA Title IV defines:

  • Who can issue an EMT. Only authorised Electronic Money Institutions (EMIs) or credit institutions. No other entity may issue or offer an EMT to the public in the EU.
  • How the EMT must be backed. A reserve of assets held 1:1 against tokens in circulation, with strict composition, custody, and liquidity requirements.
  • What rights the holder has. A statutory right of redemption at par, in fiat, at any time, free of charge.
  • What disclosures the issuer must publish. A white paper, ongoing reserve reporting, and operational disclosures.

MiCA governs the asset. It does not, by itself, regulate the activity of using that asset to move money on behalf of customers.

PSD2 and EMD2 — the framework for the activity

The activity of holding customer funds, issuing electronic money, and executing payment transactions is governed by two earlier directives: the Second Payment Services Directive (PSD2, Directive (EU) 2015/2366) and the Second Electronic Money Directive (EMD2, Directive 2009/110/EC).

PSD2 and EMD2 define:

  • Who can hold customer funds. Only authorised payment institutions, electronic money institutions, or credit institutions, and only if those funds are safeguarded against the institution’s own liabilities.
  • Who can execute payment transactions. Any of the same regulated entity types, against specific payment service authorisations.
  • What protections the customer has. Strong customer authentication, payment service liability rules, dispute resolution, and — for e-money holders — redemption rights at par.

PSD2 and EMD2 are the rules that turn a stablecoin from an asset on a blockchain into a payment instrument that a business can use without taking on legal risk.

How MiCA and PSD2 apply together

Where these frameworks meet is the regulatory architecture of a stablecoin payment processor itself.

First, an EMT is simultaneously a crypto-asset under MiCA and electronic money under EMD2. That is deliberate. MiCA Title IV explicitly cross-references EMD2 and applies its substantive rules — including safeguarding, redemption at par, and the prohibition on paying interest — to EMT issuers. An EMT is not a new legal category alongside e-money. It is e-money, issued in a tokenised form, with additional MiCA-specific disclosures on top.

Second, the entity holding customer funds at any point in the payment chain needs a payment-services or e-money authorisation, regardless of whether the funds are held in fiat or in EMT. Moving an EMT on behalf of a customer is, in legal substance, executing an e-money transfer. It engages the same authorisation requirements as moving fiat e-money would. A processor that does this without a PSD2/EMD2 licence is operating outside the regulated perimeter, even if the asset it moves is itself MiCA-compliant.

Third, the issuer of the EMT and the processor moving it can be the same entity or different entities. If they are the same — vertically integrated — a single regulated entity covers the full lifecycle: the asset is regulated under MiCA, the activity is regulated under PSD2/EMD2, and the customer relationship is regulated end-to-end. If they are different, the processor depends on the issuer’s regulatory standing, and the merchant inherits that dependency.

The description “regulated stablecoin payment processor” is therefore not redundant. It points to the combination of two authorisations — issuance and movement — and the question for any business considering one is whether both are present, who holds them, and how they relate to each other.

What unregulated looks like in practice

Some live patterns sit outside this perimeter:

  • VASP-only processors. A Virtual Asset Service Provider registration permits crypto-asset custody, exchange, and transfer. It does not authorise the holding of customer fiat funds, the issuance of e-money, or the provision of payment services as defined under PSD2. A VASP processing stablecoin payments and paying out fiat through a partner bank is, in regulatory terms, providing custody and exchange — not payment services.

  • Processors using non-MiCA-compliant stablecoins. USDT has substantial global volume but is not authorised under MiCA Title IV. A processor that routes payments through USDT can still operate in Europe, but the stablecoin itself does not meet the EU regulatory standard. Merchants accepting it bear the corresponding risk: no statutory redemption right, no reserve transparency at the EU regulatory standard, and ongoing uncertainty about USDT’s status in European markets.

  • Crypto-to-fiat on-ramps marketed as payment infrastructure. A service that converts incoming crypto into fiat and credits the merchant via a partner bank account is a useful tool — but is not a regulated payment processor in its own right. The regulated leg is the partner bank’s; the on-ramp itself typically holds only VASP authorisation, if any.

These are not necessarily bad services. They have legitimate use cases. But they are not the same thing as a regulated stablecoin payment processor, and presenting them as if they were creates risk that the merchant absorbs without realising it.

What this means for your business

For any business considering stablecoin payment infrastructure, the regulatory architecture above raises questions worth asking of any prospective processor:

Who holds the regulatory authorisations? Both PSD2/EMD2 and MiCA Title IV. Not just one. A processor that holds only one of these is dependent on a third party for the other — and the merchant should know who that third party is and how the relationship works.

Is the stablecoin itself MiCA-compliant? If the processor uses a non-MiCA-authorised stablecoin, the merchant inherits the regulatory uncertainty attached to that asset. For EUR-denominated transactions in particular, using a MiCA-compliant EMT removes that uncertainty.

What happens if the processor fails? Under a regulated relationship with proper safeguarding, customer funds are protected against the processor’s own insolvency. Outside that, the merchant is an unsecured creditor.

Stablecoin payment infrastructure is not new technology in search of a use case. The use case — faster, cheaper, programmable payments — is real and increasingly well-understood. The question for any business adopting it is whether the infrastructure they are adopting is regulated end-to-end, or whether one or more legs of the chain rely on assumptions that the regulatory frameworks above do not actually support.

Stable Mint is an authorised Electronic Money Institution under MiCA and PSD2, issuing its own MiCA-compliant EMTs (EURSM and USDSM) and providing the full payment lifecycle — collection, settlement, treasury, and payouts — under a single regulated relationship. If you are evaluating stablecoin payment infrastructure for your business, talk to our team.