Reverse Solicitation Under MiCA: The Article 61 Boundary

Skip key takeaways

Key takeaways: reverse solicitation under MiCA Article 61 6

Updated July 21, 2026

What Article 61's exclusive-initiative exemption actually permits, how broadly ESMA's guidelines construe solicitation, the broker-model opinion's warning on group-venue routing and where NCA adoption of the guidelines still has gaps.

• Since 1 July 2026 a third-country crypto firm without CASP authorization has one legal route to EU clients Since 1 July 2026 a third-country crypto firm without CASP authorization has one legal route to EU clients, Article 61 reverse solicitation, an exemption the broker-model opinion says should not be assumed nor exploited to circumvent MiCA.
• Article 61 carries its own anti-abuse devices in the statute itself Article 61 carries its own anti-abuse devices in the statute itself: solicitation through connected persons counts, disclaimers are void by statute and a client's initiative never licenses marketing of new types of crypto-assets.
• ESMA's guidelines of 26 February 2025 (ESMA35-1872330276-2030) construe solicitation broadly and technology-neutrally ESMA's guidelines of 26 February 2025 (ESMA35-1872330276-2030) construe solicitation broadly and technology-neutrally, ads, sponsorships, paid influencers, EU-language websites, country-targeted SEO and even public brand advertising can kill the exemption, and they have applied since 27 April 2025.
• The exemption is transaction-bound, same-type marketing is allowed only in the context of the original transaction The exemption is transaction-bound, same-type marketing is allowed only in the context of the original transaction and ESMA's own example rules out marketing to the same client a month later.
• The broker-model opinion warns NCAs against "legal cover" structures The broker-model opinion warns NCAs against "legal cover" structures, systematic order routing to group venues, missing unaffiliated-venue analysis, trading on the offshore brand and skewed revenue flows are very likely indications assessed holistically, never from a single factor.
• Per ESMA's compliance table of 10 July 2026 every designated EU competent authority complies with the guidelines while Poland and Romania remain non-compliant by default for lack of a designated authority Per ESMA's compliance table of 10 July 2026 every designated EU competent authority complies with the guidelines while Poland and Romania remain non-compliant by default for lack of a designated authority, and the enforcement record so far is warning lists, 164 NCASP records with 162 from Consob in our 20 July 2026 snapshot, not fines.

Copy takeaways

If your platform relies on reverse solicitation to serve EU clients, or routes EU orders to an offshore group venue and needs to know how that reads under the broker-model opinion, we can walk through what a defensible boundary looks like for your architecture.

See our MiCA compliance software development services

The MiCA transitional period ended on 1 July 2026. A third-country crypto firm that serves EU clients today without a CASP authorization has exactly one legal basis left to stand on, Article 61 reverse solicitation, and it is an exemption regulators have spent two years narrowing to a keyhole. Our own ESMA register data study, snapshot 20 July 2026, counts 295 active authorized CASPs against the 1,200 or more national VASP registrations industry analyses counted before the transition, so most firms that used to serve EU clients never became CASPs at all. ESMA's own non-compliant entities register already lists 164 unauthorized operators in that same snapshot, 162 of them flagged by Italy's Consob alone.

In short: Article 61 lets a third-country firm provide a crypto-asset service to an EU client without authorization only where the client initiated the relationship at its own exclusive initiative, with no solicitation by the firm or anyone acting on its behalf. ESMA's guidelines of 26 February 2025 (ESMA35-1872330276-2030) construe solicitation broadly, in a technology-neutral way, everything from banner ads to sponsorship deals to a website written in an EU language for no other reason. Disclaimers do not help, the exemption expires at the end of the original transaction, and ESMA's freshest compliance table, dated 10 July 2026, shows Poland and Romania still without a designated competent authority for the guidelines ten days after the grandfathering deadline passed. We build the geo-fencing, onboarding and audit-trail infrastructure that turns "the client came to us" from a claim into a queryable fact.

What Article 61 actually says

Article 61's exemption has a precise shape. ESMA's own broker-model opinion restates the first subparagraph exactly: "This exemption... is applicable where a client established or situated in the Union initiates at its own exclusive initiative the provision of a crypto-asset service or activity by a third-country firm." Where that condition holds, the Article 59 authorization requirement simply does not apply to that one provision of service.

The statute does not stop there. Its second subparagraph, quoted verbatim in the opinion's own footnote, closes the obvious workaround: "the crypto-asset services of a third-country firm should not be deemed to be services provided on the own initiative of the client where a third-country firm - including through an entity acting on its behalf or having close links with such third-country firm or any other person acting on behalf of such entity - solicits clients or prospective clients in the Union, regardless of the means of communication used for the solicitation, promotion or advertising in the Union." A third subparagraph then kills the paperwork defense outright: "The second subparagraph shall apply notwithstanding any contractual clause or disclaimer purporting to state otherwise."

Article 61(2) adds a second limit that has nothing to do with who initiated contact: a client's own exclusive initiative "shall not entitle a third-country firm to market new types of crypto-assets or crypto-asset services to that client." And Article 61(3) is the source of everything below, it mandated ESMA to issue guidelines specifying when a third-country firm is deemed to solicit EU clients and how supervisors should detect and prevent circumvention.

Three anti-abuse devices are therefore already in the Level 1 text before any guideline exists: solicitation through connected persons counts, disclaimers are statutorily void and a client's initiative never licenses marketing of new products. The guidelines below did not invent the strictness. They operationalized it.

Article 61 did not invent this architecture. It follows the reverse-solicitation model of Article 42 of MiFID II, which uses the same exclusive-initiative wording for third-country investment firms, so ESMA's narrow reading imports years of supervisory history already built up under that regime rather than starting from a blank page.

The ESMA guidelines: status, dates and what comply-or-explain means

The operative document is "Guidelines on situations in which a third-country firm is deemed to solicit clients established or situated in the EU and the supervision practices to detect and prevent circumvention of the reverse solicitation exemption under the Markets in Crypto Assets Regulation (MiCA)", ESMA35-1872330276-2030, dated 26 February 2025. A separate December 2024 Final Report, ESMA35-1872330276-1899, covers the consultation feedback and is a different document from the guidelines themselves.

Who the guidelines bind is not the same question as who they apply to. Scope paragraph 1 reads: "These guidelines apply to competent authorities, as defined in Article 3(1)(35) of MiCA and, as regards Section 5, third-country firms." Section 5, the solicitation guidelines proper, is therefore addressed to third-country firms directly. But the instrument's legal force runs through Article 16(3) of the ESMA Regulation, under which national competent authorities "should make every effort to comply with these guidelines" on a comply-or-explain basis. That is not the same thing as a rule binding firms or courts directly, and it is worth pausing on: this is the same non-binding-guidance layer our companion article on ESMA Q&A 2552 works through for a different corner of MiCA, an administrative interpretation that steers supervisory practice without being law a court must follow.

The application date is now settled. The guidelines apply 60 calendar days from the date of their publication on ESMA's website in all official EU languages, and that publication landed on 26 February 2025, which puts the application date at 27 April 2025. National competent authorities had two months from that same publication date to notify ESMA whether they comply, intend to comply or do not comply, a deadline that fell on 26 April 2025.

The two most quoted lines in this whole cluster come from two different documents, and the difference matters. The famous sentence that this exemption "should be understood to be very narrowly framed and, as such, should be regarded as an exception to the rule of Article 59 of MiCA," and that it "should not be assumed, nor exploited to circumvent MiCA," is not in the guidelines at all. It is in the broker-model opinion, at paragraph 17, itself citing an ESMA statement from 17 October 2023, regulators said this before MiCA even applied in full. The guidelines' own formulation, at paragraph 23, is shorter and no less firm: "The client's own exclusive initiative should be construed narrowly."

What counts as solicitation

Guideline 1 sets the baseline rule at paragraph 11: "The solicitation of clients by third-country firms should be construed broadly and in a technology-neutral way." Paragraph 12 then supplies the means list, given here in full because the breadth is the point:

Solicitation "includes the promotion, advertisement or offer of crypto-asset services or activities to clients or prospective clients in the Union by any means", including without limitation internet commercials, brochures, telephone calls, emails, banners and pop-ups and similar tools on websites and social media, face-to-face meetings, press releases, other forms of physical or electronic means including websites, social media platforms and mobile applications, participation in road shows and trade fairs, invitations to events, affiliation campaigns, retargeting of advertising, invitations to fill in a response form or follow a training course, messaging platforms and sponsorship deals.

General brand advertising is not exempt from that list either. Paragraph 13, verbatim: "Promotions, advertisements, marketing and offers of a general nature such as brand advertisements, and which are addressed to the public (with a broad and large reach), may also constitute solicitation." A footnote example makes the point concrete rather than abstract: a third-country firm "may be sponsoring an international sporting competition in which Member States national teams or EU athletes may also be entering. MiCA does not prohibit such sponsorship deals. However, as a consequence of this, the firm should be considered to be soliciting clients in the EU and would thus be unable to benefit from the reverse solicitation exemption."

ESMA names the practical countermeasures itself. Paragraph 16 points to not accepting new EU client accounts, and a footnote spells out the two technical measures that follow from it, IP-based website geo-blocking and keeping a mobile application out of EU app stores. The Annex adds a set of concrete indicators that read like an SEO audit checklist rather than a legal test: regional or country-specific SEO through country-code domains such as .fr, .es or .at, EU country subdirectories and geo-targeted link building, geo-targeted digital ads, a website written in an official EU language "which is not customary in the sphere of international finance" with no non-EU explanation for the choice, sponsoring an EU or Member State-centric sporting event and group structures that leave clients unable to differentiate between an EU-regulated entity and a third-country affiliate. There is a narrow carve-out for genuine education, paragraph 17: purely educational material and industry events are not solicitation, until the audience is pointed to the firm's website, handed access means or brochures or invited to fill in a client profile.

Who can do the soliciting

Solicitation counts "irrespective of the person through whom it is performed", and acting on a firm's behalf can be established contractually or, per paragraph 19, "implicitly via an informal agreement". Guideline 2's most quoted indication is influencers. Paragraph 20 names them directly, "Such persons can include so-called influencers", and lists indications: directing the audience to the firm's website, providing access means, offering promotional deals or displaying the firm's logo. Remuneration is a strong but not exclusive marker: "The existence of any form of remuneration or benefit (monetary or non-monetary)... should be a strong indication that the third party is acting on behalf of the third-country firm. The lack of remuneration or benefit should, however, not necessarily exclude" it. There is a narrow carve-out here too, paragraph 21, for independent reviews the firm genuinely had no hand in: they are not solicitation where the firm "does not have knowledge of the review and has not consented, encouraged or otherwise facilitated it".

One provision in Guideline 2 is underused in commentary and deserves more attention than it usually gets, because it reaches regulated EU institutions rather than crypto marketers. Paragraph 22, verbatim: "an EU credit institution, investment firm or payment service provider should not redirect clients (for instance, via its website) to crypto-asset services provided by a third-country firm. This applies whether that third-country firm is part of the same group or not." An EU bank or payment institution that links out to an offshore crypto affiliate is inside the same solicitation ban as any influencer, group affiliation included.

The exclusive-initiative test and the same-type rule

Paragraph 23's narrow-construction standard, already quoted above, pairs with paragraph 24's factual test: "The assessment... should be a factual one. Contractual arrangements or disclaimers cannot supersede contrary facts."

Timing is where the exemption actually runs out. Marketing of same-type assets is only permitted in the context of the original transaction, and ESMA's own example in paragraph 27 draws the line concretely: "if the client contacts the third-country firm to buy crypto-asset X, the firm may - at this point in time - market to the clients crypto-assets of the same type. However, the third-country firm would not be entitled to market further crypto-asset X transactions or transactions in similar crypto-assets to the client a month later." A month is not a rule of thumb ESMA states as a bright line, it is the guidelines' own illustration of how quickly the window closes. The Annex reinforces it with ordinary retention mechanics as breach examples, push notifications sent two days or two months after the initial transaction flagging "what crypto-assets are trending" or a temporary promotion.

Paragraph 28 sets the evidentiary expectation that follows directly from that timing rule: "Third-country firms should be able to provide records tracking the relationship with the client and, in particular, whether the client has taken the initiative to receive crypto asset services with respect to a new product." That is an audit-trail requirement stated in a supervisory guideline, and it is the reason a firm relying on Article 61 needs more than a marketing policy, it needs a record it can produce years later.

Paragraph 32 works through what does not count as the same type, and it is worth reading as a paraphrase of the guidelines' logic rather than a verbatim list: utility tokens, asset-referenced tokens and e-money tokens are treated as different types from each other; assets built on different underlying technology are different types; e-money tokens referencing different official currencies are different types; a fiat-based asset-referenced token differs from a crypto-weighted one; liquid and illiquid assets differ; and an asset with an identifiable offeror differs from one without, a distinction that matters well beyond this test since MiCA treats crypto-assets with no identifiable issuer differently elsewhere in the regulation too. Paragraph 33 adds a caution against reading the list the other way round, similarity on one dimension does not automatically make two assets the same type on every other dimension.

The guidelines say nothing about clients onboarded before 1 July 2026 as a class, nothing in them grandfathers a pre-existing relationship, so on our reading each new transaction for such a client must independently satisfy the exclusive-initiative and same-type tests, exactly as it would for a client who arrived yesterday. ESMA's wind-down statement of 23 June 2026 (ESMA75-113276571-1710) points the same way: unauthorized CASPs should limit services for existing EU clients to selling, transferring or closing positions, with a footnote carve-out only for services strictly provided at the client's own exclusive initiative under the narrow reverse solicitation regime.

The broker-model opinion: routing, letter-boxes and legal cover

The second primary document in this cluster is ESMA's Opinion on broker models, ESMA75-453128700-1048, dated 31 July 2024, addressed primarily to NCAs. It targets what the opinion calls Multifunction Crypto-asset Intermediaries, a category borrowed from the Financial Stability Board's own definition and illustrated with FTX by name, firms or groups that combine broad service ranges typically centered on operating a trading platform.

The opinion's core concern is stated in one sentence at paragraph 19: NCAs "should notably ensure that the application does not aim at obtaining a 'legal cover' in the Union for third-country firms which seek to solicit clients or prospective clients in the Union through a MiCA-authorised entity (typically belonging to the same group), whilst still providing services from outside the Union." That is the pattern the whole opinion is built to catch, an EU-authorized broker acting as a front door for an offshore platform that never itself sought authorization.

Paragraph 23 sets out four factors the opinion calls "very likely indications" of exactly that pattern: an EU-authorized broker that systematically routes orders to the group's execution venue outside the Union; a broker that has not analyzed the availability of unaffiliated execution venues or cannot justify excluding them from its execution policy; a broker that relies on the reputation and brand of the non-EU exchange to attract EU clients; and a broker with little or no independent revenue from its EU brokerage activity, or revenue flows that diverge significantly from what an independent party would expect. It is important to state the legal weight of that list precisely, because commentary sometimes overstates it: paragraph 24 requires a holistic approach, and no single factor "singlehandedly" establishes a breach. The opinion permits presuming solicitation only after a holistic assessment of all circumstances, never from a single indicator.

Two further practices get flagged as related risk signals rather than as automatic violations. Riskless back-to-back execution against a group's non-EU venue "may constitute a relevant indication of a strategy to structurally circumvent the MiCA regime", and streaming quotes sourced from the non-EU liquidity provider is a further flag alongside it. The opinion's substance concerns are not new invention either, they extend ESMA's May 2017 Brexit Opinion, whose principles required that outsourcing to third countries be "strictly framed and consistently supervised" and that delegation "did not result in those entities becoming letter-box entities". The opinion states that "mutatis mutandis, the principles two to eight of the Brexit Opinion should apply" to MiCA authorizations, the same substance-over-form logic UK-relocating firms faced after 2017 now applies to crypto brokers claiming an EU base.

The remaining sections of the opinion round out the same theme from three angles. On conflicts of interest, an ex-ante structural decision to route execution to the group's own third-country platform "should be considered as a very strong indication that such structural conflict of interest has not been properly managed", and disclosure alone does not fix it. On best execution, the Article 78 factors apply in full, and reliance on a single execution venue "should be considered unlikely" to deliver best results across a broad asset range, with regular execution-quality reviews expected under Article 78(6). And on custody, Article 75(9) requires that the non-EU execution venue never take custody or administration of EU clients' crypto-assets at any point, with a narrow carve-out only for the moment of settlement itself.

The requirement that an EU-authorized entity actually have substance in the Union, rather than functioning as a letter-box for offshore operations, is a statutory condition of MiCA Article 59 authorization in its own right, not an invention of the broker opinion. The opinion's own contribution is applying the Brexit Opinion's substance principles to MiCA specifically, described above; we keep the precise wording of Article 59's conditions out of this article rather than paraphrase them loosely.

Who has adopted this: the NCA map as of 10 July 2026

The freshest primary document in this cluster is also the one almost nobody cites: ESMA's compliance table on the reverse-solicitation guidelines, ESMA35-24871704-2592, dated 10 July 2026. It is the NCA-by-NCA comply-or-explain record required under Article 16(3), and reading it ten days after the grandfathering deadline passed turns up a finding that belongs in this article more than anywhere else in the cluster.

Every EU competent authority with a designated authority complies or intends to comply, BaFin in Germany, the AMF in France, Consob in Italy via an avviso dated 30 April 2025, CySEC in Cyprus and the CSSF in Luxembourg among them. Luxembourg implements through its own supervisory instrument, Circular CSSF 25/887, linked directly from the table. Outside the EU proper, Liechtenstein and Norway comply as EEA members and Iceland has not responded at all.

Two entries stand out. Poland and Romania are both marked, verbatim: "Non-compliance by default, pending designation by the Member State of the Competent Authority for the jurisdiction." Ten days after the transitional period ended on 1 July 2026, two Member States still had no designated MiCA competent authority for these guidelines to attach to, a gap in institutional readiness that sits directly beside the deadline that made Article 61 the only remaining legal doorway for third-country firms. Greece splits competence rather than lacking it, general jurisdiction sits with the HCMC while the Bank of Greece supervises CASPs that are also credit institutions, e-money institutions or payment institutions.

The guidelines' own supervision section tells NCAs what to look for in practice, and the list reads like an investigation playbook rather than abstract policy: searching for firms using local country phone codes or EU-hinting URL endings, running consumer surveys, deploying marketing monitoring tools capable of tracking social media activity, exchanging information with other authorities including police and tax bodies and following up on client complaints and whistleblowers.

Enforcement reality: warning lists, not fines

Here is the honest state of the enforcement record as of 21 July 2026: we found no published fine or sanction decision from any EU national competent authority grounded specifically in abuse of the reverse-solicitation exemption. That is not the same as saying the risk is theoretical, it is information about where enforcement currently sits, at the perimeter rather than in adjudicated cases.

What the record does show is warning lists. Our own parse of ESMA's non-compliant entities register counted 164 records of unauthorized operators in the 20 July 2026 snapshot, with 162 of them flagged by a single national authority, Italy's Consob, a near-monopoly on public perimeter work. Belgium's Financial Services and Markets Authority published a warning on 6 July 2026, days after the transitional period ended, naming six crypto-asset service providers it identifies as operating without authorization referencing the 1 July 2026 transitional expiry directly: Aurum Foundation, Bank Bit, Bithf Pro, Dxago, Global Dynamic Trade and ZeriaFunding.

The stakes of that timing are plain. Grandfathering ended on 1 July 2026. Any unauthorized third-country firm still serving EU clients from that date forward has no fallback position left, none, other than proving every one of those client relationships genuinely began at the client's own exclusive initiative under the narrow reading this article has walked through. Against 295 active authorized CASPs in our same 20 July 2026 register snapshot, that is a comparison worth sitting with: the firms doing this by the book are a known, counted population, and the ones operating outside it are starting to show up on named lists.

The consultation leaves this boundary untouched

The European Commission's MiCA review consultation, open until 30 September 2026, is effectively silent on reverse solicitation, so for third-country access the 2025 ESMA guidelines and the broker-model opinion remain the only operative layer, and our full analysis of the MiCA review consultation covers what is actually on the table.

Enforcing the boundary in code

ESMA's own guidance names the two technical measures that keep a third-country platform honest: geo-blocking EU IP access and keeping the app out of EU app stores. When we build these controls we treat them as compliance infrastructure, not settings, versioned blocklists, monitored bypass rates, alerts when EU-attributed traffic gets through. A geo-fence nobody watches is a disclaimer in disguise, and Article 61 already tells you what disclaimers are worth.

The guidelines expect a third-country firm to produce records showing the client took the initiative. That is an engineering requirement wearing legal clothes. We design onboarding flows that capture how every account actually arrived, referrer, campaign attribution or the documented absence of both, so that "the client came to us" is a queryable fact, not an affidavit written two years later.

Proving a negative is the hard part of reverse solicitation, showing a client was not acquired through EU-targeted marketing. The only way we know is to log the positive for everyone, every campaign, every audience definition, every geo parameter, so the absence of EU targeting is demonstrable from the same dataset an NCA would ask for.

ESMA's same-type pairs read like a product taxonomy, so we implement them as one: assets tagged by category, technology and liquidity, and cross-sell surfaces that check the tag before showing anything to a reverse-solicited EU client. The guidelines' breach examples are push notifications and trending lists, retention mechanics every exchange runs by default. Compliance here means suppression logic, not policy documents.

The register and warning-list numbers above make the point directly: the perimeter is now a published dataset. Platforms on either side of it get asked the same question sooner or later, show us how this EU client got here. We build systems where the answer already exists as a report you can produce on demand, not as a reconstruction project.

How Pharos Production helps

We build the geo-fencing, onboarding-attribution and audit-trail infrastructure that sits behind an Article 61 determination: initiative evidence captured at signup, marketing logs that prove the negative, same-type product gates and export-ready records for the day an NCA inquiry arrives. If your platform relies on reverse solicitation to serve EU clients, or routes EU orders to an offshore group venue and needs to know how that reads under the broker-model opinion, our MiCA compliance software development practice can walk through what a defensible boundary looks like for your architecture.

Sources: ESMA Guidelines on reverse solicitation under MiCA, ESMA35-1872330276-2030 (26 February 2025); ESMA Opinion on broker models, ESMA75-453128700-1048 (31 July 2024); ESMA Guidelines compliance table, ESMA35-24871704-2592 (10 July 2026); Regulation (EU) 2023/1114 (MiCA) Article 61; ESMA statement of 17 October 2023, ESMA74-449133380-441; ESMA Public Statement 23 June 2026 (ESMA75-113276571-1710); FSMA warning notice, fsma.be (6 July 2026); our own ESMA CASP register and non-compliant entities register raw-data analysis dated 20 July 2026.

FAQ

Last updated: July 21, 2026

Quick answers to common questions about custom software development, pricing, process and technology.

Expand all Collapse all

Search FAQs

Popular

Type to filter questions and answers. Use Topic to narrow the list.

Showing all 7

• ★ Featured question. What is reverse solicitation under MiCA?

  Copy link Copies a direct link to this answer to your clipboard.

  The exemption in Article 61 of MiCA. A third-country firm may provide a crypto-asset service to an EU client without a CASP authorization only where the client initiated the service at its own exclusive initiative.

  ESMA treats it as a narrow exception to the Article 59 authorization requirement, not a distribution model.

• ★ Featured question. Can a non-EU crypto exchange serve EU clients after 1 July 2026?

  Copy link Copies a direct link to this answer to your clipboard.

  Only with a CASP authorization or within genuine reverse solicitation. The MiCA transitional period ended on 1 July 2026, so a third-country exchange serving EU clients without authorization must show every client relationship was client-initiated with no solicitation by the firm or anyone acting on its behalf.

• Do disclaimers protect a reverse-solicitation model?

  Copy link Copies a direct link to this answer to your clipboard.

  No. Article 61(1) applies notwithstanding any contractual clause or disclaimer purporting to state otherwise, and ESMA's guidelines state that contractual arrangements or disclaimers cannot supersede contrary facts. The assessment is factual.

• What counts as solicitation under the ESMA guidelines?

  Copy link Copies a direct link to this answer to your clipboard.

  A broad, technology-neutral list: internet ads, banners and pop-ups, emails and calls, press releases, road shows, affiliation campaigns, ad retargeting, messaging platforms, sponsorship deals and paid influencers. Even general brand advertising reaching the EU public may qualify, and country-targeted SEO or an EU-language website are named indicators.

• Are the ESMA reverse-solicitation guidelines legally binding?

  Copy link Copies a direct link to this answer to your clipboard.

  Not directly. They are Article 16(3) ESMA Regulation guidelines, national competent authorities must make every effort to comply on a comply-or-explain basis, and Section 5 is addressed to third-country firms as well, but the guidelines bind neither firms nor courts directly.

  ESMA's compliance table dated 10 July 2026 shows every designated EU competent authority complying or intending to comply, with Poland and Romania non-compliant by default pending designation of a competent authority.

• How long does a reverse-solicitation relationship last?

  Copy link Copies a direct link to this answer to your clipboard.

  Only as far as the original transaction's context. Marketing of same-type assets is permitted only in the context of the original transaction, and ESMA's own example states a firm may not market further transactions to the client a month later, a new client-initiated request is needed for anything outside that window.

• Has any EU regulator fined a firm for abusing reverse solicitation?

  Copy link Copies a direct link to this answer to your clipboard.

  As of publication we found no published fine grounded specifically in reverse-solicitation abuse. Enforcement so far runs through warning lists, ESMA's non-compliant entities register held 164 unauthorized operators, 162 flagged by Italy's Consob, in our 20 July 2026 snapshot, and Belgium's FSMA named six unauthorized providers days after the transitional period ended.

I work with startup founders who need a dedicated software development team but don’t want to gamble on hiring, random outsourcing, or opaque delivery.
Most founders face the same problem sooner or later.
Early technical and team decisions lock the product into tech debt, slow delivery, missed milestones and constant re-hiring. By the time this becomes visible, fixing it is already expensive.

As a CTO and software architect, I help founders design, build and run dedicated development teams that work as a true extension of the startup. Not as a black-box vendor.

My focus is on complex products where mistakes are costly:

• Web3 and blockchain platforms
• FinTech and regulated products
• High-load startup systems
• MVP → scale transitions

We don’t do body-shopping.
We don’t sell generic outsourcing.

Instead, we help founders:

• build the right team structure from day one
• keep technical ownership and transparency
• scale delivery without losing control
• avoid vendor lock-in and hidden risks

Teams are aligned with the product roadmap, business goals and long-term architecture. Not just short-term velocity.