MiCA Q&A 2882 and the B2B Consultancy: The Perimeter Should Follow the Risk, Not the Recommendation
ESMA Q&A 2882 confirms MiCA advice is broader than MiFID II. Recommending an exchange or custodian to a corporate client may require a licence — or may not. The perimeter should follow the risk, not the recommendation.
Analysis of ESMA Q&A 2882 (18 June 2026) on the perimeter of advice on crypto-assets under MiCA Article 3(1)(24) versus MiFID II investment advice, published thirteen days before the Article 143(3) transitional periods expired on 1 July 2026. Core thesis: B2B consultancies providing regulatory analysis, vendor comparison and procurement support to corporate clients should not automatically fall within the advice perimeter; the licensing perimeter should follow the risk created by the activity, not merely the subject matter of the recommendation. Statutory divergence: MiFID II advice is transaction-triggered; MiCA Article 3(1)(24) adds a second prong covering personalised recommendations on the use of crypto-asset services, so steering infrastructure (exchange, custody) can trigger advice without naming a crypto-asset. Article 59 is activity-based; Article 81 attaches once inside; Q&A 2143 closes the tied-agent route. Five-prong Q&A 2882 test applied to B2B consultancy: recommendation; crypto transaction or crypto-asset service use; suitability/circumstances; not exclusively public; investor capacity. ESMA uses "may" / case-by-case, not "shall". Negative boundary: sole public, equally accessible CASP reference is not a recommendation. Prong 5 (investor capacity) is the strongest defence for corporate treasury/procurement: client may be procuring operational infrastructure, not acting as investor. Counterweight: Austrian FMA Specific Aspects guidance treats recommending suitable providers and financial integration into corporate systems as in-scope advice, while excluding legal/tax/audit and purely technical services — so compliance analysis has a lane outside, vendor recommendation is the risk. Proportionality critique: recommendation-only firm inherits Article 81 suitability, DORA financial-entity ICT obligations, €50k Class 1 capital / Article 67 overheads, and ESMA knowledge-and-competence CPD (ESMA35-24871704-2922) without holding assets, keys, or running platforms — regulatory osmosis. Adoption paradox: broad reading pushes specialists to become CASPs or go generic, thinning independent expertise institutions need. Three categories: (1) regulatory/technical consultancy — outside; (2) scored procurement/vendor selection — battleground; (3) investor suitability steering — clearly advice. Weak defences discarded: professional clients only; incidental advice (no MiFID Article 2(1)(c) equivalent); partner-licence umbrella (Q&A 2143); reverse solicitation (ESMA35-1872330276-1899/2030) unavailable to EU firms. Engagement structuring: requirements-first deliverables, reusable objective matrices, client-only fees, contractual category separation, document client capacity for prong 5. Seven diagnostic questions for consultancies. Not legal advice.
MiCA Q&A 2882 and the B2B Consultancy: The Perimeter Should Follow the Risk, Not the Recommendation MiCA Edge Cases | Where Innovation Meets Regulation On 18 June 2026, ESMA published Q&A 2882, confirming that the perimeter of advice on crypto assets under MiCA is broader than the perimeter of investment advice under MiFID II. Thirteen days later, on 1 July 2026, the last MiCA transitional periods expired under Article 143(3). Providing a crypto asset service in the EU without the required authorisation was no longer a transitional problem. Together, those two dates raise a question most B2B consultancies in this market have not yet asked themselves: Does recommending an exchange or a custodian to a corporate client now require a MiCA licence? ESMA's answer is: It may, depending on the circumstances. Our answer is: Not necessarily. And our position, stated at the outset, is that a consultancy providing regulatory analysis, vendor comparison and procurement support to corporate clients should not automatically fall within the advice perimeter. The correct legal test should be whether the activity is actually the type of advice MiCA was designed to regulate, and whether the activity creates the risks the CASP framework was built to control. That is our view. We will make the case for it from both sides, because a position that only survives contact with friendly readings is not a position. It is hopium. The Statutory Divergence: What Article 3(1)(24) Actually Changed Under MiFID II, investment advice is defined by a transaction based trigger: a personal recommendation in respect of one or more transactions in financial instruments. A firm that recommends a brokerage relationship but never recommends a trade sits, in most configurations, outside the perimeter. MiCA cut that anchor. Article 3(1), point 24, defines "providing advice on crypto assets" as offering, giving or agreeing to give personalised recommendations to a client, either at the client's request or on the initiative of the service provider, in respect of one or more transactions relating to crypto assets, or the use of crypto asset services . The second prong is the entire edge case. Because operating a trading platform, custody and exchange are themselves defined crypto asset services under Article 3(1), point 16, a personalised recommendation to use a specific exchange or custodian can satisfy the definition without any crypto asset ever being mentioned. Under MiFID II, the adviser is regulated for steering the investment. Under MiCA, the adviser can be regulated for steering the infrastructure. The distinction is not subtle. And since the definition is being cited loosely across the commentary: point 24, not point 25, not point 5. Point 15 defines the CASP itself. Article 59 makes authorisation mandatory. Article 81 attaches conduct obligations once you are inside. The perimeter question is whether you are inside. The Five Questions: What Q&A 2882 Actually Says ESMA did not declare that introductory and recommendation services are advice. It set out a series of questions that point toward the perimeter, with several elements that must be considered together: | Prong | Test | Application to a B2B consultancy | | | | | | 1 | Does the service constitute a recommendation? | Satisfied where the consultancy steers the client toward a preferred provider. Not satisfied by a neutral comparison. | | 2 | Is it in relation to crypto asset transactions or the use of crypto asset services? | Satisfied whenever the subject is an exchange, custodian or other CASP service. | | 3 | Is it presented as suitable or based on the person's circumstances? | Satisfied where the shortlist is tailored to the client's volumes, systems or jurisdiction. This is where engagement structure matters most. | | 4 | Is it issued otherwise than exclusively to the public? | Satisfied by a private deliverable. Public research fails this prong by design. | | 5 | Is it made to a person in their capacity as an investor or potential investor, or as an agent for one? | The most underanalysed prong, and in our view the strongest limb of the defence. | Two things deserve more attention than they have received. First, ESMA concluded that introductory services "may be regarded as advice on crypto assets for the purpose of MiCA, depending on the circumstances surrounding the recommendation." ESMA writes "shall" when it means shall. A case by case standard means the facts of the engagement determine the outcome, which means the facts can be structured. Second, ESMA stated the negative boundary explicitly: "providing solely a reference to a CASP (without further indications) equally accessible to all potential investors should not constitute a recommendation." Public, non personalised, equally accessible material is outside the perimeter. That is not an inference. It is the text. Two further points are settled and worth stating once, briefly, before moving on. The client's sophistication does not narrow the perimeter. Article 59 is activity based, and MiCA uses client type to scale conduct obligations, not to waive authorisation. And there is no agent route. ESMA Q&A 2143 confirms that MiCA has no framework for agents acting on behalf of CASPs, so a consultancy cannot shelter under a partner exchange's licence. Both points return, with their reasoning, under "The Arguments That Do Not Work" below. What remains genuinely open is where prong 3 ends, what prong 5 means for a corporate procurer, and whether the full CASP framework fits a recommendation only business. Nobody has litigated any of it yet. Prong Five: The Investor Capacity Question The fifth limb requires the recommendation to be made to a person: "in his capacity as an investor or potential investor or as an agent for an investor or potential investor." Consider what a corporate treasury is actually doing when it engages a consultancy to select a custody provider. It is not necessarily deciding whether to hold crypto assets. That decision may already have been taken at board level, on legal, tax, strategic and financial advice, before the consultancy arrives. It is deciding which regulated infrastructure will hold what it has already decided to hold. The criteria read like an IT procurement scorecard: MPC or HSM architecture; segregation model; insurance coverage; API functionality; settlement integration; incident response; pricing. A company selecting stablecoin settlement rails to replace correspondent banking for supplier payments is further still from the investor frame. It is buying plumbing. The personalised part is not the difficult bit. If a consultancy spends three months understanding your systems, jurisdiction, transaction volumes and custody requirements, pretending the recommendation is generic is not going to fool anyone. The difficult question is what the client is being advised as . Is the client acting as an investor or potential investor? Or is it acting as an undertaking procuring operational infrastructure? The argument, then: a corporate client procuring operational infrastructure is not ac