← Back to blog

MiCA compliance guide for UK crypto firms: 2026 edition

August 8, 2026
MiCA compliance guide for UK crypto firms: 2026 edition

A UK crypto-asset service provider or token issuer that actively targets EU clients, offers tokens to the public in the EU, or seeks admission to trading on an EU platform must treat Regulation (EU) 2023/1114 — the Markets in Crypto-Assets Regulation (MiCA) — as a binding compliance obligation, not a foreign regulatory curiosity. Brexit removed the UK from the EU's passporting framework, but it did not remove UK firms from MiCA's reach when their activities cross into EU territory.

Three priorities demand attention immediately:

  • Scope decision: Determine whether your token offers, trading services, or custody activities constitute an offer to the public in the EU or admission to trading on an EU platform. This single test determines whether MiCA applies at all.
  • White paper and notification readiness: If MiCA applies, a crypto-asset white paper is almost certainly required. Assess whether your current disclosures meet MiCA's mandatory content rules and iXBRL tagging obligations.
  • Governance and capital gap analysis: Map your existing governance structure, AML/CFT policies, and capital position against MiCA's prudential and operational requirements before any authorisation filing.

Three actions to take today:

  • Run a formal scope test against MiCA's definitions of crypto-asset, asset-referenced token (ART), and e-money token (EMT).
  • Commission a gap assessment comparing your current policy stack against MiCA Title III (ARTs), Title IV (EMTs), and Title V (CASPs).
  • Appoint an accountable compliance officer with a defined MiCA mandate, even before authorisation is sought.

The FCA, Bank of England, HM Treasury, ESMA, and EBA are all relevant to UK firms navigating this framework. Cryptoverselawyers has supported clients through MiCA authorisation filings and cross-border readiness assessments across multiple EU jurisdictions.

Pro Tip: Do not wait for the FCA to issue definitive UK equivalence guidance before acting. MiCA's cross-border reach is determined by where your clients are located and where your tokens are offered, not where your firm is incorporated.*


What does MiCA actually cover, and which obligations apply to you?

MiCA divides crypto-assets into three regulatory categories, each carrying a distinct obligation set.

Other crypto-assets (utility tokens, payment tokens, and assets that do not qualify as ARTs or EMTs) are the broadest category. Issuers must publish a white paper notified to the relevant national competent authority (NCA) at least 20 working days before any public offer. No prior approval is required for this category, but civil liability attaches to the white paper under Article 14 of MiCA.

Asset-referenced tokens (ARTs) reference multiple currencies, commodities, or crypto-assets to maintain a stable value. ART issuers require prior authorisation from their home-state NCA, must maintain a reserve of assets, and are subject to ongoing prudential and redemption obligations. Significant ARTs attract additional ESMA and EBA oversight.

E-money tokens (EMTs) reference a single fiat currency and are treated as electronic money under MiCA. Issuers must hold either an electronic money institution (EMI) or credit institution authorisation. EMT white papers require notification to the NCA at least 40 working days before issuance.

For CASPs, Title V of MiCA sets out nine licensable service categories: custody and administration of crypto-assets; operation of a trading platform; exchange of crypto-assets for fiat or other crypto-assets; execution of orders; placing of crypto-assets; reception and transmission of orders; portfolio management; advice; and transfer services. Each service category carries specific conduct, disclosure, and prudential obligations. Firms providing custody services must also comply with MiCA's client asset segregation rules, which mirror but are not identical to MiFID II's safeguarding requirements.

Compliance checklist and tablet on conference table


Who must comply, and does MiCA reach your UK firm?

The threshold question is whether your activity constitutes an offer to the public in the EU or admission to trading on an EU trading platform. Both tests are location-of-client tests, not location-of-firm tests.

A UK firm offering tokens via a website accessible to EU retail clients, without geo-blocking or meaningful access controls, is likely making a public offer in the EU. Similarly, a UK exchange that lists tokens on an EU trading venue, or that routes EU client orders to an EU platform, may be providing CASP services into the EU regardless of where its servers sit.

Practical scope-decision questions for issuers:

  • Is the token marketed in any EU member state, whether through social media, press releases, or broker networks?
  • Does your white paper or marketing material name EU investors as a target audience?
  • Are EU retail clients able to purchase the token directly from your platform without restriction?

For CASPs, NCAs assess whether the firm is "habitually" providing services into their jurisdiction. Indicators include EU-language marketing, EU-domiciled client onboarding, and EU payment rails. A single EU client is unlikely to trigger authorisation; a structured EU sales effort almost certainly will.

UK firms that establish an EU subsidiary or branch to access EU markets must obtain full MiCA authorisation for that entity. Passporting under MiCA allows an authorised CASP to notify its home-state NCA and then passport services into other EU member states, but this right belongs to the EU-authorised entity, not the UK parent.


What does authorisation require, and how long does it take?

MiCA CASP authorisation is a structured dossier process. NCAs conduct a completeness check before the formal assessment clock starts, so the quality of the initial submission directly affects timeline.

A complete authorisation file typically includes:

  1. Legal and corporate documentation: constitutional documents, group structure chart, shareholder register, and details of qualifying holdings.
  2. Business plan: description of services, target markets, revenue model, and three-year financial projections.
  3. Governance framework: board composition, fit-and-proper assessments, organisational chart, and terms of reference for risk and audit committees.
  4. Capital and prudential plan: evidence of minimum own funds (€50,000 to €150,000 depending on services), an ICAAP-equivalent prudential model, and liquidity stress scenarios.
  5. AML/CFT policies: risk-based approach document, customer due diligence procedures, transaction monitoring framework, and Travel Rule compliance plan.
  6. Custody and IT controls: custody model description, segregation of client assets policy, business continuity plan, and penetration testing results.
  7. Conflicts of interest policy, whistleblowing procedure, and complaints handling policy.

For ART issuers, the reserve asset plan must align with EBA's regulatory technical standards on liquidity requirements, which specify eligible asset classes, concentration limits, and redemption mechanics. Significant ART designations trigger additional ESMA and EBA notifications and a longer assessment period.

The assessment period for CASP authorisation is 25 working days after the completeness check. NCAs may extend this by a further 25 working days for complex applications. ART authorisation involves a 60-working-day completeness review followed by a separate assessment window. The European Commission's catalogue of delegated and implementing acts specifies the Level-2 templates and technical standards that govern each stage.

Pro Tip: Structure your authorisation submission so that each policy document cross-references the specific MiCA article it satisfies. NCAs conducting completeness checks work through a checklist; a submission that maps itself to that checklist reduces queries and avoids clock-stopping information requests.


What operational policies and governance does MiCA require of CASPs?

MiCA's operational obligations translate into a minimum policy stack that compliance teams must draft, implement, and evidence before filing for authorisation. Generic templates drawn from MiFID II or FCA frameworks will not satisfy NCAs conducting thematic reviews; ESMA has identified bespoke, model-specific policies as a key differentiator in authorisation quality.

The minimum policy set covers:

  • Conflicts of interest: identification, management, and disclosure procedures specific to crypto-asset markets (e.g., proprietary trading alongside client order execution).
  • AML/CFT and KYT: risk-based customer due diligence, ongoing transaction monitoring, and a Know-Your-Transaction (KYT) framework aligned with FATF Recommendation 16 (the Travel Rule).
  • Whistleblowing: an internal reporting channel with documented investigation procedures and non-retaliation protections.
  • Incident response and business continuity: cyber incident classification, escalation paths, and recovery time objectives for critical systems.
  • Outsourcing and third-party oversight: due diligence on material service providers, contractual protections, and exit plans.
  • Record-keeping: retention periods, data formats, and access controls for order books, client records, and transaction logs.

Board accountability is non-negotiable. MiCA requires that at least two individuals effectively direct the business, both of whom must satisfy fit-and-proper requirements. A nominated compliance officer with a direct reporting line to the board, and documented evidence of independent oversight (board minutes, risk committee papers, internal audit reports), is what NCAs look for during on-site reviews.

For UK firms mapping existing FCA-compliant policies to MiCA, the gap is usually in custody segregation specificity, KYT integration, and the ART/EMT reserve asset governance framework. Policies that reference "crypto-assets" generically without distinguishing between token types will require rewriting.

Pro Tip: Build your MiCA policy index as a living document that maps each policy to the MiCA article it satisfies, the owner responsible, and the last review date. This single artefact becomes your primary evidence of governance readiness during NCA inspections.


What must a MiCA white paper contain, and how do you submit it?

White paper requirements differ materially by token type, and the iXBRL tagging obligation introduced on 23 December 2025 adds a technical layer that many firms underestimate.

For all token types, the white paper must include: a description of the issuer and its key personnel; the token's features, rights, and obligations; the underlying technology; the risks to the holder; and the use of proceeds. ART white papers must additionally describe the reserve asset composition, redemption rights, and stabilisation mechanisms. EMT white papers must confirm the issuer's EMI or credit institution status.

Since 23 December 2025, all white papers submitted to NCAs must be tagged in inline XBRL (iXBRL) using ESMA's MiCA taxonomy. The ESMA MiCA taxonomy reporting manual v1.0 sets out the tagging rules, validation requirements, and entry points for each token category. Firms should engage an XBRL-capable vendor or build internal tagging capability before drafting the white paper, not after, because retrofitting taxonomy tags to a completed document is significantly more time-consuming.

Common reasons NCAs return or refuse white paper submissions:

  • Missing mandatory disclosure items from MiCA Annex I, II, or III.
  • iXBRL tags that fail ESMA's validation rules or use incorrect taxonomy entry points.
  • Inconsistencies between the white paper and the authorisation dossier (e.g., different descriptions of the reserve asset mechanism).
  • Marketing materials that contradict or expand on white paper disclosures.

For practical drafting guidance, the Cryptoverselawyers framework for regulating crypto-assets in the EU sets out the white paper content requirements and notification workflow in detail.


How do technical data standards affect your internal systems?

ESMA's MiCA implementation work includes a standardised JSON schema for orders and trades that CASPs operating trading platforms must adopt. This schema defines the required fields, data types, and formats for order-book records, trade confirmations, and transaction logs that NCAs can request during supervisory reviews.

Lit data center aisle supporting crypto compliance

Firms that align their internal logging systems to the ESMA JSON schema from the outset avoid the costly data migration that typically follows a supervisory information request. The schema covers order identifiers, timestamps (to microsecond precision), instrument identifiers, price and quantity fields, and client reference data. Record-keeping retention periods under MiCA are five years for most transaction records, with machine-readable formats required for records subject to supervisory access.

Market abuse monitoring is a parallel obligation. CASPs must maintain systems capable of detecting and reporting suspicious transactions and orders. These systems should generate interoperable feeds for suspicious transaction reports (STRs) submitted to NCAs. Integrating the JSON order schema into your transaction monitoring platform from day one means your audit trail is already in the format regulators expect, reducing the friction of any future investigation.

For firms building or procuring crypto risk management infrastructure, aligning monitoring workflows with established risk management frameworks supports both prudential modelling and the technical compliance evidence NCAs require.


What transitional measures apply, and what are the critical deadlines?

Article 143 of MiCA provides transitional relief for firms that were operating under a national crypto-asset regime before MiCA's full application date. These firms may continue operating under their existing national authorisation for a limited period while pursuing full MiCA authorisation.

The key dates and obligations for firms relying on transitional measures:

  1. Identify your national regime status: Confirm whether your EU entity held a valid national crypto-asset licence or registration before MiCA's application date. Firms without a pre-existing national authorisation cannot rely on Article 143 grandfathering.
  2. Document your transitional basis: Retain evidence of your national authorisation, the services covered, and the date from which you have been operating. NCAs will require this documentation when assessing your transition to full MiCA authorisation.
  3. Submit your full authorisation file before the grandfathering window closes: The transitional period for most member states ends by 1 July 2026. Firms that miss this deadline lose the right to continue operating under the national regime and must cease regulated activities until MiCA authorisation is granted.
  4. Monitor the ESMA interim register: ESMA maintains a register of authorised CASPs and notified white papers. Firms in the transitional period appear on this register with a transitional status flag. Mid-2026 is the expected point at which ESMA integrates transitional and full authorisation data into a single register view.
  5. Prepare for a seamless handover: NCAs expect firms transitioning from national regimes to demonstrate that their MiCA-compliant policies, governance structures, and technical systems are operational before the authorisation decision, not after.

For a detailed breakdown of the transitional phase mechanics, the Cryptoverselawyers guide to MiCA's transitional phase covers grandfathering options and simplified procedures by member state.


How does MiCA interact with FCA requirements for UK firms?

The FCA's crypto-asset regulatory perimeter is defined by the Financial Services and Markets Act 2000 (FSMA) and the UK's own cryptoasset registration regime under the Money Laundering Regulations 2017. MiCA and the FCA regime are parallel frameworks: compliance with one does not satisfy the other.

A UK firm serving EU clients faces dual-compliance obligations. Its FCA registration or authorisation governs its UK-facing activities; MiCA (through an EU-authorised entity or direct cross-border obligations) governs its EU-facing activities. The practical risk is policy divergence: AML/CFT procedures drafted for FCA purposes may not satisfy MiCA's specific KYT and Travel Rule requirements, and vice versa.

HM Treasury and the Bank of England become relevant when a UK firm issues an ART that references sterling or a basket including sterling. The Bank of England has supervisory interest in payment system stability risks arising from widely-used stablecoins, and HM Treasury's proposed stablecoin regime may impose additional requirements on sterling-referenced tokens regardless of where they are issued. Firms in this position should monitor HM Treasury's consultation process alongside MiCA developments.

Cross-border enforcement cooperation between EU NCAs and the FCA operates through memoranda of understanding and IOSCO frameworks. When an NCA investigates a potential MiCA breach by a UK firm, it may request information from the FCA under these cooperation arrangements. UK firms should therefore maintain records that satisfy both FCA and MiCA standards, and ensure client contracts clearly specify the governing law and regulatory regime applicable to each service.

For firms assessing their FCA authorisation position alongside MiCA obligations, the UK crypto licensing decision tree provides a structured framework for mapping activities to the correct regulatory pathway.


A practical 6–12 month implementation roadmap for UK CASPs and issuers

The sequence below reflects the dependencies between workstreams. Attempting authorisation before governance and technical integration are complete is the most common cause of NCA information requests that stop the assessment clock.

  1. Months 1–2: Scope and gap analysis. Run the cross-border scope test. Commission a formal gap assessment against MiCA Titles III, IV, and V. Appoint a compliance officer with a defined MiCA mandate.
  2. Months 2–3: Governance uplift. Revise board terms of reference, establish a risk committee with crypto-specific terms, and conduct fit-and-proper assessments for all senior managers.
  3. Months 3–5: Policy drafting. Draft or revise the full policy stack (AML/CFT, conflicts of interest, custody, outsourcing, whistleblowing, incident response). Map each policy to its MiCA article.
  4. Months 4–6: White paper production and iXBRL tagging. Draft the white paper using ESMA's Annex I, II, or III as the content template. Engage an XBRL vendor and complete taxonomy mapping using the ESMA taxonomy reporting manual. Validate the tagged document before submission.
  5. Months 5–7: Technical integration. Align internal order and trade logging to ESMA's JSON schema. Integrate KYT and transaction monitoring feeds. Test market abuse detection workflows.
  6. Months 6–9: Capital and prudential modelling. Prepare own-funds calculations, ICAAP-equivalent prudential model, and (for ART issuers) reserve asset plan aligned with EBA liquidity technical standards.
  7. Months 8–10: Pre-submission NCA engagement. Request a pre-application meeting with the relevant NCA. Present the governance framework and policy index. Address any preliminary feedback before filing.
  8. Months 10–12: Authorisation filing and assessment. Submit the complete dossier. Respond to NCA queries within the prescribed windows. Maintain a live issues log tracking each query and its resolution.

Responsibilities by role:

DeliverablePrimary ownerSupporting owner
Scope and gap analysisCompliance officerGeneral counsel
Governance frameworkBoard/CEOCompliance officer
Policy stackCompliance officerLegal counsel
White paper and iXBRLLegal counselXBRL vendor
JSON/technical integrationCTOCompliance officer
Prudential modellingCFOCompliance officer
Authorisation filingGeneral counselCompliance officer

What enforcement powers do NCAs have, and what triggers scrutiny?

MiCA grants NCAs a broad supervisory toolkit. Powers include the right to require information, conduct on-site inspections, issue public warnings, suspend or withdraw authorisation, and impose financial penalties. For significant ARTs and EMTs, ESMA and EBA hold direct supervisory powers alongside the home-state NCA.

NCAs also have publication powers: a public censure naming the firm and describing the breach is a reputational sanction that operates independently of any financial penalty.

Common supervisory red flags identified in thematic reviews include:

  • Generic policies: AML/CFT or conflicts-of-interest documents that are not specific to the firm's token types, client base, or custody model.
  • Weak custody controls: absence of documented segregation procedures, no third-party custody audit, or client asset records that cannot be reconciled in real time.
  • Inadequate record-keeping: order and trade logs that do not meet the JSON schema field requirements or that cannot be produced in machine-readable format within the NCA's requested timeframe.
  • Misleading white papers: disclosures that overstate the stability of a reserve asset, omit material risks, or conflict with marketing materials published after the white paper notification date.

Practical mitigation steps: conduct annual policy testing against MiCA's requirements, maintain a supervisory engagement log, and prepare a rapid remediation plan template that can be activated within 48 hours of an NCA information request.


Why bespoke policy design consistently outperforms template packages

The firms that clear MiCA authorisation with the fewest supervisory queries share one characteristic: their submissions are built around their actual business model, not around a generic regulatory template. ESMA's own convergence observations confirm that NCAs are increasingly adept at identifying documents that have been lightly adapted from a standard precedent rather than drafted from the ground up.

The failure mode is predictable. A template AML policy that references "virtual assets" without distinguishing between the firm's specific token types, custody arrangements, and client risk profiles will prompt an NCA to issue a detailed information request. That request stops the assessment clock. Each round of back-and-forth adds weeks to the timeline and increases the risk that the NCA forms a negative preliminary view of the firm's compliance culture.

Bespoke documents must demonstrate three things: that the firm understands its own risk profile, that its controls are calibrated to that profile, and that the board has genuinely reviewed and approved the framework rather than rubber-stamping a bought-in template. The governance evidence, board minutes, risk committee papers, and compliance officer reports, is what separates a credible submission from a paper exercise.

Early alignment to ESMA's technical standards, particularly the JSON schema and iXBRL taxonomy, signals to NCAs that the firm's operational infrastructure is genuinely MiCA-ready. Firms that treat technical integration as a post-authorisation task routinely face conditions attached to their authorisation or, in some cases, a refusal pending technical remediation.


How Cryptoverselawyers supports your MiCA readiness

Cryptoverselawyers offers end-to-end MiCA advisory for UK CASPs and token issuers seeking EU market access. The firm's services cover the full authorisation lifecycle: scope and gap analysis, governance framework design, bespoke AML/CFT policy drafting, white paper production with iXBRL taxonomy mapping, prudential modelling for ART reserve assets, and full authorisation dossier preparation and NCA liaison.

Cryptoverselawyers

For firms at the pre-application stage, Cryptoverselawyers provides a fixed-fee MiCA readiness review that delivers a gap report, a prioritised remediation plan, and a draft policy index within four weeks. For firms already in the authorisation process, the firm offers targeted support on specific workstreams, including iXBRL tagging, JSON schema integration, and NCA query responses.

Cryptoverselawyers's cross-regulatory experience spans VARA, SCA, DFSA, FSRA, and CBUAE in the UAE, alongside MiCA, FCA, MAS, and FINTRAC frameworks globally. That breadth means the firm can structure multi-entity operations that satisfy both UK FCA requirements and MiCA obligations without creating conflicting compliance obligations. To discuss your MiCA position and engage the firm's digital asset advisory services, contact Cryptoverselawyers directly for an initial scoping call.


Sources

The following primary sources should be consulted before preparing any MiCA authorisation file or white paper submission:

Note: Always consult the ESMA taxonomy reporting manual before beginning iXBRL white paper preparation. The validation rules are updated periodically, and a white paper tagged against an outdated taxonomy version will fail the NCA's technical completeness check.


This article provides general information about MiCA regulatory requirements and does not constitute legal advice. Firms should confirm current obligations with a qualified legal adviser and consult the relevant national competent authority for jurisdiction-specific guidance.

This article is general information, not a substitute for advice from a qualified financial advisor. Consult a qualified financial professional about your own circumstances before acting on anything here.