A polished application is not enough

The quality problem in a MiCA (Markets in Crypto-Assets) application is rarely solved by better wording alone. The core question is whether corporate documents, contracts, organizational responsibilities, technology and policies describe one coherent business. A mismatch between the paper model and the real service flow can generate supervisory questions even where each individual policy appears well drafted.

Management capability and substance

The licensed entity needs real decision-making and oversight capability. Review should cover reporting lines, management availability and competence, access to information, internal staffing, systems access and the ability to challenge or replace providers. Formal titles cannot compensate for an operating model in which responsibility cannot actually be exercised.

Outsourcing without regulatory hollowing-out

Outsourced functions should be mapped individually. Contracts, service levels, information and audit rights, incident cooperation, business continuity, subcontracting and exit need to support the oversight model. Internally, each important service requires an accountable owner who can monitor performance and escalate failures.

Custody and asset flows

Where custody or control over client assets is relevant, legal analysis and technical architecture have to meet. Wallet design, segregation, reconciliation, withdrawal processes and third-party dependencies should be consistent with client terms and the application narrative. The location of technical control can affect legal responsibility.

Readiness means evidence

A pre-filing review should test each material requirement through owner, control, procedure, record and evidence. It should also identify missing approvals, policies that have not been implemented and contracts that do not support the promised operating model. Filing should follow a controlled consistency review rather than becoming the first time the components are compared.

Turning the analysis into a controlled mandate

In a live mandate concerning the authorization file, the work cannot stop at high-level advisory language. The legal conclusion should be translated into a controlled workplan covering governance, outsourcing, custody, ICT and whether the applicant can operate the model it describes. Each material issue receives a factual owner and legal owner, required documents, decision point, dependencies and a completion criterion. This allows the team to distinguish true blockers from parallel workstreams and from tasks requiring a specialist or local counsel. It also provides disciplined change-control when the client alters a business assumption during the project, rather than allowing scope and responsibility to expand informally.

Failure modes to identify before they become regulatory statements

The most expensive problems are not always difficult points of law. They are often policy owners with no authority, outsourced functions without meaningful oversight and asset flows inconsistent with customer terms. Those inconsistencies should be found before they become a filing, supervisory statement, board representation or contractual commitment. The delivery model uses an issue log recording severity, legal implication, business impact, owner and required decision. Where a gap cannot responsibly be closed in time, it should be disclosed internally and managed through an informed decision rather than hidden by drafting that creates a larger problem later.

Evidence, quality control and later review

A strong project file allows an independent reviewer to trace the path from requirement to decision and implementation. Depending on the matter, the record should include responsibility matrices, outsourcing registers, custody evidence, management approvals and a pre-filing consistency review. Evidence should not sit in an unstructured folder: it should be linked to a requirement or action and carry an owner, date, version and review status. Before filing, closure or management assurance, a second consistency review should test whether claims, contracts, governance records and operational proof remain aligned.

Cross-border and professional-practice controls

In cross-border work, the language of a deliverable does not determine the governing law. the chosen Member State still requires local legal and supervisory adaptation. Each country therefore passes a separate jurisdiction, practice-rights and professional-conduct gate. OIKONOMAKIS LAW may coordinate the overall matter, while local-law opinions or representation are allocated to appropriately qualified professionals where required. The same distinction applies to marketing: a service that can be delivered into a market is not automatically eligible for every form of paid targeting or personalized solicitation in that jurisdiction.

 

Deeper analysis and implementation:

Substance before policy production

Organizational substance is not established by an organization chart. The firm must be able to show who has the time, competence, authority and information necessary to perform each regulated responsibility. Governance documents must align with engagement terms, delegations, committee mandates, system access and escalation routes. If those elements conflict, the issue is structural rather than editorial.

Group models require particular care where people, technology or compliance resources sit outside the applicant. The analysis should distinguish support, delegation and outsourcing, identify responsibilities that remain with the CASP and ensure that information and access rights allow effective oversight.

Custody and actual control

Custody analysis should follow the end-to-end asset and key-control model rather than a wallet label. It should identify who can move assets, how keys are generated and protected, what approvals exist, how segregation and reconciliation operate, how failed transactions or compromise are handled and which third parties create material dependencies. This technical map is legally relevant because it reveals actual control and accountability.

Every significant proposition should then be supported by evidence. A policy requiring daily reconciliation is not sufficient if there is no tested process, sample record, accountable owner and escalation for exceptions. The same evidence discipline applies to complaints, conflicts, outsourcing oversight, continuity and change management.

Independent pre-filing challenge

Before submission, the dossier should be challenged by reviewers who are not limited to proofreading. The review should identify contradictions, unresolved assumptions, controls that have not been implemented and claims that are not supported by evidence. A final readiness report should distinguish complete items, implemented controls with incomplete evidence, open remediation and matters requiring a legal decision.

Primary / official sources for publication verification

Regulation (EU) 2023/1114 (MiCA) — https://eur-lex.europa.eu/eli/reg/2023/1114/oj/eng — EU MiCA framework.

Commission Delegated Regulation (EU) 2025/305 — https://eur-lex.europa.eu/eli/reg_del/2025/305/oj/eng — CASP authorization application information.

ESMA — MiCA — https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica — Current supervisory material.

Prepared by Christos Oikonomakis, Chairman, OIKONOMAKIS LAW

Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.