Regulation

Reverse solicitation under MiCA after July 1, 2026

What MiCA Article 61 still allows a non-EU payout provider after July 1, 2026, why ESMA reads it narrowly, and what an EU business should check before signing.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: Reverse solicitation under MiCA after July 1, 2026
Cover image for Lumx blog article: Reverse solicitation under MiCA after July 1, 2026

Reverse solicitation under MiCA is a narrow exception: a non-EU firm may serve an EU client without a MiCA authorisation only if the client made the first move at its own exclusive initiative and the firm never solicited it (Article 61, Regulation (EU) 2023/1114). Since July 1, 2026 ESMA reads it strictly, and it does not relax for business clients.

What Article 61 says

Article 59 sets the rule: a person shall not provide crypto-asset services within the Union unless it is authorised as a crypto-asset service provider under Article 63 (a CASP), or is a credit institution, electronic money institution or another regulated entity allowed to provide them under Article 60. The article has no exception for business clients and none for payouts.

Article 61 is the carve-out. Where a client established or situated in the Union initiates the provision of a crypto-asset service by a third-country firm at its own exclusive initiative, the authorisation requirement in Article 59 does not apply to that service for that client. Three further provisions close the door around it.

  • A third-country firm that solicits clients or prospective clients in the Union, directly or through someone acting on its behalf, regardless of the means of communication, cannot claim the client came on its own.

  • That holds notwithstanding any contractual clause or disclaimer saying otherwise.

  • A client's exclusive initiative does not entitle the firm to market new types of crypto-assets or crypto-asset services to that client.

So the exception is defined by what the firm did before the contact, not by what the contract says after it.

What changed on July 1, 2026

The transition for providers that operated under national law before December 30, 2024 ended on July 1, 2026. The ESMA statement of April 17, 2026 says any entity providing crypto-asset services to EU clients without a MiCA licence after that date is in breach of EU law and must cease offering them. The MiCA rules for payment companies covers the dates and the Article 143 transition; the MiCA and GENIUS Act dates puts them next to the US ones.

The same statement reminds market participants that entities established outside the EU are, outside the narrow exception of reverse solicitation, not permitted to provide services that qualify as MiCA services to EU investors or to solicit EU clients. ESMA's public statement of June 23, 2026 repeats it and footnotes the exception as services provided strictly at the client's own exclusive initiative under the narrow reverse solicitation regime.

Luxembourg's financial regulator, the CSSF, described the risk in its communiqué of July 2, 2026. It says providers without an EU authorisation that already serve EU customers may increasingly rely on the exemption, that providers that wrongly rely on it may be prohibited from providing services, and that this is a risk for customers when accounts must be closed at short notice.

What counts as solicitation under the ESMA guidelines?

The ESMA guidelines on reverse solicitation, published on February 26, 2025 under Article 61(3), tell national authorities how to read the word. Solicitation is construed broadly and in a technology-neutral way, and a general brand advertisement with a wide reach can count. The client's own exclusive initiative, in contrast, is construed narrowly, and the assessment is a factual one.

Situations from the ESMA guidelines (February 26, 2025) and what they say about the exception.

Situation

Reading in the guidelines

Where

Regional SEO: a country-code domain, EU-country subdirectories, geo-targeted link building

Likely solicitation

Annex, Guideline 1

A website in an EU language that is not customary in international finance, with no home market using it

Likely solicitation

Annex, Guideline 1

Sponsoring an EU- or Member State-centric sporting event

Likely solicitation

Annex, Guideline 1

A paid EU-based influencer

Likely solicitation

Annex, Guideline 2

An EU bank or payment firm redirecting its clients to the third-country firm

Breach of MiCA, including inside the same group

Guideline 2, para. 22

Purely educational material that does not point to the firm or its services

Not solicitation

Guideline 1, para. 17

An independent review the firm did not know of, consent to or encourage

Not solicitation

Guideline 2, para. 21

A push notification two months after the first transaction inviting the client to trade more

Not the client's own initiative

Annex, Guideline 3

Offering a bundle of services to someone who asked for one

Not the client's own initiative

Annex, Guideline 4

Two lines matter most for a provider's contract. Contractual arrangements or disclaimers cannot supersede contrary facts. And a third-country firm should be able to provide records tracking the relationship with the client, including whether the client took the initiative for a new product.

On repeat business, the guidelines are strict. If a client contacts the firm to buy crypto-asset X, the firm may at that moment market assets of the same type, but it may not market further transactions in X to that client a month later.

Why business-to-business does not change the answer

Some companies assume MiCA is a consumer rule and that a business buying payouts from a foreign provider sits outside it. ESMA's April statement closes that reading: the prohibition on non-EU entities providing MiCA services to EU clients or soliciting them "also applies in a business-to-business context". The June statement says the same.

The reason ESMA gives is outsourcing. MiCA prohibits a CASP from outsourcing or delegating certain services, notably custody, to entities that are not authorised as CASPs, so an authorised EU provider cannot hand the work to an unauthorised third-country entity and keep serving its clients. ESMA asks CASPs to make sure their outsourcing and delegation arrangements do not end with services reaching EU clients through unauthorised third-country entities.

Article 61 itself speaks of "a client established or situated in the Union" and does not limit the word to consumers. A company can be that client. The exception then depends on the same two facts as for an individual: who made the first move, and what the provider has done in the EU since.

What an EU business should check before it signs

Put these questions to a non-EU payout provider, and keep the answers.

  1. Which legal entity will contract with us? ESMA warns that MiCA protections apply to the specific authorised EU entity, not to other companies of the same group and not to non-EU entities, and that providers may share one brand across several companies.

  2. Is that entity listed as authorised in the ESMA interim MiCA register, and for which services? A credit institution or an electronic money institution may be allowed under Article 60 without being a CASP.

  3. If the entity is outside the EU, what is the written basis? A provider relying on Article 61 should be able to show records of how the relationship began.

  4. Did we contact the provider, or did it reach us? Look for what the guidelines list: advertising aimed at the EU, an EU-language site, a local domain or subdirectory, sponsorships, paid creators, events.

  5. Does the service stay inside what we asked for? New types of services need a new, separate initiative from us each time.

  6. Are we passing the provider to our own users? An EU regulated entity that redirects its clients to a third-country firm breaches MiCA under the guidelines, and a CASP that outsources custody must use an authorised entity.

  7. What happens if the provider is told to stop? The CSSF warns of accounts closed at short notice. We want a way to move balances and a second provider before we need one.

I would not accept a reverse solicitation clause as an answer to a compliance question. The clause says what the parties agreed, and the guidelines say contracts do not decide it, so what a company needs from a provider is the facts of how the relationship began and the name of an EU entity, or a plan that does not depend on the exception.

When reverse solicitation is the wrong basis

For a product. A company that builds a flow for European customers on a non-EU provider's exception is building on something that does not scale: each client has to come on its own, and nothing the provider does to attract EU clients is allowed.

For a provider that markets in the EU. Once a firm advertises, sponsors or targets Member States, it may be treated as soliciting. The guidelines mention precautionary measures such as not accepting new EU client accounts or geo-blocking access.

For a group structure. ESMA says providers should serve EU clients through their authorised EU entities, even when the group trades under one brand, and that MiCA protections do not extend to other companies of the same group.

For a regulated EU referrer. A bank, an e-money institution or a payment firm that points its clients to a third-country firm is outside what the guidelines allow, whether or not the firm belongs to the same group.

When no crypto-asset service is involved. A payout that moves only fiat through a payment institution is a payments question under other EU law, and Article 61 does not come into it. The off-ramping USDC to euros shows where the stablecoin leg ends and the bank leg starts, and the list of SEPA countries shows where the euro leg reaches.

What this looks like with Lumx

Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

<!-- LUMX REGULATORY PARAGRAPH: needs Caio and legal read --> Lumx's own statements as of November 9, 2026: the EUR and GBP legs run through a banking partner authorised as an EMI (electronic money institution) by the UK Financial Conduct Authority and as a financial institution by the MFSA (the Malta Financial Services Authority). Lumx onboards customers in the United Kingdom, Hong Kong and Singapore by reverse solicitation, and does not market or prospect in those countries. Lumx is not a bank.

The licenses page lists what Lumx and its partners hold, and the USDC to EUR page shows how the EUR payout leg works over SEPA. The UK rules for GBP payments cover the UK side of the same question, and own licence versus partner licence and what a VASP is explain the partner-licence model.

Methodology and sources

Read on November 16, 2026:

Quotations are from these texts. Whether a particular provider can rely on Article 61 is a factual question for counsel and for the national authority in the Member State concerned. Lumx's statements are its own, dated above.

Verified on November 16, 2026. Operational context, not legal, tax, or investment advice. Regulation (EU) 2023/1114 (MiCA) checked against eur-lex.europa.eu on November 16, 2026.

Cover photo: Dmitry Voronov on Unsplash.

  • Is reverse solicitation still allowed under MiCA after July 1, 2026?

    Yes, as a narrow exception. Article 61 of Regulation (EU) 2023/1114 removes the authorisation requirement only when the EU client initiated the service at its own exclusive initiative and the third-country firm did not solicit it. ESMA and the CSSF both describe it as narrow, and the CSSF warns that providers relying on it wrongly may be prohibited from providing services.

  • Does reverse solicitation apply to business clients?

    Article 61 refers to a client established or situated in the Union and does not exclude companies. ESMA's April and June 2026 statements say the prohibition on non-EU firms serving or soliciting EU clients also applies in a business-to-business context.

  • Can a contract clause prove the client came on its own?

    No. Article 61(1) says the rule on solicitation applies notwithstanding any contractual clause or disclaimer purporting to state otherwise, and the ESMA guidelines say contractual arrangements or disclaimers cannot supersede contrary facts. The assessment looks at what the firm did, including its marketing and the records of how the relationship began.

  • Can a non-EU provider keep marketing to a client it already serves?

    Only inside the original request. Article 61(2) says a client's own exclusive initiative does not entitle the firm to market new types of crypto-assets or services. The ESMA guidelines add that the timing matters: marketing the same type of service at the moment of the original request may be allowed, but marketing further transactions a month later is not.

  • How does an EU company check whether a provider is authorised?

    Look the legal entity up in the ESMA interim MiCA register, which lists authorised crypto-asset service providers in the EU, and check the entity named in the contract, not only the brand. ESMA says MiCA protections apply to the specific authorised EU entity and not to other companies of the same group.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

reverse-solicitation-mica-non-eu-payout-providers

A

reverse-solicitation-mica-non-eu-payout-providers

Reverse solicitation under MiCA after July 1, 2026

Copy link

Copied!

reverse-solicitation-mica-non-eu-payout-providers

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Regulation

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.