EST · MMXXVI
Home/Insights/Regulatory/Non-Financial Disclosure for Crypto-Asset Firms in the EU
Licensing & Registration

Non-Financial Disclosure for Crypto-Asset Firms in the EU

Non-Financial Disclosure for Crypto-Asset Firms in the EU. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagem

A crypto-asset service provider preparing its MiCA authorisation application discovers that the operating licence is only the first layer. Alongside it sits a parallel obligation to publish non-financial disclosures – sustainability reports, cyber-resilience statements and governance frameworks that must be reviewed, attested and made public on a rolling schedule. For many firms, the disclosure burden is heavier than the licence itself, and it arrives without warning in the final stages of the authorisation process.

Non-financial disclosure under MiCA and adjacent EU regimes requires crypto-asset firms to report on environmental impact, governance systems, operational resilience and consumer safeguards in a way that mirrors the obligations imposed on traditional financial institutions. The publication timetable is fixed, the content expectations are detailed and the penalties for late or incomplete reporting mirror those for substantive regulatory breaches. This page sets out what must be disclosed, when it must appear and how it interacts with the white-paper content already required at authorisation.

The analysis that follows covers the scope of the obligation, the timetable and format for publication, the substantive content expected in each disclosure category, the interaction with white-paper and prospectus rules and the position of firms that operate across multiple member states. Two anonymized matters illustrate the practical risk when disclosure is left to the last quarter before go-live.

Who must disclose: the scope of the obligation

Every entity authorised as a crypto-asset service provider under MiCA is subject to non-financial disclosure requirements, regardless of the specific services it provides or the volume of activity it handles. The obligation applies equally to exchanges, custodians, advisory firms and operators of trading platforms. It begins at the point of authorisation and runs for as long as the licence remains in force, with updated reports required annually and certain statements refreshed on a shorter cycle where material changes occur.

The disclosure regime draws on the Corporate Sustainability Reporting Directive and the Digital Operational Resilience Act, both of which impose similar obligations on traditional financial institutions across the EU. For crypto firms, the result is that sustainability reporting, governance disclosures and operational-resilience statements must be prepared to the same standard as those filed by banks and investment firms, even where the crypto business has no physical premises, no employee headcount beyond a small operational team and no legacy IT estate. The regulator's view is that the scale of the obligation should match the scale of the risk the firm presents to consumers and to market integrity, not the size of its balance sheet.

Firms that hold multiple licences across member states face a choice: prepare a consolidated group-level report that covers all entities and all jurisdictions, or file separate reports with each national competent authority. In our cross-border practice, we see most operators choose the consolidated route, but that requires the parent entity to hold the MiCA authorisation at group level and for each subsidiary to be registered as a tied agent or branch. Where the structure is a collection of stand-alone entities, each with its own licence, each files its own disclosure suite. The compliance burden is not shared.

What must be published: the four pillars of non-financial disclosure

The content falls into four categories: sustainability and climate impact, governance and remuneration, operational resilience and cyber security, and consumer protection and complaints handling. Each category corresponds to a specific disclosure template published by ESMA, and each must be filed in a structured data format that allows aggregation and comparison across firms. Plain-language narrative alone is not sufficient; the regulator expects quantitative data where it is available, and qualitative explanation where measurement is not yet feasible.

Sustainability and climate impact requires the firm to quantify the energy consumption of its infrastructure, report the carbon footprint of its operations and disclose any steps taken to mitigate environmental harm. For firms that operate proof-of-work mining facilities or that custody assets on energy-intensive blockchains, the disclosure will include estimates of the energy consumed per transaction and, where the firm has committed to carbon neutrality or to renewable-energy sourcing, the evidence that supports the claim. Firms that operate only on proof-of-stake networks or that provide advisory services without direct custody face a lighter burden, but they must still disclose their governance approach to environmental risk and explain why their impact is low.

Governance and remuneration covers the structure of the board, the independence of non-executive directors, the existence and terms of reference of audit and risk committees, and the remuneration policy for senior management. The expectation is that a crypto-asset service provider will have a governance structure comparable to that of a MiFID investment firm, with separation between executive and supervisory functions and documented escalation paths for conflicts of interest, related-party transactions and breaches of internal controls. Firms must also disclose the total remuneration of the three highest-paid individuals, broken down into fixed salary, variable pay and equity or token-based incentives, and explain how the incentive structure aligns with the firm's risk appetite and with consumer protection.

Operational resilience and cyber security is the most technically detailed of the four pillars. Firms must report on incident response times, system availability measured over the reporting period, the frequency and severity of cyber incidents, the results of penetration testing and the existence of third-party certifications such as ISO 27001 or SOC 2 Type II. For firms that rely on third-party infrastructure – cloud hosting, wallet-service APIs, blockchain node providers – the disclosure must identify each critical dependency, the jurisdiction in which the provider is based and the contractual provisions that govern service continuity and data sovereignty. The regulator expects to see evidence that the firm has tested its incident-response playbook in a live simulation and that it can restore service within a defined recovery-time objective.

Consumer protection and complaints handling requires the firm to publish the number of complaints received in the reporting period, the time taken to resolve them, the proportion escalated to the national ombudsman or alternative-dispute-resolution scheme and a summary of the root causes identified. Firms must also disclose the content of their consumer-protection policy, the process for handling vulnerable customers and the arrangements for compensating consumers where the firm has caused loss through error or misconduct. This disclosure overlaps with the white-paper obligation to explain custody arrangements and consumer recourse, but it goes further: the regulator expects annual evidence that the systems described in the white paper are operating as promised.

When disclosure is due: the timetable and publication format

The first disclosure suite must be published no later than six months after the date of authorisation, regardless of whether the firm has commenced live operations. The regulator's position is that the obligation to disclose governance, resilience and consumer-protection systems exists from the moment the licence is granted, not from the moment the first client transacts. For a firm that receives authorisation but then delays its market launch, the disclosure timetable runs independently of the business timetable, and a report covering the pre-launch period must still be filed on schedule.

Annual reports are due within four months of the end of the firm's financial year. The sustainability and governance sections must be signed by the board and attested by an external auditor or by a qualified environmental consultant where the firm has made specific climate commitments. The operational-resilience and consumer-protection sections may be signed by senior management, but they must be reviewed by the internal audit function or by an external advisor with relevant technical credentials. Where a firm operates across multiple member states, the consolidated report is filed with the competent authority of the home member state and shared automatically with the other authorities through the ESMA central repository.

Interim updates are required where a material change occurs: a significant cyber incident, a change in control, the addition of a new service category under the firm's licence or a breach of the recovery-time objective for critical systems. The interim update must be filed within 30 days of the event and must explain the impact on consumers, the remedial action taken and the expected timeline for full restoration. In our disputes practice, we have seen enforcement cases open on the basis of a late interim update alone, even where the underlying incident was resolved quickly and caused no consumer loss. The lesson is that the disclosure obligation is as binding as the substantive rule it reports on.

Interaction with white papers and prospectus content

Token issuers face a double burden: the white paper required at the point of offering must cover governance, risk and environmental impact in summary form, and the annual non-financial disclosure must cover the same topics in operational detail. The white paper is forward-looking; it describes the governance model the issuer will adopt and the resilience measures it will put in place. The non-financial disclosure is backward-looking; it reports on the governance model as it operated over the past year and on the incidents that tested the resilience measures in practice.

Where a white paper makes a specific commitment – "the reserve will be audited quarterly", "the issuer will achieve carbon neutrality by a stated date" – the annual disclosure must report progress against that commitment and explain any deviation. For asset-referenced tokens and e-money tokens, the interaction is particularly tight: the white paper must describe the reserve composition and the redemption mechanism in detail, and the annual disclosure must publish the actual reserve holdings, the results of the quarterly attestation and the total volume of redemptions processed. Firms that promise more in the white paper than they can deliver in the operational year face a choice between admitting the shortfall in the disclosure or facing an enforcement action for misleading the market.

For firms that do not issue tokens but that provide custody or trading services, the interaction is lighter but still present. The white paper is replaced by the disclosure document required at client onboarding, and that document must cover the same governance and resilience topics as the non-financial disclosure. The regulator expects consistency: if the client disclosure says that the firm's systems are ISO-certified, the annual report must confirm the certification and disclose the most recent audit date. Any inconsistency is treated as a potential breach of the fair-presentation rule.

Drafting the sustainability statement: energy, emissions and offsets

The sustainability statement is the most politically visible of the four disclosure categories, and it is the one for which template language is least available. Traditional financial institutions can draw on a decade of sustainability reporting under the Non-Financial Reporting Directive and its successor, the Corporate Sustainability Reporting Directive; crypto firms cannot. The industry's energy footprint is contested, the accounting methodology for on-chain emissions is not standardised and the treatment of carbon offsets purchased by the firm is subject to regulatory and public scrutiny.

Firms that custody or stake proof-of-work assets face the highest disclosure burden. They must estimate the energy consumed by the network per transaction, allocate a portion of that consumption to their own custody activity and report the resulting carbon footprint in tonnes of CO₂ equivalent. Where the firm operates its own mining or validation infrastructure, the calculation is straightforward: total energy consumed, multiplied by the carbon intensity of the local grid, equals the firm's direct emissions. Where the firm custodies assets without operating nodes, the calculation is indirect and relies on third-party estimates of network energy consumption. The regulator permits the use of published models – those from the Cambridge Centre for Alternative Finance, for example – but requires the firm to disclose the model used, the assumptions it embeds and the margin of error in the result.

Proof-of-stake networks present a different challenge. The energy consumption per transaction is negligible, but the governance question is sharper: if the firm operates a validator node, does it vote on protocol changes that affect energy use or does it delegate that vote to a foundation or to other validators? The sustainability statement must disclose the firm's voting policy and explain how it considers environmental factors in governance decisions. For firms that provide staking-as-a-service to clients, the disclosure must also cover whether the firm offers clients a choice of validators based on their sustainability credentials.

Carbon offsets are treated with suspicion by the regulator. A firm that claims carbon neutrality on the strength of purchased offsets must disclose the volume of offsets purchased, the project from which they were sourced, the standard to which the project was certified and the year in which the offsets were generated. Offsets from projects that are more than five years old, or that are not certified to a recognised standard, do not count toward the neutrality claim. In our licensing practice, we advise clients to avoid making hard carbon-neutrality commitments in the white paper unless the offsetting strategy is already in place and can be evidenced in the first disclosure cycle.

Governance disclosure: board structure, conflicts and remuneration

The governance disclosure must identify each member of the board by name and role, state whether they are executive or non-executive and disclose any other directorships they hold in financial or technology firms. The regulator is alert to conflicts of interest: a non-executive director who also sits on the board of a competing exchange, or who holds a significant token position in a project the firm custodies, must be disclosed. The firm must also explain the process by which conflicts are identified and managed, and whether any board decisions in the reporting period were taken in the absence of a conflicted director.

Remuneration disclosure is more intrusive than many founders expect. The total remuneration of the three highest-paid individuals must be disclosed, broken down into salary, bonus, equity or token grants and benefits in kind. Where remuneration includes tokens issued by the firm or by a related entity, the disclosure must state the vesting schedule, the performance conditions attached to the grant and the accounting treatment of the tokens for financial-reporting purposes. The regulator's concern is that token-based remuneration can create misaligned incentives – executives who are paid in the firm's own token may prioritise short-term price action over long-term consumer protection – and the disclosure is intended to surface those risks.

Firms that are controlled by a parent entity outside the EU face additional governance disclosure. They must explain the control structure, identify the ultimate beneficial owner and state whether the parent is itself regulated in its home jurisdiction. Where the parent is in a jurisdiction that the EU has designated as high-risk for money-laundering purposes or that does not cooperate on tax transparency, the firm must disclose the steps it has taken to ensure that group-level decisions do not compromise its compliance with EU rules. In a recent licensing matter, a custodian with a parent in a non-cooperative jurisdiction was required to appoint an independent compliance officer with a power to veto group instructions that conflicted with MiCA obligations. That veto power, and the process for invoking it, had to be disclosed in the governance statement.

Operational resilience and cyber: incidents, testing and third-party risk

Operational resilience is measured by system uptime, incident frequency and recovery time. The firm must report its actual uptime percentage over the reporting period, broken down by service category – trading, custody, client onboarding – and explain any material deviation from the service-level agreement published in the client terms. An uptime figure below the promised level is not a breach in itself, but it triggers an obligation to disclose the cause of the downtime, the number of clients affected and the compensation offered.

Cyber incidents must be reported in summary form: the number of incidents in the reporting period, classified by severity; the number that resulted in unauthorised access to client data or to private keys; the time taken to detect and contain each incident; and the remedial action taken. The regulator does not require disclosure of the technical details of an exploit – that would create a roadmap for future attackers – but it does require a plain-language explanation of the root cause and the control failure that allowed the incident to occur. Where an incident was caused by a third-party supplier, the firm must disclose the supplier, the service it provides and the steps taken to prevent recurrence.

Penetration testing and third-party certification are disclosed as evidence of the firm's resilience posture. The firm must state the date of the most recent penetration test, whether it was conducted by an independent security firm, the scope of the test and the number of critical and high-severity findings. It must also disclose any security certifications it holds – ISO 27001, SOC 2 Type II, PCI DSS – and the date on which each was awarded and most recently audited. A firm that claims to be "bank-grade secure" in its marketing must evidence that claim in the operational-resilience disclosure; the regulator treats unsubstantiated security claims as misleading advertising.

Consumer protection and complaints: the operational test

The consumer-protection disclosure is an operational test of the promises made in the white paper and the client terms. The firm must report the total number of complaints received, the proportion resolved within the target timeframe stated in the client terms, the proportion escalated to the national ombudsman and the root causes of the ten most common complaint types. Where a firm has a high complaint rate relative to its transaction volume, or where the proportion of complaints escalated to the ombudsman is above the sectoral average, the regulator will open a supervisory inquiry.

Vulnerable-customer handling is a new focus for crypto firms. The regulator expects firms to have a process for identifying customers who may be at risk of financial harm – those with poor digital literacy, those transacting in amounts that appear inconsistent with their stated financial position, those who contact customer support repeatedly with questions that suggest confusion – and to have a procedure for offering additional support or for declining to onboard them. The disclosure must state the number of customers identified as vulnerable, the support offered and the number of account applications declined on vulnerability grounds. In our compliance practice, we see many firms struggle with this requirement because the client-onboarding flow was designed for speed, not for vulnerability screening, and retrofitting a screening layer is technically complex.

Compensation and redress must also be reported. The firm must disclose the total value of compensation paid to consumers in the reporting period, broken down by cause – operational error, security incident, mis-selling. It must also state whether it holds professional-indemnity insurance or whether it maintains a reserve fund for consumer redress, and if so, the size of the fund and the governance rules that control its use. The regulator's expectation is that a firm with a material volume of retail clients will hold insurance or a reserve fund sufficient to cover at least six months of potential redress claims at the average payout level.

Cross-border firms: consolidation, tied agents and branch reporting

A firm that operates in multiple member states has three structural choices, and each affects the disclosure burden differently. The first is a single entity authorised at group level, with tied agents in each member state; the second is a branch network, with each branch registered under the passporting rules; the third is a collection of separately authorised entities, one per member state. The first two allow consolidated reporting; the third requires separate reports for each entity.

Consolidated reporting is simpler but not cost-free. The parent must aggregate the sustainability, governance, resilience and consumer-protection data from all tied agents and branches, apply the ESMA reporting template and file a single report with the home-state competent authority. That authority then shares the report with the host-state authorities, which may request additional detail on the operations in their jurisdiction. The consolidation exercise itself is substantial: data formats differ across jurisdictions, incident definitions vary, and the parent must reconcile those differences before the data can be aggregated. In our licensing practice, we advise clients to plan for two months of aggregation and reconciliation work before the annual report can be drafted.

Firms that choose separate authorisations in each member state cannot consolidate. Each entity files its own disclosure suite with its own competent authority, and each is assessed independently. The compliance burden is multiplied by the number of jurisdictions, but the advantage is that a poor performance in one member state – a high complaint rate, a significant cyber incident – does not automatically trigger scrutiny of the operations in other member states. For a firm with uneven operational maturity across its network, separate reporting may be the safer choice.

Timing, attestation and the cost of external review

External attestation is required for the sustainability statement and for the governance section of the disclosure. The regulator accepts attestation from a firm of chartered accountants, from a specialist ESG consultant or from a legal advisor with relevant technical expertise. The attester reviews the firm's data sources, the calculation methodology and the narrative explanations, and issues an opinion on whether the disclosure fairly presents the firm's position. A qualified opinion – one that highlights data gaps, methodological weaknesses or incomplete explanations – must be disclosed alongside the report, and it will trigger a supervisory inquiry.

The cost of attestation is jurisdiction-specific and depends on the complexity of the firm's operations. For a mid-sized exchange with a straightforward custody model and a single-entity structure, the annual review typically sits in the low five figures. For a multi-entity group with complex third-party dependencies, with token-based remuneration schemes and with a carbon-offset strategy that requires verification, the review cost can reach the low six figures. Firms budget less than they should and are surprised by the cost at the end of the first reporting cycle. In our structuring practice, we build attestation cost into the annual compliance budget at the point of authorisation, and we identify the attestation provider before the first disclosure is due.

The publication deadline is strict. A late report is treated as a breach of the MiCA transparency rules, and the penalty is immediate: the firm's authorisation status is flagged as "non-compliant" on the ESMA register, and that flag remains visible to the public until the report is filed. For a firm with institutional clients or with banking relationships, the flag is commercially fatal. Clients and counterparties routinely check the ESMA register before onboarding a crypto-asset service provider, and a non-compliant flag is grounds for immediate termination of the relationship.

Interaction with national company-law and listing-rule disclosure

MiCA disclosure sits alongside, not instead of, national company-law disclosure obligations. A firm that is incorporated in a member state must still file annual accounts, a directors' report and, where it meets the size thresholds, a sustainability report under national law. The content overlap between the MiCA disclosure and the national sustainability report is substantial, but the templates are not identical. The MiCA template is prescribed by ESMA and focuses on consumer protection and operational resilience; the national template follows the Corporate Sustainability Reporting Directive and covers a broader set of environmental and social topics, including supply-chain due diligence and workforce diversity.

For firms that are listed on a regulated market or on an MTF, listing-rule disclosure adds a third layer. The listing rules require half-yearly and annual financial reports, ad-hoc disclosure of inside information and, for issuers of financial instruments, a transparency obligation that mirrors the MiCA white-paper rule. A crypto-asset service provider that is also a listed issuer must reconcile three disclosure streams – MiCA, national company law, listing rules – and ensure that the narrative is consistent across all three. Inconsistency is treated as market abuse: if the annual report says that the firm has strong cyber resilience but the MiCA disclosure reports a material incident, the regulator will investigate whether the annual report was misleading.

Enforcement and penalties for incomplete or misleading disclosure

The penalties for late, incomplete or misleading non-financial disclosure are the same as those for a breach of the authorisation conditions: a formal warning, a fine or, in serious cases, withdrawal of the authorisation. A firm that files a disclosure with material omissions – it fails to report a cyber incident, it overstates its system uptime, it omits a board member's conflicting directorship – faces the same enforcement path as a firm that operates outside the scope of its licence. The regulator's position is that transparency is as fundamental to consumer protection as capital adequacy or custody safeguards.

In practice, the most common enforcement action is a requirement to restate and republish the disclosure within a short deadline. The firm must issue a public correction, file the corrected version with the competent authority and send a direct notice to all clients explaining the error and the corrected position. The reputational cost of a restatement is high, and the operational cost – drafting the correction, securing board approval, re-engaging the external attester – is comparable to the cost of preparing the original disclosure. In a recent supervision case known to our disputes practice, a custodian that failed to disclose a minor cyber incident in its annual report was required to restate, and the restatement process took three months and cost more than the original report.

Systemic or repeated failures trigger licence withdrawal. A firm that files late reports in two consecutive years, or that publishes materially misleading sustainability claims and fails to correct them when challenged, will be invited to show cause why its authorisation should not be revoked. The cause-shown process is adversarial and public, and it is rare for a firm to survive it with its licence intact. The lesson for operators is that non-financial disclosure is not a tick-box compliance exercise; it is a material obligation that must be resourced and governed to the same standard as the financial reporting and the risk management that underpin the licence itself.

Practical preparation: building the disclosure function before go-live

Firms that wait until the six-month deadline to begin preparing the first disclosure find that the data they need was never collected. System uptime was not logged at service-category level; cyber incidents were resolved but not documented in a format that maps to the ESMA template; complaints were handled but not categorised by root cause. The result is a scramble to reconstruct the data from email threads, support tickets and incident logs, and the final disclosure is incomplete or hedged with qualifications that invite supervisory scrutiny.

The alternative is to build the disclosure function into the operating model from the point of authorisation. That means implementing logging and monitoring systems that capture the required data points – uptime by service, incident classification, complaint root causes – in real time. It means establishing a quarterly review cycle in which the compliance team, the technology team and the customer-support team meet to review the data, identify any gaps and agree on the narrative that will appear in the annual report. And it means engaging the external attester early, at the end of the first quarter, so that any methodological issues can be corrected before the year-end data is finalised.

In our licensing practice, we build a disclosure-readiness checklist into the authorisation work plan. The checklist covers data capture, governance sign-off, attestation procurement and the internal review cycle, and it is reviewed at each project milestone. Firms that follow the checklist meet the six-month deadline comfortably and file a disclosure that requires no material revision. Firms that ignore it spend the first year in reactive mode, and the disclosure they eventually file is weaker than their actual operational performance would justify.

For a scoped assessment of your disclosure obligations before the first filing deadline, contact OBOLUS at info@oboluslaw.com. We map the data points your systems must capture, the governance approvals you will need and the attestation route that fits your structure.

A recent authorisation: disclosure as the critical path

In the first quarter of the current reporting season, an exchange authorised under MiCA in a Baltic member state discovered three weeks before its first disclosure deadline that its incident-logging system did not capture the data required by the ESMA template. The system logged incidents by severity but not by cause, and it did not track the time to detection or the time to containment. The firm had experienced two significant incidents during the reporting period – a denial-of-service attack that caused three hours of downtime and a configuration error that exposed client email addresses – but the logs did not contain enough detail to complete the operational-resilience section of the disclosure.

The firm reconstructed the incident data from server logs and from the post-incident review documents prepared by the technology team. That reconstruction took two weeks and required input from engineers who had since left the business. The final disclosure was filed on time, but it included a qualification: the incident data was described as "reconstructed from operational records" rather than "captured in real time," and the external attester noted in the opinion that the firm's logging system did not meet the standard expected of a regulated entity. The competent authority opened a supervisory inquiry, and the firm was required to implement a new incident-management platform and to resubmit evidence of its effectiveness at the next reporting cycle.

The lesson: disclosure obligations shape the technology roadmap. A firm that designs its systems without reference to the ESMA reporting template will find itself in remediation mode before it has filed its first report.

A multi-entity group: consolidation and the data-aggregation problem

In the second half of last year, a custodian operating through a parent entity in Luxembourg and tied agents in Germany, France and the Netherlands began consolidating the data for its first annual disclosure. The parent had assumed that the data formats used by the tied agents were identical, but they were not. The German agent tracked complaints by the date received; the French agent tracked them by the date resolved. The Netherlands agent had categorised cyber incidents by the team that handled them, not by the type of incident. And none of the agents had separated the uptime data by service category because the parent's initial instructions had not specified that the data needed to be segmented.

The consolidation exercise that the parent had budgeted for two weeks ultimately took two months. A consultant was brought in to reconcile the data formats, and the tied agents were required to reprocess three quarters of data manually. The final disclosure was filed one week late, and the ESMA register flagged the parent as non-compliant for that week. Two institutional clients noticed the flag and suspended onboarding pending an explanation. The parent provided the explanation – a consolidation delay, not an operational failure – but the damage was reputational. One client resumed onboarding; the other did not.

The lesson: cross-border consolidation is not an accounting exercise. It is a data-governance project that must begin at the point of authorisation, not at the point of filing.

A common assumption: disclosure is less important than the licence itself

Operators routinely approach disclosure as a compliance formality that sits downstream of the substantive licensing work. The assumption is that if the firm has been authorised, the disclosure will be straightforward – a matter of writing down what the firm already does and having it signed off by the board. That assumption fails in three ways. First, the disclosure obligation is as binding as the authorisation conditions; a late or incomplete report triggers the same enforcement path as a breach of capital adequacy or custody safeguards. Second, the data required for disclosure must be captured in real time, not reconstructed from memory at year-end, and capturing it requires systems that many firms do not build until the first deadline is approaching. Third, the reputational risk of a non-compliant flag on the ESMA register is material; clients and counterparties check the register before onboarding, and a flag is grounds for suspension or termination.

The firms that succeed treat disclosure as an operational requirement from day one. They build the logging systems, establish the quarterly review cycle and engage the external attester early. The firms that fail treat disclosure as an afterthought and spend the first year in remediation mode. The difference in cost, in management time and in reputational outcome is significant.

If a prior disclosure filing was incomplete or late, a structured review can identify the control gap and establish the process that prevents recurrence. Write to us at info@oboluslaw.com.

FAQ

How long does a crypto licence take to obtain?

The timeline for a crypto-asset service provider authorisation under MiCA is jurisdiction-specific and depends on the complexity of the application. In member states with established VASP regimes, the authorisation process typically takes between four and nine months from the submission of a complete application to the grant of the licence. In member states that are processing MiCA applications for the first time, the timeline can extend to twelve months or longer. The timeline begins when the competent authority confirms that the application is complete, not when it is first submitted; incomplete applications sit in a pre-assessment queue and the clock does not start. Applicants should plan for a preparation phase of two to three months before submission, during which the business plan, governance documents and technical systems are finalised and reviewed.

Which jurisdiction suits my crypto business?

The choice of jurisdiction turns on where your users are, where your banking sits and where your operational team is based. For a firm serving clients across the EU, authorisation in any member state allows passporting into all others, so the choice is between states with established supervisory practices and those with faster timelines. States with prior VASP regimes – Lithuania, Malta, France – offer deeper supervisory experience but higher compliance expectations. States entering the MiCA regime for the first time may offer faster authorisation but less certainty on interpretation. For a firm serving clients outside the EU, a European licence may still be necessary if the firm custodies assets for EU-resident users or if it markets its services into the EU. The jurisdiction that suits your business depends on the client base, the operating model and the banking strategy, and a structured comparison across three to five candidate states is standard practice at the licensing stage.

Do I need a separate custody licence?

Custody of crypto-assets on behalf of clients is a regulated activity under MiCA, and a firm that provides custody must be authorised as a crypto-asset service provider with custody listed in the scope of its authorisation. A separate custody licence as a distinct legal instrument does not exist under MiCA; instead, custody is one of several services that may be included in a CASP authorisation. A firm that provides trading or advisory services without holding client assets does not need custody in its authorisation scope. A firm that intends to add custody later must apply for a variation of authorisation, and that variation is treated as a new application with a full review of governance, systems and capital adequacy. For firms operating across multiple jurisdictions, the custody authorisation in the home member state allows the firm to passport custody services into other member states without applying for separate approvals.

About OBOLUS

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across more than seventy jurisdictions, on disputes and on-chain asset recovery across twenty-five forums, and on the tax, banking and compliance systems that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we build disclosure and attestation processes into the licensing roadmap from the point of application. To discuss your situation, contact info@oboluslaw.com.

By Aisha Tan, Licensing & Jurisdictions Analyst – Aisha specialises in MiCA authorisation, cross-border licence structuring and the interaction between licensing and non-financial disclosure obligations.

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.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours