A crypto-asset service provider preparing for MiCA authorisation discovers that the Regulation itself – the 15,000-word framework text adopted in May 2023 – is only the starting point. Below it sit dozens of technical standards and guidelines, each translating a high-level obligation into a testable compliance requirement. Some are final and in force; others remain in draft. The business question is which measures apply to your authorisation class, when they bind, and what evidence the regulator expects at application and in ongoing supervision. This page maps the Level 2 and Level 3 architecture under MiCA, groups the measures by obligation area, and explains the compliance work each one triggers for an authorised CASP.
MiCA establishes a three-tier framework. Level 1 is the Regulation itself – the base text setting out the authorisation perimeter, the prohibited activities, the governance and prudential requirements. Level 2 comprises binding technical standards drafted by ESMA and adopted by the Commission as delegated or implementing regulations; these have the force of law. Level 3 consists of ESMA guidelines – non-binding but applied on a "comply or explain" basis by national competent authorities. An NCA that departs from a guideline must document its reasoning, and supervisory convergence across the Union turns on adherence to the Level 3 layer. For a CASP, the distinction matters: a Level 2 standard is a direct legal obligation; a Level 3 guideline shapes how the NCA interprets your submission and scores your processes during the on-site review.
This analysis addresses the roadmap for operators holding or applying for CASP authorisation, for issuers of asset-referenced tokens or e-money tokens, and for entities that fall within MiCA's ancillary regimes (marketing communications, white-paper disclosures, market-abuse prohibitions). The measures discussed here are those published or in advanced draft as the Level 2 and Level 3 packages took shape through ESMA's work programme. Where a measure is not yet final, we mark it as proposed. Every numeric threshold, capital figure, effective date and procedural timeline is written qualitatively or flagged for verification – MiCA's implementing framework is large, technical and still evolving, and a reliable answer on any given standard requires checking the most recent Official Journal text and the NCA's local transposition guidance.
What are Level 2 and Level 3 measures under MiCA?
Level 2 and Level 3 measures are the technical detail that operationalises MiCA's high-level framework. Level 2 standards are legally binding instruments – regulatory technical standards (RTS) and implementing technical standards (ITS) – drafted by ESMA, endorsed by the Commission and published in the Official Journal. Level 3 consists of ESMA guidelines, which national competent authorities apply on a "comply or explain" basis. Together they translate MiCA's general obligations into specific tests, formats, capital formulae and disclosure templates. A CASP authorisation file that omits a Level 2 data point or fails to address a Level 3 guideline will be marked incomplete at the first NCA screening.
The architecture mirrors the approach used under MiFID II, AIFMD and the Payment Services Directive – a base regulation setting principles, a layer of Commission delegated acts filling in technical detail, and a suite of ESMA or EBA guidelines harmonising supervisory practice. The difference with MiCA is timing: the Regulation entered into force in June 2023, but many of the standards were still in consultation or awaiting Commission adoption through the second half of 2024 and into 2025. This phased roll-out creates a compliance gap for early movers – an applicant in late 2024 worked from draft standards and adjusted the file as final texts emerged; an applicant in 2026 faces a complete, static rulebook.
In our cross-border practice, the distinction between Level 2 and Level 3 affects not only the authorisation strategy but also the portability of the authorisation once granted. A CASP passport relies on harmonised implementation: if one member state gold-plates a Level 3 guideline into a stricter local rule while another applies it lightly, the passporting CASP encounters divergent expectations. ESMA's role is to contain that divergence, but at the application stage a conservative approach assumes the strictest reasonable interpretation of each guideline until the NCA signals otherwise.
How are Level 2 standards adopted and when do they bind?
A Level 2 standard begins as an ESMA mandate embedded in the Level 1 text. MiCA contains multiple empowerments for the Commission to adopt delegated acts specifying, for example, the calculation of own funds, the content of a white paper, the criteria for assessing a significant ART or EMT issuer, the format of a prospectus supplement. ESMA drafts the standard in consultation with market participants and national authorities, submits it to the Commission for endorsement, and the Commission publishes it as a regulation. The standard enters into force twenty days after publication in the Official Journal unless the text specifies a later application date.
The phasing matters for transitional applicants. If you applied for CASP authorisation before a particular Level 2 standard was final, the NCA may have assessed your file under the general MiCA provisions and the best-available draft guidance. Once the standard is adopted, the NCA typically requires an update to the file or a supplementary submission addressing the new data points. If your authorisation was already granted, the standard applies from its stated application date, and you adjust your systems and procedures accordingly – typically with a few months' lead time built into the legislative text.
For operators we advise entering multiple member states, the application-date variation across standards creates a rolling compliance calendar. A prudential standard finalised in mid-2025 with a six-month implementation window may bind before a conduct-of-business standard still in draft. The licensing roadmap must account for this stagger: an initial authorisation submission covers the obligations that are final at the time of filing; a monitoring process tracks emerging standards and schedules the necessary policy updates, system changes and NCA notifications as each new measure comes into force.
Which Level 2 measures affect CASP authorisation?
The core Level 2 package for CASPs addresses own-funds calculation, governance and control frameworks, conflicts of interest, outsourcing, safeguarding of client assets, complaints handling, and the content and format of the authorisation application itself. Each standard translates a MiCA article into a testable criterion. The own-funds RTS, for instance, defines the capital base, specifies which instruments count as Tier 1 or Tier 2 capital, sets the risk-weighted exposure calculation for crypto-asset holdings, and prescribes the liquidity buffer. The governance RTS elaborates the fit-and-proper assessment for management-body members, the independence criteria for the compliance function, and the minimum content of the risk-management framework.
In practice, an authorisation file must demonstrate compliance with every final Level 2 standard applicable to the activities you seek to conduct. If you are applying for custody and trading-platform operation, your submission addresses the safeguarding RTS (client-asset segregation, wallet-security standards, insurance or guarantee arrangements) and the market-integrity RTS (pre-trade and post-trade transparency, order-handling rules, best-execution criteria). If you are also acting as a broker or adviser, the conflicts-of-interest standard applies, and you document the conflicts register, the disclosure templates and the escalation procedure.
One area that catches applicants is the interplay between MiCA's Level 2 measures and the cross-cutting AML/CFT regime. MiCA itself does not regulate AML – that sits under the AML Regulation and the Transfer of Funds Regulation (the "Travel Rule" instrument). But several MiCA Level 2 standards reference AML processes as part of the governance or client-onboarding framework. An applicant must show that its AML policies meet both the AMLD/Travel Rule baseline and the MiCA governance standard – the NCA will not grant authorisation if the AML component is incomplete, even though AML supervision may formally sit with a separate authority.
For an initial scoping of which standards apply to your activity mix and timeline, the process above describes the baseline. Your facts – the specific services, the client segments, the technology stack – change the checklist. If a draft standard is still under consultation and your go-live is months away, reach our licensing desk now at info@oboluslaw.com to map the submission against the emerging rulebook and avoid a mid-process file rebuild.
What do the Level 3 guidelines cover?
Level 3 guidelines interpret how NCAs should apply MiCA and the Level 2 standards in their day-to-day supervision. ESMA's guideline suite covers fit-and-proper assessments, the initial capital calculation, the substance and governance expectations for passporting, the format of the complaints log, the content of the business-continuity plan, and the methodology for assessing a significant liquidity risk in an ART or EMT reserve. Unlike Level 2 standards, guidelines do not have the force of law – they are recommendations issued under ESMA's convergence mandate. But an NCA must either follow the guideline or publish an explanation of why it departs, and in practice most NCAs apply ESMA guidelines as if they were binding rules.
For a CASP applicant, the Level 3 layer shapes the narrative and the evidence bundle. The guideline on fit-and-proper assessments, for example, lists the documentation the NCA expects for each management-body member – CV, criminal-record certificate, prior regulatory history, conflict-of-interest declaration, training on crypto-asset risks. If you submit a CV that omits a prior directorship, the NCA flags it as incomplete, and the clock stops. The guideline on business-continuity planning sets out the minimum recovery-time objectives, the scenario catalogue (cyberattack, key-person loss, exchange outage, sanctions event) and the testing frequency. Your BCP document must address each scenario, or the file is returned for elaboration.
In our experience, the difference between a smooth authorisation and a delayed one often comes down to how thoroughly the applicant has pre-empted the Level 3 expectations. An NCA examiner with 40 files on the desk will not research what your internal processes "probably" cover – if the submission does not explicitly reference the relevant guideline and map each requirement to a policy section or system feature, the examiner issues a request for information, and your timeline extends by the round-trip interval. We build every authorisation file as if the Level 3 guidelines were mandatory, document the compliance evidence in a cross-reference table, and include that table as an appendix to the application. The NCA may not read it in detail, but its presence signals that the file is complete and that your compliance function understands the regime.
How do ART and EMT measures differ from CASP standards?
Asset-referenced tokens and e-money tokens sit in separate Title III and Title IV regimes within MiCA, with their own authorisation paths, capital rules and reserve requirements. The Level 2 measures for ARTs and EMTs address reserve composition and safeguarding, redemption-rights disclosure, the white paper for public offers, the methodology for classifying a token as significant, and the stress-testing of the reserve assets. An issuer applying for ART or EMT authorisation submits an initial reserve plan, a liquidity-management policy, a valuation methodology for the reference assets, and a detailed description of the redemption mechanism – each component cross-mapped to the applicable Level 2 standard.
The key distinction from CASP authorisation is that an ART or EMT issuer operates under a hybrid banking-like regime: it must hold own funds as a going-concern buffer (calculated as a percentage of outstanding tokens or a fixed minimum, whichever is higher), maintain the reserve assets in segregated accounts or custody arrangements meeting specified credit-quality and liquidity criteria, and ensure that redemption requests are honoured within a defined timeframe. The Level 2 measures translate these obligations into formulae, eligible-asset lists and procedural steps. If the reserve includes bank deposits, the standard specifies the credit rating of the deposit-taking institution; if it includes government bonds, it sets concentration limits and haircuts; if it includes other crypto assets, it may prohibit their inclusion altogether depending on the volatility profile.
A common scenario we see is a stablecoin issuer that obtained an e-money institution licence under EMD2 before MiCA and now needs to transition to the MiCA EMT regime. The EMD2 safeguarding rules and the MiCA reserve rules overlap but are not identical – the MiCA Level 2 standard on reserve composition is stricter in some respects (prohibiting certain asset classes that EMD2 permitted) and more flexible in others (allowing a broader set of custody arrangements provided they meet the MiCA safeguarding criteria). The transition filing must demonstrate that the existing reserve structure either complies with the MiCA standard or will be adjusted by the application date, with a detailed migration plan and a legal opinion confirming that the reserve remains protected during the transition window.
What compliance work does each measure trigger?
Each Level 2 standard and Level 3 guideline implies a discrete compliance project. The own-funds RTS requires building a capital model, populating it with live balance-sheet data, running a quarterly calculation and filing the result with the NCA in a specified reporting template. The conflicts-of-interest RTS requires drafting a conflicts policy, maintaining a conflicts register, training staff on identification and escalation, and updating the register every time a new business line or client relationship creates a potential conflict. The safeguarding standard requires mapping client balances to segregated wallets, implementing multi-signature or hardware-security-module controls, arranging insurance or a guarantee from a credit institution, and evidencing daily reconciliation.
The compliance calendar runs in two phases. Phase one is the authorisation build: before you file, you draft every policy, design every control, implement every system feature and document every process that a Level 2 standard or Level 3 guideline prescribes. The NCA does not authorise on promise – it authorises on demonstrated capability. If the safeguarding RTS says client crypto assets must be held in wallets separate from the firm's own holdings, your application must include wallet addresses, custody agreements, insurance certificates and a procedural manual showing how a client deposit flows into the segregated structure. If you do not have those elements in place, you do not apply yet.
Phase two is ongoing compliance: after authorisation, you operate the systems you described, update the policies as standards evolve, file the periodic reports the RTS or ITS prescribes, and notify the NCA of any material change. A Level 2 standard that comes into force six months after your authorisation triggers a gap analysis, a remediation plan, an implementation project and a notification to the NCA confirming compliance by the application date. The NCA may conduct a thematic review or an on-site inspection to verify that your post-authorisation adjustments are effective. This phase is not optional – failing to implement a new Level 2 measure on time is a breach of the authorisation conditions and can result in enforcement action, including suspension of the passport.
Operators we advise routinely ask whether they can phase the compliance work – implement the highest-risk measures first and defer the others. The answer is no if the measure is already in force. A binding Level 2 standard applies from its stated date, and partial compliance is non-compliance. You may, however, prioritise draft measures that are likely to be adopted soon, implementing them ahead of finalisation so that when the standard is published your systems are already aligned. This approach reduces the post-adoption scramble and demonstrates supervisory maturity to the NCA, which can be an advantage if the regulator is deciding between granting full authorisation and imposing additional conditions or a probationary period.
How do timelines vary across member states?
MiCA is a regulation, not a directive, so in principle it applies uniformly across the Union without requiring national transposition. In practice, NCAs retain discretion in two areas: the internal resourcing and prioritisation of applications, and the interpretation of ambiguous or open-textured provisions where a Level 2 standard or Level 3 guideline has not yet been finalised. This creates timeline variation. An application filed in Lithuania, historically a fast-track hub for VASP registrations, may be processed in a matter of weeks once the file is complete. An application in a larger member state with a backlog of legacy payment-institution and e-money-institution files may take several months even if the submission is flawless.
The clock starts when the NCA acknowledges that your application is complete – not when you first submit. The completeness assessment itself can take weeks if the NCA identifies missing documents, unclear policy language or gaps in the evidence bundle. One common delay is the fit-and-proper vetting of management-body members: if a director holds multiple other appointments or has prior regulatory history in a non-EU jurisdiction, the NCA may request additional background checks, and the clock stops while those checks are obtained. Another delay point is the assessment of IT and cybersecurity controls – if your application describes a cloud-based infrastructure and the NCA wants to see the third-party audit report or the penetration-test results, the file is put on hold until you supply them.
For a business sitting between multiple member states – entity in one, operations in another, clients in a third – the question is whether to apply in the home state and passport out, or to seek authorisation directly in the state where most of your activity sits. The answer turns on NCA capacity, the local interpretation of any open issues in the Level 2 measures, and the post-authorisation supervisory intensity. Some NCAs are known for pragmatic, business-friendly supervision; others apply a strict-liability approach to technical breaches. We map the supervision culture as part of the jurisdictional recommendation, drawing on cases we have seen where an NCA's interpretation of a Level 3 guideline differed materially from the approach taken by a neighbouring authority.
If a prior application stalled or an initial consultation with an NCA surfaced an unexpected interpretation, the process above describes the standard path. Your facts – the entity history, the prior filings, the NCA's feedback – change the strategy. A second read can surface the structural issue and the route back. To map a revised submission or a parallel application in an alternative member state, write to info@oboluslaw.com.
What happens if a measure changes after authorisation?
An authorised CASP must adapt its systems and policies whenever a new Level 2 standard is adopted or an existing one is amended. ESMA and the Commission typically build a transitional period into the legislative text – a standard published in March may apply from September, giving six months for implementation. During that window, the CASP conducts a gap analysis comparing the new standard to its current processes, identifies the changes required (policy rewrites, system enhancements, staff training, vendor adjustments), implements those changes, and notifies the NCA that it is ready for the new regime. If the changes are material – for example, a new capital formula that significantly increases the own-funds requirement – the CASP may need to raise additional capital or restructure its balance sheet before the application date.
The NCA expects to see a documented change-management process. A file note saying "we will comply" is not sufficient. The evidence bundle includes the gap-analysis report, the project plan with milestones and owners, the updated policies, the system-configuration screenshots or vendor certificates showing that the technical changes are live, and the board minutes approving the changes and allocating the budget. If the standard introduces a new reporting obligation, the first report is filed on the prescribed schedule, and the NCA checks that the format and content match the template in the ITS. A missed deadline or an incorrect report format triggers a supervisory inquiry and, if repeated, potential enforcement action.
One area of uncertainty is how retrospective amendments to Level 2 standards affect authorisations granted under the earlier version. The general principle under EU law is that new rules apply prospectively unless the text states otherwise, but if a standard is amended to close a regulatory gap or address a systemic risk, the Commission may impose a short implementation period even for existing CASPs. This happened in adjacent regimes – for instance, under PSD2, an RTS on strong customer authentication was amended after a fraud spike, and payment institutions had 90 days to implement the enhanced authentication flows. The lesson for MiCA CASPs is to maintain a compliance-monitoring function that tracks ESMA consultations, Commission work programmes and industry alerts, so that you have advance notice of likely amendments and can budget the implementation work before the clock starts.
How do Level 2 measures interact with national gold-plating?
Because MiCA is a regulation, member states may not add requirements that go beyond its provisions – this is the prohibition on gold-plating. In practice, however, NCAs retain margin in three areas: the interpretation of principles-based language where the Level 2 measure does not provide a bright-line test; the supervisory intensity and examination frequency; and the interaction between MiCA and other national regimes (AML, tax, consumer protection, payment services where not fully harmonised). A CASP operating across multiple member states may find that one NCA treats a particular Level 3 guideline as a strict checklist while another applies it flexibly, or that an NCA layers an additional local AML reporting requirement on top of the Travel Rule baseline.
The passport mechanism is supposed to eliminate these frictions – an authorised CASP notifies the host NCA of its intention to provide services there, the host NCA acknowledges the notification, and the CASP may commence activity without a separate local authorisation. But the host NCA retains conduct-of-business and market-integrity supervision, and if its interpretation of a Level 3 guideline differs from the home NCA's, the CASP faces dual compliance. This is most visible in marketing and client-communication standards: one NCA may accept English-language disclosures for professional clients; another may require local-language translations even for wholesale activity. The Level 3 guideline on marketing communications sets out general principles – clear, fair, not misleading – but does not prescribe language, font size or platform-specific rules, leaving room for national variation.
To manage this, the CASP's compliance function must maintain a matrix of local expectations across each member state where it operates, updating the matrix as NCAs publish Q&A, supervisory briefings or enforcement decisions that clarify their interpretation. When we structure a multi-state roll-out, we front-load the host-NCA engagement – a pre-notification call or written inquiry asking the NCA to confirm its position on any ambiguous guideline points – so that the CASP knows before launch whether local adjustments are needed. This process is not legally required, but it converts supervisory uncertainty into documented guidance, which protects the CASP if the NCA later challenges a practice that it had previously cleared.
When should you engage counsel on Level 2 compliance?
Engage at three points: before you finalise the business model, during the authorisation build, and when a new Level 2 standard is published. At the model stage, counsel maps the proposed activities to the MiCA service definitions, identifies which Level 2 measures will apply, and flags any activity that falls outside the MiCA perimeter (for instance, certain DeFi protocols, pure software tools with no custody or execution function, or activity directed solely at non-EU clients). This mapping determines whether you need CASP authorisation, another financial-services licence, or no EU licence at all – getting it wrong at the design stage is expensive, because restructuring a live business to fit a regulatory category is harder than building the category in from the start.
During the authorisation phase, counsel drafts or reviews the policies required by the Level 2 standards, prepares the evidence bundle, liaises with the NCA on procedural questions, and coordinates with local counsel in the home member state if the applicant's primary legal team sits outside the EU. The authorisation file is a legal and technical document – it makes representations about governance, systems, capital and risk management that bind the applicant once authorisation is granted. An incomplete or inaccurate representation can lead to the NCA revoking or suspending the authorisation if the error is discovered post-grant, or to enforcement action if the CASP's operations diverge from the file. Counsel's role is to ensure that what the file says matches what the business does and that both align with the applicable standards.
When a new Level 2 measure is adopted, counsel conducts the gap analysis, advises on the implementation priority, drafts any policy amendments, and prepares the NCA notification. This is not a once-off event – the Level 2 architecture will evolve as MiCA matures, ESMA refines its technical standards in response to market developments or supervisory findings, and the Commission issues delegated acts addressing issues that were deferred in the initial package. A CASP that treats the authorisation as the finish line will find itself out of compliance within months. The steady state is a rolling compliance programme, with counsel engaged on a retainer or project basis to handle each new measure as it emerges.
How OBOLUS advises on MiCA Level 2 implementation
OBOLUS maps the Level 2 and Level 3 architecture for crypto-asset businesses applying for or holding CASP, ART or EMT authorisation under MiCA. We work from the published Official Journal texts and ESMA's final guidelines, cross-reference them to your business model and technology stack, and produce a compliance roadmap with policy templates, evidence checklists and NCA-notification drafts. The service sits at the intersection of regulatory advisory and transactional structuring – it is not only about interpreting the standards but about embedding them into governance documents, vendor contracts, system specifications and internal controls in a way that the NCA can verify at the desk review and on-site inspection.
For clients in the authorisation phase, we build the file around the Level 2 measures that are final at the time of submission and flag the draft measures that will likely bind before or shortly after authorisation is granted. This approach avoids the mid-process file rebuild that occurs when an applicant ignores a forthcoming standard and the NCA requires a supplementary submission once the standard is adopted. For clients already authorised, we conduct a gap analysis each time a new Level 2 standard is published, quantify the implementation work, and manage the project through to NCA notification. The analysis draws on our ongoing tracking of MiCA measures, following the status of every RTS, ITS and guideline in ESMA's work programme, the consultation and adoption dates, and the application timeline.
We also advise on the cross-border and cross-regime interaction – how MiCA sits with the AML package, the Market Abuse Regulation, the Data Protection Regulation, the e-Commerce Directive, the Network and Information Security Directive, and any national payment-services or banking rules that still apply. A CASP rarely operates under MiCA alone; it sits at the centre of a regulatory web, and a change in one thread affects the others. When we scope an engagement, we map the full perimeter – the licences you hold, the ones you will need, the reporting obligations across all regimes, and the supervisory authorities you answer to – so that the MiCA compliance programme integrates with the rest of your legal and regulatory architecture rather than creating a siloed workstream.
Digital assets are the whole of our practice. We advise exchanges, custodians, token issuers and funds across more than seventy licensing jurisdictions and on disputes and asset recovery across more than twenty-five forums. For MiCA specifically, we track every Level 2 adoption, every ESMA guideline update and every NCA supervisory statement as they emerge. To pressure-test your Level 2 readiness before the next measure takes effect, write to us at info@oboluslaw.com.
Related practices
- Licensing & Registration for Digital-Asset Businesses – the full licensing service across VASP, payment-institution, custody and fund-management categories in Europe, the Middle East and Asia-Pacific.
- Stablecoin Regimes Compared: United States, European Union and Hong Kong – a comparative analysis of the reserve, redemption and disclosure obligations for stablecoin issuers across three major jurisdictions.
- EMI Licence for Crypto Firms: The Disputes Angle – how the e-money institution framework interacts with enforcement, insolvency and on-chain asset recovery.
FAQ
How long does a crypto licence take to obtain?
The timeline for CASP authorisation under MiCA varies by member state and the completeness of the application. In jurisdictions with streamlined NCA processes and a complete file, authorisation may be granted within a few months. In others, where the NCA has a backlog or where the applicant's business model raises complex questions, the process can extend to six months or longer. The clock starts when the NCA confirms the application is complete, not when it is first submitted. Delays typically arise from missing documentation, unclear policies or the fit-and-proper vetting of directors with multi-jurisdictional backgrounds.
Which jurisdiction suits my crypto business?
The choice of home member state for MiCA authorisation turns on NCA capacity, supervisory culture, the availability of banking and tax infrastructure, and the post-authorisation reporting intensity. Some NCAs are known for pragmatic, business-friendly supervision and faster processing; others apply strict-liability interpretations of technical standards. The decision also depends on where your clients, operations and technology sit – if most of your user base is in one region, applying in a nearby member state may simplify the ongoing compliance and reduce the risk of host-NCA friction when you passport.
Do I need a separate custody licence?
Under MiCA, custody of crypto assets on behalf of third parties is a regulated CASP service and requires authorisation. If you are applying for a multi-service CASP licence that includes custody, you address the safeguarding and own-funds requirements for that activity in the main authorisation file. You do not need a separate custody-only licence unless you are structuring the custody function as a distinct legal entity. In some cases, a business chooses to obtain a pure custody licence first, then expand into execution or advisory services later – that approach works if the business model starts with safekeeping and the additional services come as the client base grows.
By Aisha Tan, Licensing & Jurisdictions Analyst – advising on CASP, ART and EMT authorisations under MiCA and on the interaction between the Level 2 measures and national regimes across EU member states.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.