CASP Wind-Down Planning — Operational Guide 2026

What Article 84 actually requires

MiCA Article 84 sets the recovery and resolution planning framework for CASPs. The article is less detailed than equivalent provisions for credit institutions under the BRRD but produces real operational requirements:

Recovery plan. Operational measures available to the CASP to restore viability under stress without external support. Capital actions, asset disposals, business-line exits, operational cost reduction, and customer-facing measures.

Resolution plan. Operational measures available where recovery is not viable or where supervisor-directed action requires orderly cessation. Customer notification framework, asset return mechanism, contract termination process, and deregistration sequencing.

Wind-down framework. Operational sequencing for orderly cessation of CASP activity. The wind-down framework is the operational core of the resolution plan — how the CASP actually stops operating without producing customer harm or market disruption.

Article 84 does not require a specific plan format but produces real substantive expectations. NCAs increasingly test wind-down plans during routine supervisory dialogue, particularly for larger CASPs and designated CASPs under Article 85.

When wind-down planning activates

A CASP wind-down plan can activate under three principal scenarios:

Voluntary wind-down. Board decision to cease CASP activity. Reasons include strategic pivot, business-model failure, sale to a successor where the successor does not require continued authorisation, or shareholder-driven decision. The CASP activates the plan and works through orderly cessation under supervisor coordination.

Supervisor-directed wind-down. Home NCA directs cessation of CASP activity. Reasons include authorisation withdrawal under Article 64, enforcement action with cessation as remedy, or supervisor concerns that warrant orderly exit rather than continued operation under enhanced supervision.

Insolvency-protective wind-down. Financial stress or insolvency risk triggers wind-down to preserve client assets and produce orderly market exit. The framework operates alongside insolvency proceedings to protect client interests during the broader corporate process.

Each scenario produces different operational dynamics. Voluntary wind-down typically has longer runway and more control. Supervisor-directed wind-down operates under stricter supervisor coordination. Insolvency-protective wind-down operates under additional procedural constraints.

The customer notification framework

Customer notification is operationally the longest and most resource-intensive part of CASP wind-down. The framework needs to address:

Notification channels. Email, in-app notification, web banner, and SMS for material customer segments. Multiple channels are needed because single-channel notification fails for customers with stale email or low app engagement.

Multi-language support. EU-operating CASPs serve customers across multiple language groups. Notification content needs translation appropriate to the customer base. English-only notification fails for customers in non-English-primary member states.

Tiered notification timeline. Customer notification operates in waves — initial notification, follow-up, final notice, post-deadline communication. Each wave addresses customers who did not respond to prior waves.

Customer instructions. Clear instructions on how customers reclaim assets, transfer to a successor CASP, or close accounts. The instructions need to work for retail customers without technical sophistication and institutional customers with bespoke arrangements.

Customer support capability. Resource scaling for customer questions during the notification period. Customer support volumes typically increase 5-10x during initial notification waves. The wind-down plan needs to address how this is staffed.

Escalation framework for unresponsive customers. Some customers will not respond to any notification wave. The plan needs a process for handling assets of unresponsive customers — typically transfer to a regulated successor or eventual escheatment under national law.

Asset return mechanics

Asset return is the operational and legal core of CASP wind-down. The framework needs to address:

Client asset segregation. Article 75 segregation continues through wind-down. Client crypto-assets remain in segregated wallets until final transfer. The wind-down framework operates on the segregated assets, not on commingled client-and-firm assets.

Customer-designated wallet transfers. The primary asset return mechanism. Customer provides destination wallet address, the CASP transfers the asset to the designated address. The framework needs to address address verification, transfer fees, technical operations, and audit trail.

Successor CASP transfer. Alternative mechanism where the CASP arranges transfer of customer assets and account information to a regulated successor CASP. The framework needs to address customer consent for transfer, KYC re-onboarding at the successor, and operational coordination.

Fiat asset return. Customer-held fiat balances return through the CASP’s banking framework. The framework needs banking access during wind-down — banks can become less cooperative once wind-down is public.

Asset return for unresponsive customers. Where customers do not provide return instructions, the framework needs a final mechanism — typically transfer to a custodial successor with notice to the original customer, or escheatment under national unclaimed-property law.

Audit trail for all returns. Every asset return needs documented audit trail — customer instruction, return execution, customer confirmation, and reconciliation. The audit trail supports both supervisor reporting and legal defence against later customer disputes.

ICT third-party exit

ICT third-party exit is one of the most under-planned aspects of CASP wind-down. CASPs depend on substantial third-party infrastructure — cloud hosting, custody technology vendors, KYC/AML vendors, blockchain analytics providers, payment processors, customer support tooling, banking partners. Each needs orderly exit during wind-down.

The DORA Article 28 exit-planning framework supports CASP wind-down. DORA requires CASPs to maintain exit plans for critical ICT third-party providers including data return, data deletion, transition assistance, and contractual exit provisions. A CASP that has built DORA-compliant exit plans has substantial wind-down ICT exit capability already in place.

Specific operational areas:

Customer data export. CASPs hold substantial customer data — KYC records, transaction history, account information. Wind-down requires structured export of this data either to customers (subject to data protection rights) or to a successor CASP (with customer consent).

Customer data deletion. Post-wind-down data retention follows national data-protection law (typically 5-7 years for AML records). The framework needs to document retention obligations and post-retention deletion.

Cloud and infrastructure exit. Cloud hosting contracts, infrastructure services, and operational tooling all need orderly termination. Data return obligations under cloud vendor contracts support the exit but require active management.

KYC and AML vendor exit. Vendor-held customer KYC data and AML records need return or proper transition. Vendor contracts typically include exit provisions; the wind-down team needs to operationalise them.

Blockchain analytics provider exit. Historical analytics data, alerting configuration, and compliance reporting framework all need orderly termination with appropriate data retention.

Regulatory deregistration

The final step of CASP wind-down is formal deregistration. The framework:

Home NCA authorisation withdrawal. Final step where the home NCA withdraws the CASP authorisation under Article 64. The withdrawal happens after operational wind-down completes and after the supervisor confirms client assets are returned and obligations discharged.

ESMA register update. The home NCA notifies ESMA which updates the ESMA-coordinated register. The CASP appears in the register as authorisation-withdrawn with effective date.

National corporate dissolution. Where the corporate vehicle is dissolved post-wind-down, corporate dissolution follows under national company law. Wind-down typically completes before corporate dissolution to allow customer claims to be addressed against the legal entity.

AML reporting framework completion. Final FIU reports, AML transaction record retention, and post-cessation cooperation obligations need documentation. AML record retention typically extends 5-7 years post-cessation.

Tax framework completion. Final tax filings, customer reporting under DAC8, and any cross-border tax matters need closure.

Supervisor coordination during wind-down

Home NCA coordinates the wind-down execution. The supervisor relationship intensifies during the wind-down period:

Pre-activation supervisor engagement. Where wind-down is voluntary, the CASP engages the supervisor before activation to align on sequencing. Where wind-down is supervisor-directed, the supervisor sets the framework.

Regular supervisor reporting. Wind-down progress reports to the home NCA at frequencies set by the supervisor — typically weekly or fortnightly during active wind-down.

Customer-asset reconciliation reporting. Detailed reporting on segregated client asset position, return progress, and outstanding balances.

Issue escalation. Operational problems during wind-down — banking exits, customer disputes, vendor issues, asset return blockers — escalate to the supervisor for guidance and where needed supervisor support.

Final closure confirmation. Supervisor signs off on wind-down completion before authorisation withdrawal. The sign-off confirms operational closure is orderly and customer interests are protected.

For designated CASPs under Article 85, ESMA participates in the supervisor coordination framework alongside the home NCA.

Plan maintenance

Wind-down plans need ongoing maintenance to remain operational. Annual review covers:

Customer base updates. Customer numbers, geographic distribution, asset position changes affect notification framework and asset return logistics.

Operational change updates. New service lines, withdrawn service lines, technology changes affect wind-down sequencing.

Third-party provider updates. New vendors, removed vendors, contract changes affect ICT exit planning.

Banking change updates. Bank relationship changes affect fiat asset return capability.

Supervisor expectation updates. NCA guidance, ESMA publications, and EBA guidelines on recovery and resolution planning may shift expectations.

Material change triggers substantive update outside the annual cycle. Material change includes any of: significant new service line, acquisition or merger, change of home NCA jurisdiction, material change in customer base size or composition, or significant operational restructuring.

Stale wind-down plans fail at activation. Building plan maintenance into the annual compliance calendar — with explicit refresh triggers — produces a plan that works when needed.

Practical takeaways

Wind-down planning is one of MiCA’s quietest but operationally important compliance requirements. Three principles for operators:

Build the plan with the operational team that would execute it. Paper-only compliance plans fail at activation. Bring operations, compliance, technology, customer-facing, finance, and legal teams into the plan design. The cross-functional plan is operationally workable; the compliance-only plan is not.

Use the DORA Article 28 framework to support ICT exit planning. DORA exit planning and CASP wind-down planning overlap substantially. CASPs that have built DORA-compliant exit plans have most of the ICT-exit framework already. Use the overlap rather than building parallel plans.

Maintain the plan as a living document. Annual review, material-change refresh, and operational rehearsal where appropriate. Stale plans are worse than no plans — they create false comfort and operational rigidity that fails at activation.

The wind-down framework is rarely activated but always needed. Building it well during normal operations produces a clean exit when the time comes, whether voluntary, supervisor-directed, or insolvency-protective.

For corrections, updates, or counsel referrals on CASP wind-down planning under Article 84, email [email protected].