EST · MMXXVI
Home/Insights/Guides/MiCA Complaints Handling and Conflicts of Interest for CASPs
Compliance, AML & Travel Rule

MiCA Complaints Handling and Conflicts of Interest for CASPs

MiCA Complaints Handling and Conflicts of Interest for CASPs. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee enga

A crypto-asset service provider preparing for MiCA authorisation discovers that the regulator expects documented complaints procedures, a conflicts-of-interest policy and records proving both systems work in practice. The business has customer-service workflows and internal controls already, but translating operational practice into a form that meets the European Securities and Markets Authority's supervisory expectations – and proving it under audit – is a different exercise. Under the Markets in Crypto-Assets Regulation, a CASP must establish, implement and maintain effective and transparent procedures for the prompt, fair and consistent handling of complaints received from clients, and maintain a policy to identify, prevent, manage and disclose conflicts of interest that arise in the provision of crypto-asset services.

This guide sets out the steps to build a MiCA-compliant complaints-handling function and conflicts policy, the records and governance that sit around them, and the common mistakes that stall authorisation or trigger supervisory follow-up after go-live.

Why complaints and conflicts matter under MiCA

Complaints-handling and conflicts management are core organisational requirements under MiCA because they expose how a CASP treats the client when something goes wrong and whether the firm's economic interest can override the client's. ESMA and the national competent authorities treat both as tests of the CASP's governance, culture and fitness to hold authorisation. A complaints procedure that exists on paper but is not followed in practice, or a conflicts policy that lists theoretical scenarios without explaining how the firm actually manages them, will surface in the application vetting or the first supervision cycle and may result in a request for additional information, conditions on authorisation or an enforcement referral.

The regime applies to every CASP, regardless of size or service mix. There is no de minimis threshold, no small-operator carve-out and no grandfathering for firms transitioning from prior national regimes. If your entity requires CASP authorisation, the complaints and conflicts framework must be in place before the regulator grants the licence – and it must remain current as the business scales, adds services or changes its revenue model.

If the application file does not show how complaints are logged, investigated, escalated and closed – and how conflicts are identified and addressed at the business-line level – the regulator will ask for a second pass. By that stage, the authorisation timeline has slipped and management is retrofitting process documentation under time pressure. In our cross-border licensing practice, we see firms treat these requirements as afterthoughts, then scramble when the competent authority requests evidence of real-world application during the pre-authorisation review.

What the complaints handling procedure must include

The MiCA complaints procedure must cover five elements: receipt and acknowledgment, investigation and decision-making, escalation and alternative dispute resolution, record-keeping, and periodic reporting to senior management and the competent authority. Each element requires documented process, assigned ownership and evidence that the procedure operates as written.

Receipt and acknowledgment. The procedure must specify how clients can submit complaints – email, web form, postal address – and the timeline for the firm's acknowledgment. The expectation is a clear, accessible channel and a prompt acknowledgment that confirms receipt and provides a reference number. A generic customer-service inbox that also handles service queries is acceptable if the firm can demonstrate that complaints are identified, flagged and routed correctly.

Investigation and decision-making. The procedure must set out who investigates the complaint – typically someone outside the team that handled the original transaction or service interaction – and the maximum time for a substantive response. The investigation should include a review of relevant records, communication with the client if clarification is needed, and a written decision explaining the outcome and the reasoning. The regime does not mandate a specific investigation timeline, but national competent authorities generally expect a substantive response within a matter of weeks, not months.

Escalation and alternative dispute resolution. If the client is not satisfied with the initial response, the procedure must explain the internal escalation route and, where applicable, the availability of an out-of-court dispute-resolution mechanism. Some member states operate financial ombudsman schemes or alternative dispute resolution bodies for investment services; the CASP must inform the client of any such scheme that covers crypto-asset services in the jurisdiction of authorisation.

Record-keeping. Every complaint must be logged in a complaints register with sufficient detail to allow supervisory review: the date, the client identifier (pseudonymised if required by data-protection rules), the nature of the complaint, the investigation findings, the decision, the timeline from receipt to closure, and any follow-up action. The register must be retained for a period that aligns with the regulator's record-retention requirements – typically five years – and must be producible on request.

Periodic reporting. Senior management and the competent authority receive periodic summaries of complaints received, resolved and outstanding, and any thematic issues or process failures the complaints reveal. The reporting frequency to management is typically quarterly; reporting to the competent authority follows the supervisory-return schedule set by the national authority.

The conflicts of interest policy structure

The conflicts policy must identify the circumstances that give rise to a conflict of interest in the CASP's business, explain how the firm prevents or manages each conflict, and describe the disclosure to clients where prevention or management is not sufficient. The policy sits at the intersection of governance, revenue structure and service design, and it must be tailored to the CASP's actual activities – not copied from a template written for a different type of firm.

A conflict arises where the CASP or a person within the firm has an interest that may conflict with a client's interest, or where one client's interest conflicts with another client's. Common sources of conflict in crypto-asset services include proprietary trading alongside client execution, fee structures that reward transaction volume over client outcomes, referral or revenue-sharing arrangements with third parties, and the use of affiliated entities for custody, liquidity or banking services.

The policy must address each material conflict at a practical level. For example, if the CASP operates a trading desk that takes proprietary positions in the same assets that clients trade, the policy must explain the controls that prevent information leakage, front-running and unfair pricing – typically through Chinese walls, separate trading systems and independent surveillance. If the CASP earns rebates from liquidity providers or market makers, the policy must disclose this to clients and explain how the firm ensures that client orders receive best execution regardless of the rebate.

Where a conflict cannot be prevented or adequately managed through internal controls, the CASP must disclose the nature and source of the conflict to the client before providing the service, in a durable medium and in clear terms. The disclosure obligation is not satisfied by a generic conflicts statement buried in the terms of service; it requires a specific, comprehensible explanation of the conflict relevant to the transaction or relationship.

Governance and three lines of defence

Both the complaints procedure and the conflicts policy must be embedded in the CASP's governance framework and subject to the three-lines-of-defence model that MiCA expects from authorised firms. The first line – business operations – implements the procedures day to day. The second line – compliance and risk – monitors adherence, escalates issues and proposes policy updates. The third line – internal audit – tests the effectiveness of the controls and reports findings to senior management and the board.

The compliance function reviews complaints data quarterly to identify patterns: repeated issues with a particular service, jurisdiction or transaction type signal a control gap or a design flaw that requires corrective action. The risk function assesses whether conflicts are being identified and managed consistently across business lines, and whether new services or revenue arrangements introduce conflicts not covered in the current policy. Internal audit tests a sample of complaints files annually to verify that investigations followed procedure, decisions were documented and escalations occurred where required.

Senior management – typically the board or management body – receives a quarterly report summarising complaints and conflicts activity, thematic findings and any material changes to the policy or procedure. This report forms part of the supervisory record and demonstrates that governance oversight is active, not nominal.

The cross-border dimension for multi-jurisdiction CASPs

A CASP authorised in one member state and passporting into others must apply a single complaints procedure and conflicts policy across the entire European Economic Area footprint. The procedure must accommodate complaints from clients in any EEA jurisdiction where the CASP provides services, and the policy must address conflicts that arise from the firm's pan-European activity. This creates practical challenges where local consumer-protection rules, language requirements or alternative-dispute-resolution mechanisms vary.

The complaints procedure must specify how the CASP handles complaints submitted in a language other than the working language of the home-state competent authority. Best practice is to accept complaints in any official EU language and arrange translation where necessary, or to state clearly which languages the procedure supports and provide contact details for a multilingual complaints officer.

The conflicts policy must account for cross-border service arrangements. For example, a CASP may use an affiliated custody provider in one jurisdiction, a payments partner in another and a liquidity provider in a third. Each arrangement must be assessed for conflicts, and the policy must explain how the CASP ensures that client interests are protected when multiple legs of a service involve related parties. The competent authority expects the policy to address conflicts at the group level, not only at the level of the individual authorised entity.

For a multi-hub operator, the structural question is whether to centralise complaints handling and conflicts management in the home state or to maintain satellite teams in each host state. Centralisation offers consistency and efficiency but requires investment in multilingual capability and real-time case management. Distributed handling offers local responsiveness but increases the risk of inconsistent decisions and control gaps. The choice depends on the firm's scale, service model and governance appetite – and it must be documented in the procedure and reflected in the staffing plan submitted with the authorisation application.

Records the regulator expects to see

Supervisory review of complaints and conflicts focuses on records that prove the systems work in practice. The competent authority will request, during the authorisation vetting or a periodic inspection, the complaints register, a sample of closed complaints files, the conflicts register (if the CASP maintains one as best practice), minutes of senior-management discussions on complaints and conflicts, and evidence of staff training on both procedures.

The complaints register must be a searchable, structured log – a spreadsheet or database – not a folder of email threads. Each entry must show the complaint reference, the submission date, the client identifier, a short description of the issue, the assigned investigator, the decision date, the outcome and any follow-up. Where a complaint was escalated to alternative dispute resolution or resulted in a payment or service adjustment, that must be noted. A register that shows zero complaints over a sustained period will prompt questions: either the firm is not logging complaints correctly or clients are not aware of the complaints channel.

The conflicts register is not a MiCA requirement but has become a de facto supervisory expectation. It is a document that lists each identified conflict, the business line or service where it arises, the controls in place to manage it, the residual risk after controls and the disclosure approach if applicable. The register is reviewed quarterly by compliance and updated when new services launch or revenue models change. It gives the regulator a single point of reference for how the CASP's conflicts framework operates in practice.

Training records must show that staff who handle complaints or make service decisions have been trained on the complaints procedure and the conflicts policy, understand their obligations and know when to escalate. Training is typically delivered during onboarding and refreshed annually, with attendance tracked in the CASP's learning-management system.

Common mistakes that delay authorisation

The most common error is submitting a generic complaints procedure copied from a template for a different type of financial-services firm. The regulator expects a procedure that reflects the CASP's actual services – for example, how complaints about transaction delays on a blockchain are investigated differently from complaints about a refused fiat withdrawal. A boilerplate procedure signals that the applicant has not thought through implementation.

A second mistake is treating the conflicts policy as a disclosure exercise rather than a control framework. A policy that lists potential conflicts and states "the firm will disclose these to clients" without explaining how conflicts are prevented or managed in the first instance will not satisfy the regulator. The disclosure obligation is a fallback, not the primary control.

A third mistake is failing to assign clear ownership. The complaints procedure must name the role responsible for complaints handling – typically a compliance officer or a designated complaints manager – and the conflicts policy must specify who reviews and updates it and how often. If the policy is silent on ownership, the regulator will ask who is accountable, and the answer cannot be "the board" without an implementing officer.

A fourth mistake is ignoring the cross-border angle. A CASP that plans to passport into multiple host states but submits a complaints procedure written only in the home state's language, with no reference to host-state alternative-dispute-resolution mechanisms, will be asked to revise it. The procedure must work for the entire EEA footprint from day one.

When to engage counsel on complaints and conflicts

The procedural framework for complaints and conflicts sits at the boundary between legal obligation, operational design and governance culture. Firms typically engage counsel at three points: during the pre-application phase to translate the MiCA requirements into a documented procedure and policy, when the competent authority requests clarification or additional detail during the authorisation review, and when a material complaint or conflict surfaces post-authorisation and management needs advice on escalation, disclosure and supervisory reporting.

A scoped advisory engagement early in the application process avoids the need to rebuild the framework under time pressure later. The work involves reviewing the firm's current complaints-handling workflow and conflicts-identification process, mapping them against the MiCA expectations, drafting the formal procedure and policy documents, and preparing the complaints and conflicts register templates. The deliverable is a set of documents ready for submission with the authorisation application and a training deck for staff who will implement them.

Operators we advise routinely underestimate the effort required to document these systems in a form that satisfies a European competent authority. The investment is not in legal complexity – the concepts are straightforward – but in the discipline of turning operational practice into auditable process and proving that the process is followed consistently. For a scoped assessment of your complaints and conflicts readiness, contact OBOLUS at info@oboluslaw.com.

Building the framework before you apply

The sequence for building a MiCA-compliant complaints-and-conflicts framework runs as follows. First, map the firm's current complaints-handling practice: where do complaints come in, who handles them, how are decisions made, where are they logged. Second, draft the formal complaints procedure that documents this practice, fills any gaps the mapping revealed and assigns ownership. Third, test the procedure with a pilot: run a small number of historical or simulated complaints through it to verify that the steps work and the records come out correctly.

Fourth, identify the conflicts that arise in each of the firm's service lines – custody, exchange, advisory, portfolio management, transfer, issuance platform – using a structured workshop with business, compliance and legal. Fifth, draft the conflicts policy that explains how each identified conflict is prevented, managed or disclosed. Sixth, build the conflicts register and train the business on how to update it when new services or arrangements are added.

Seventh, embed both the complaints procedure and the conflicts policy in the compliance manual and the staff handbook, and deliver initial training to all relevant staff. Eighth, prepare the quarterly reporting template for senior management and the annual supervisory-return template if the competent authority has published one. Ninth, submit the documented framework with the CASP authorisation application, supported by a short narrative explaining how the firm's approach meets each element of the MiCA requirement.

The timeline from start to final documentation is typically four to eight weeks, depending on the firm's scale and whether the current practice requires material redesign. The critical path is the conflicts-identification workshop: if the firm's revenue model includes referral fees, payment-for-order-flow arrangements or affiliate service providers, the conflicts analysis takes longer and the policy must be more detailed.

Post-authorisation: the annual review cycle

Once authorised, the CASP must review and update the complaints procedure and conflicts policy at least annually, and more frequently if the business changes materially. The review cycle is typically tied to the end of the financial year and feeds into the board's annual governance report. The compliance function leads the review, with input from business lines, risk and legal.

The review asks: have there been changes to the services offered, the revenue model, the service providers or the group structure that introduce new conflicts or change how complaints are received? Are the current controls effective, or have complaints revealed gaps? Has the competent authority issued new guidance or supervisory expectations on complaints or conflicts that require a policy update? Are the record-keeping and reporting processes working as designed, or do they need refinement?

Material changes to the policy or procedure must be notified to the competent authority in the next supervisory return, and some authorities expect advance notification if the change affects how conflicts are managed or complaints are escalated. A CASP that launches a proprietary trading desk or enters into a revenue-sharing arrangement with a liquidity provider mid-year must update the conflicts policy immediately and inform the regulator at the next scheduled reporting point, not wait for the annual review.

Related at OBOLUS

FAQ

What does MiCA require from a CASP's complaints procedure?

MiCA requires a CASP to establish, implement and maintain effective and transparent procedures for the prompt, fair and consistent handling of complaints from clients. The procedure must cover receipt and acknowledgment, investigation, escalation, alternative dispute resolution where available, and record-keeping. Every complaint must be logged in a register and reviewed periodically by senior management and the competent authority. The procedure must be documented and accessible to clients, and staff must be trained on it.

How does a CASP identify conflicts of interest under MiCA?

A conflict of interest arises where the CASP or a person within the firm has an interest that may conflict with a client's interest, or where one client's interest conflicts with another's. Identification requires a structured review of the firm's revenue model, service arrangements, related-party relationships and staff incentives. Common sources include proprietary trading, referral fees, affiliate service providers and volume-based compensation. The conflicts policy must list each identified conflict and explain how it is prevented, managed or disclosed.

What records must a CASP keep for complaints and conflicts?

The CASP must maintain a complaints register showing the date, client identifier, nature of the complaint, investigator, decision, timeline and outcome for each complaint. Closed complaints files must be retained for the regulator's inspection period, typically five years. For conflicts, best practice is a conflicts register listing each conflict, the controls in place, the residual risk and the disclosure approach. Training records, senior-management reports and policy-review minutes form part of the governance record and must be producible on supervisory request.

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 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance 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 coordinate freezing relief and on-chain tracing across leading common-law forums when recovery clocks are running. To discuss your MiCA authorisation or a complaints or conflicts audit, contact info@oboluslaw.com.

By Victor Olsen, Regulatory & Compliance Analyst – MiCA organisational requirements and CASP authorisation readiness across the European Economic Area.

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