Paying out into the EU in stablecoins from outside it: what MiCA actually requires of you

If your institution sits outside the EU and wants to pay EU beneficiaries in stablecoins, MiCA CASP requirements apply to the leg that touches an EU client: transferring crypto-assets on behalf of clients, exchanging them for funds, or holding them in custody are each a regulated crypto-asset service, and each must be performed by a crypto-asset service provider authorised in a member state. The token must be an e-money token issued by an EU-authorised credit institution or electronic money institution, which as of mid-2026 admits USDC and EURC and excludes USDT from regulated EU venues. A non-EU bank or MSB therefore has two clean routes: partner with an authorised CASP that performs the EU-side service, or settle in stablecoin with an EU counterparty and deliver euro over SEPA. This article covers the obligations, the tokens, the transitional position and the operating design of each route.

Which of your activities does MiCA treat as a crypto-asset service?

MiCA, Regulation (EU) 2023/1114, lists the crypto-asset services in Article 3. The ones a payout provider touches are custody and administration of crypto-assets on behalf of clients, exchange of crypto-assets for funds, and transfer services for crypto-assets on behalf of clients. The test is whether the service is provided to clients in the EU on a professional basis, not where the provider is incorporated.

The decision rule for a non-EU institution is simple to state. If an EU-resident business or consumer is your client and you move USDC to their wallet, or convert it into euro for them, you are providing a crypto-asset service in the EU and Title V of MiCA applies. Article 59 requires that person to be a legal entity with a registered office in a member state and to hold a CASP authorisation from its national competent authority. Article 61 preserves a reverse solicitation exemption where the EU client initiated the relationship on its own exclusive initiative, but ESMA guidance reads it narrowly: it does not cover marketing, it does not extend to new products, and it is not a business model. A payout programme that recruits EU beneficiaries cannot rely on it.

The operational consequence is that somewhere in your chain there must be an authorised CASP whose name appears in the ESMA register, and your onboarding file for that counterparty should contain its authorisation reference, the services it is authorised for, and the member states into which it has passported under Article 65. An examiner will ask for that page.

Which stablecoins can lawfully reach an EU beneficiary?

Title IV of MiCA governs e-money tokens, the category that covers fiat-referenced stablecoins. Article 48 restricts the offer to the public and admission to trading in the EU of an e-money token to tokens issued by an authorised credit institution or an authorised electronic money institution that has published a crypto-asset white paper notified to its competent authority. Titles III and IV applied from 30 June 2024, six months before the CASP provisions in Title V applied on 30 December 2024. Holders have a redemption right at par against the issuer at any time.

That is why the EU token map looks the way it does as of mid-2026. Circle obtained an electronic money institution authorisation in France in July 2024 and issues USDC and EURC under MiCA. Tether did not seek EU authorisation for USDT, and ESMA guidance led EU-serving exchanges to withdraw non-compliant tokens by the end of the first quarter of 2025. A non-EU institution that runs its treasury on USDT can still hold and settle USDT with non-EU counterparties, but it cannot deliver USDT to an EU beneficiary through an authorised CASP as the final asset. The control here belongs in your product configuration: an allowed-asset list per destination jurisdiction, with EU destinations mapped to MiCA-compliant e-money tokens only, and a hard block on anything else at payout initiation rather than at review.

One further nuance affects volume planning. E-money tokens denominated in a non-EU currency such as the US dollar are subject to monitoring of their use as a means of exchange within the EU, and competent authorities may require an issuer to stop issuing if usage thresholds for a single currency area are exceeded. For a payer this is an issuer-side risk rather than an obligation, but it is a reason to keep the euro leg, not the dollar-token leg, as the instrument the beneficiary receives where feasible.

Where do the transitional periods stand as of mid-2026?

Article 143 of MiCA allowed each member state to grant firms already providing crypto-asset services under national law a transitional period of up to eighteen months from 30 December 2024, which ran to 1 July 2026. Member states used that discretion differently. Several, including the Netherlands, Finland and Poland, chose a six-month window that closed on 30 June 2025. Germany's closed at the end of 2025. France, Malta and Luxembourg among others used the full period. ESMA published a statement in April 2026 on the end of the transitional periods, and the regulation contains no extension mechanism.

For a non-EU institution the practical meaning is that any EU counterparty still operating on a legacy national registration after 1 July 2026 is not a lawful counterparty for EU crypto-asset services. Your counterparty due diligence questionnaire should ask three things: the date of MiCA authorisation, the competent authority that granted it, and whether any service you rely on, in particular transfer services under Article 3(1)(26), is within its authorised scope. A partner that was registered under an earlier national regime and has not yet appeared in the ESMA register as an authorised CASP is a red flag, not a technicality.

The question is no longer whether your EU partner has a licence of some kind. It is whether the specific act you are asking it to perform for your client is inside the perimeter of its MiCA authorisation on the day the payout settles.

What does the Transfer of Funds Regulation add to a payout?

MiCA does not stand alone. Regulation (EU) 2023/1113, the recast Transfer of Funds Regulation, applied from the same date as Title V and extends the FATF Travel Rule to transfers of crypto-assets by CASPs. It has no de minimis threshold, so every transfer carries originator and beneficiary information, and it requires the beneficiary CASP to verify that the beneficiary name matches the account holder before making funds available. Transfers to or from self-hosted wallets above 1,000 euro trigger additional verification of the wallet's ownership or control.

Operationally, this means the data you would already place in a pacs.008 for a euro credit transfer must also travel with the on-chain leg. Most authorised CASPs exchange this data in IVMS101 form through a Travel Rule protocol, and they will reject an inbound transfer whose originator data is absent or malformed. The fields that most often break a payout are the sending wallet address and the beneficiary's legal name, which must match what the receiving CASP holds after KYC. Your compliance workbench should show both messages, the fiat instruction and the Travel Rule payload, side by side under the same UETR so a reviewer can see that the data is consistent before release.

How do you deliver in stablecoin through an authorised partner?

The first route keeps the stablecoin as the asset the beneficiary receives. Your institution, outside the EU, holds USDC in its own custody and sends it to a wallet controlled by an authorised EU CASP, which credits the beneficiary's account with that CASP. Under this design the EU-side services, custody and transfer on behalf of the client, are performed by the CASP, and your institution acts as an originating institution outside the EU perimeter. The beneficiary must be a customer of the CASP, onboarded under its KYC, and the CASP must be authorised for custody and transfer services.

The contract with the partner should fix the following points in writing so that neither side is guessing during an incident.

• The exact services the CASP performs for your beneficiaries and the article of its authorisation that covers each, so the perimeter is documented once and not renegotiated per payout.
• The accepted assets and chains, with the CASP confirming which e-money tokens and networks it will credit and how it treats an inbound transfer on an unsupported chain.
• The Travel Rule protocol, message format and the cut-off after which an unmatched inbound transfer is returned rather than held.
• The return path when the beneficiary cannot be matched, including the wallet the funds come back to, the fee treatment and the message you receive, ideally a pacs.004 with a structured reason code.
• The reporting the CASP will provide for your own regulator, including transaction-level records that reconcile to the chain by transaction hash.

This route suits business beneficiaries that already hold accounts with an EU CASP and want to keep working capital in a dollar stablecoin. It is less suitable for a broad payout population, because it requires every beneficiary to be onboarded by the EU partner before the first payment.

When is settling in stablecoin and paying out in euro over SEPA the better route?

The second route uses the stablecoin only as the settlement asset between institutions. Your institution sends USDC to an EU-authorised counterparty, which may be a CASP, an electronic money institution or a bank with the relevant permissions, and that counterparty converts to euro and pays the beneficiary through SEPA Credit Transfer or SEPA Instant. The beneficiary receives a euro credit on a normal bank account, with no wallet, no white paper and no MiCA question on their side. Since the EU instant payments regulation, payment service providers in the euro area are required to be able to receive instant credit transfers, which makes same-day final delivery the normal case rather than the exception.

For most non-EU banks and MSBs with a mixed beneficiary base this is the route that scales, because SEPA reach covers every euro account and the token exposure never leaves the interbank layer.

For most non-EU banks and MSBs with a mixed beneficiary base this is the route that scales, because SEPA reach covers every euro account and the token exposure never leaves the interbank layer.

Where StableNet fits

StableNet, built by SpendTheBits, is a cross border B2B payment and settlement platform for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs. For an institution paying into the EU it supports both routes described here: digital asset settlement in regulated stablecoins such as USDC on public blockchains, and crypto-to-fiat off-ramp with last-mile delivery in local fiat, including SEPA. The platform is ISO 20022 native, so the euro instruction travels as a pacs.008 inside a head.001 envelope, the acceptance returns as a pacs.002 and any unmatched payout comes back as a pacs.004, all tracked by UETR against the on-chain transaction hash. FATF Travel Rule data is carried in IVMS101 form, with sanctions and PEP screening, wallet screening and KYT applied before release, and a tamper evident audit trail records each decision. Customers keep custody throughout. SpendTheBits is a Bank of Canada registered payment service provider and a named finalist in the Swift Hackathon 2026 Technical Challenge.