შინაარსზე გადასვლა
compliance7 ნოემბერი, 2026 · 14 min read

MiCA CASP application requirements: the ICT, custody and continuity sections, and the evidence behind them

What a MiCA CASP application must show on ICT and DORA, custody and business continuity, article by article, and the evidence your software must produce.

Kostiantyn Boiko, Blockchain Engineer

English original

The MiCA CASP application requirements are set by Article 62(2) of Regulation (EU) 2023/1114 (MiCA), which lists 19 items, and by Commission Delegated Regulation (EU) 2025/305, which says what each item must contain. Implementing Regulation (EU) 2025/306 sets the form. Three of those items are mostly engineering work: the technical documentation of ICT systems and security arrangements (point (j)), the segregation of client crypto-assets and funds and the custody policy (points (k) and (m)), and the business continuity plan inside the internal-controls item (point (i)). All three refer to DORA, Regulation (EU) 2022/2554, which has applied to authorised crypto-asset service providers (CASPs) since 17 January 2025.

Timing matters more now. The transitional period in MiCA Article 143(3) ended on 1 July 2026 at the latest, and earlier in member states that shortened it; ESMA’s list shows national periods from six to 18 months. ESMA’s statement of 17 April 2026 says that after that date “any entity providing crypto-asset services to EU clients without a MiCA licence will be in breach of EU law”. A firm applying today has no grandfathering, so the file has to be right first time. The regulator checks completeness within 25 working days and decides within 40 working days of a complete application (Article 63(2) and (9)). Updated information restarts that clock (Implementing Regulation 2025/306, Article 4(2)).

This article covers the ICT, custody and continuity items, plus three items that run on the same systems: complaints, records and market abuse. It does not pick a member state; forms, portals and language rules differ, so check your home regulator’s application page. For each requirement it gives the article, the evidence the software must produce and the gap we check first. It is a technical reading of the rules, not legal advice; counsel should confirm.

Which texts set the MiCA CASP application requirements?

Text What it sets Items it affects
MiCA, Regulation (EU) 2023/1114 The Article 62(2) list; organisational and custody rules in Articles 68 to 76; market abuse in Article 92; transition in Article 143 All
Delegated Regulation (EU) 2025/305 The content of each application item All
Implementing Regulation (EU) 2025/306 The application form and how changes are notified All
DORA, Regulation (EU) 2022/2554 ICT risk management, incidents, testing, ICT third parties ICT, continuity
Delegated Regulation (EU) 2024/1774 Detailed ICT controls: key management, logging, access control ICT, custody
Delegated Regulation (EU) 2025/301 Content and time limits of major-incident reports ICT
Implementing Regulation (EU) 2024/2956 Templates for the register of ICT third-party arrangements ICT
Delegated Regulation (EU) 2025/299 Business continuity policy, plans and annual tests for CASPs Continuity
Delegated Regulation (EU) 2025/1140 Records of services, orders and transactions Records
Delegated Regulation (EU) 2025/294 Complaints handling Complaints
Delegated Regulation (EU) 2025/885 Market abuse arrangements and suspicious order reports Trading platforms

Does DORA apply to a crypto firm before it is authorised?

DORA Article 2(1)(f) covers “crypto-asset service providers as authorised under” MiCA, and DORA has applied since 17 January 2025 (Article 64). The obligations attach to an authorised firm, but the application already has to describe “the arrangements and deployed ICT and human resources established to comply with” DORA (2025/305, Article 9(a)). MiCA Article 68(7) and (8) also write DORA into a CASP’s organisational rules. ESMA’s peer review of a Maltese CASP authorisation, published on 10 July 2025, recommended that competent authorities review ICT systems, including business continuity, “in light of DORA requirements” before granting authorisation. It asked for higher scrutiny of the most critical functions, naming custody.

CASPs are not among the entities listed in DORA Article 16(1) for the simplified ICT risk framework. On our reading, the full Articles 5 to 15 apply, together with Title II of Delegated Regulation 2024/1774, scaled by the proportionality principle in Article 4. Some duties are lighter for microenterprises, for example the cyber-attack and switchover test scenarios (Article 11(6)), redundant capacity (Article 12(4)) and the testing programme (Article 24(1)). Counsel should confirm whether you qualify.

What are the MiCA CASP ICT requirements?

Article 9 of 2025/305 asks for four things:

  1. Technical documentation of the ICT systems, any DLT infrastructure relied on and the security arrangements. It should show the ICT risk management framework and how your systems protect the security, integrity, availability, authenticity and confidentiality of data under DORA and the GDPR. It should identify each ICT service that supports a critical or important function, in-house or third-party, with the provider’s identity and location and a copy of the contract. It should also show how those contracts meet MiCA Article 73 and DORA Chapter V, and describe your security and incident management (Article 9(a)).
  2. A third-party cybersecurity audit, if available (Article 9(b)). Ideally it covers organisational and physical security and the secure development lifecycle; vulnerability scans and network assessments; configuration reviews; penetration tests in black-box, grey-box and white-box phases; and a source-code review of any smart contracts you use or develop.
  3. A description of any audits of the ICT systems already carried out (Article 9(c)).
  4. The same information in non-technical language (Article 9(d)).

The DORA controls behind that documentation are specific, and each produces a record an assessor can ask for:

  • Access. Least privilege, segregation of duties, shared and generic accounts kept to a minimum, strong authentication for privileged and remote access. Access rights to systems supporting critical or important functions are reviewed at least every six months (2024/1774, Article 21).
  • Logging. Defined events and retention periods, logs protected against tampering and deletion, detection of logging failures and clocks synchronised to a reliable time source (2024/1774, Article 12).
  • Keys. A policy for the whole key lifecycle, from generation to destruction, controls against loss and unauthorised access, and a method to replace lost or compromised keys (2024/1774, Article 7).
  • Change. Every change to software, hardware or security parameters recorded, tested, approved and verified (DORA Article 9(4)(e)).
  • Incidents. Every ICT-related incident recorded and classified (Article 17). A major incident needs an initial notification within four hours of classification and no later than 24 hours after you become aware of it, an intermediate report within 72 hours of the initial notification and a final report within one month of the latest intermediate report (2025/301, Article 5).
  • Testing. A testing programme, run by independent parties, with appropriate tests at least yearly on all systems supporting critical or important functions (DORA Article 24(4) and (6)).
  • Third parties. A register of information on all ICT contracts in the templates of Implementing Regulation 2024/2956, a yearly report to the regulator, exit strategies for critical services, and contracts with service levels and audit and access rights for you and the regulator (DORA Articles 28(3), 28(8) and 30(3)).

ESMA’s supervisory briefing of 31 January 2025 tells authorities to pay particular attention to outsourced ICT infrastructure and to treat key management as a function that needs special scrutiny. It also says outsourcing to a jurisdiction where the authority cannot obtain information is not compatible with MiCA Article 73(1)(d).

What are the MiCA custody requirements in the application?

MiCA Article 70 requires arrangements that protect clients’ ownership rights and stop client crypto-assets being used for your own account. Client funds other than e-money tokens go to a credit institution or central bank by the end of the next business day, in an account kept apart from your own (Article 70(3)); e-money, payment and credit institutions are exempt from that paragraph (Article 70(5)).

Article 75 adds the custody rules. You need a client agreement that describes, among other things, the client’s authentication and your security systems. You also need a register of positions per client, and a custody policy that minimises the risk of loss from “fraud, cyber threats or negligence”, with a summary available on request. Clients get a statement of position at least every three months and on request, and there must be procedures to return their assets. Client holdings must be segregated from yours on the distributed ledger, legally and operationally. Liability for an attributable loss is capped at the market value of the lost asset at the time of loss (Article 75(8)). Custody can be delegated only to CASPs authorised under Article 59 (Article 75(9)).

Delegated Regulation 2025/305 turns this into application content. Article 10 asks how the wallets holding client crypto-assets differ from your own, for “a detailed description of the approval system for cryptographic keys and safeguarding of cryptographic keys, including multi-signature wallets”, and how an omnibus wallet’s contents are split between clients. Article 12 asks for the custody policy with the operational and ICT risks you identified, the systems that return assets, how assets and the means of access are identified and the measures that minimise loss.

MiCA does not prescribe a signing technology; MPC vs multisig covers the trade-offs an assessor will ask about. Article 75 does not require a public Merkle-tree proof either. The evidence is the per-client register reconciled with balances on the ledger, which how to implement proof of reserves covers. Two ESMA points apply to every custodian. The April 2026 statement repeats that custody cannot be outsourced to entities that are not themselves authorised as CASPs. The Malta peer review says authorities should check that an applicant can “efficiently and effectively block malicious transactions if needed”.

What must the business continuity section show?

MiCA Article 68(7) requires a business continuity policy that includes the ICT business continuity plans and ICT response and recovery plans of DORA Articles 11 and 12. Article 5 of 2025/305 asks the applicant to prove the plan is appropriate and periodically tested. It also asks how continuity holds when a third party supporting a critical or important function degrades or fails, and what happens if a key person dies.

Delegated Regulation 2025/299 sets the content. The management body endorses the policy and reviews it at least annually (Article 2). The plans cover scenarios such as the loss of staff, suppliers or data centres and the loss or alteration of critical data. They set recovery deadlines, recovery point objectives and a maximum time to resume services, cover relocation to a backup site and client communications (Article 4). When a permissionless distributed ledger you use is disrupted, clients are told when services should resume and what the risks are to their funds and crypto-assets (Article 4(3)). Plans are tested annually (Article 5).

DORA adds the engineering detail: plans tested at least yearly and after substantive changes, with cyber-attack and switchover scenarios for firms other than microenterprises (Article 11(6)); restore tests run periodically, onto systems physically and logically segregated from the source (Article 12(2) and (3)); and redundant ICT capacity (Article 12(4)). For firms that were not authorised in time, ESMA’s April 2026 statement expected wind-down plans that are “operational, credible, and immediately executable”, including transfers of client crypto-assets to an authorised CASP or a self-hosted wallet. Returning every client’s assets on request is also what MiCA Article 75(6) and Article 12(b)(iv) of 2025/305 ask an applicant to describe, so rehearse it before you file.

Complaints, records and market abuse

These are separate items in the application, but they draw on the same databases.

  • Complaints. MiCA Article 71 requires free complaints, a complaints template for clients and a record of every complaint and the measures taken. Delegated Regulation 2025/294 requires a secure electronic system for that record and a decision within two months of receipt (Articles 1(2) and 6(2)). The procedure description and the template are published on your website (Article 1(3)). It also requires ongoing analysis of processing times, missed deadlines, topic categories and outcomes (Article 8). The application describes the resources, timelines and record-keeping (2025/305, Article 11).
  • Records. Records of all services, orders and transactions are kept for five years, or up to seven if the regulator asks (MiCA Article 68(9)). Delegated Regulation 2025/1140 requires that the regulator can reconstruct each key stage of each order or transaction, that corrections and the prior content are visible, and that records cannot be manipulated or altered (Article 2(1)).
  • Market abuse. A trading platform’s systems must be able to prevent or detect market abuse (Article 76(7)(g)), and order data is kept for at least five years (Article 76(15)). Under Delegated Regulation 2025/885, monitoring covers every order placed, modified, cancelled or rejected, produces alerts, includes human analysis, and uses ICT systems that can replay and analyse order book data after the event (Article 3). Arrangements are reviewed at least annually (Article 2(3)), and a suspicious order report goes to the regulator without delay once reasonable suspicion forms (Article 6).
  • Travel Rule. The AML item asks how your controls meet Regulation (EU) 2023/1113, the Travel Rule regulation (2025/305, Article 6(c)). The transfer data comes from the same withdrawal and deposit records; when the counterparty cannot receive Travel Rule data covers the hardest case.

Requirement, article, evidence, typical gap

The first two columns are the legal requirement, paraphrased, and its citation. The evidence column is what we recommend the software can produce on request. The last column is the gap we check first when reviewing a file; it is our engineering judgement, not a regulator finding.

Requirement Article Evidence the software produces Typical gap
ICT documentation and plain-language summary MiCA 62(2)(j); 2025/305 Art. 9(a), (d) Architecture and data-flow diagrams of the deployment you will run; asset inventory; hosting locations Diagrams show a vendor reference design, not your deployment
Least privilege, strong authentication, access reviews DORA 9(4)(c)–(d); 2024/1774 Art. 21 Role matrix exported from the system; 2FA enforced for staff; six-monthly review records Shared admin accounts; vendor accounts with standing access
Logs protected against tampering 2024/1774 Art. 12; 2025/1140 Art. 2(1) Audit log of operator actions and money movements with synchronised timestamps; export Admins can edit or delete log entries; no alert when logging stops
Change management DORA 9(4)(e) Releases built from version control with approval, test result and rollback record Fixes applied by hand on production
Key approval and safeguarding 2025/305 Art. 10(1)(b); 2024/1774 Art. 7 Key ceremony record; M-of-N policy held as versioned configuration; approval log per withdrawal; key replacement procedure The policy says 2-of-3 but one operator can still send a withdrawal
Client wallets apart from own; omnibus split per client MiCA 70(1), 75(7); 2025/305 Art. 10(1)(a), (c) Wallet register labelled client, own and fee; per-client ledger positions Fee or market-maker balances in client wallets
Register of positions and reconciliation MiCA 75(2), (4) Every movement linked to a client instruction; daily ledger-to-chain reconciliation with a break log Reconciliation only against the platform’s own database
Statements and return of assets MiCA 75(5), (6); 2025/305 Art. 12(b)(iv) Quarterly statements with balance, value and transfers; tested mass-withdrawal and wind-down runbook Statements without value or transfers; return never rehearsed
Client funds with a credit institution or central bank by the next business day MiCA 70(3); 2025/305 Art. 10(1)(d) Fiat ledger reconciled to the safeguarding account, with receipt and placement times Balances left at a payment processor counted as safeguarded
Incident register and reporting clock DORA 17, 19; 2025/301 Art. 5 Register with detection, classification and notification timestamps; drill record No recorded classification time, so the four-hour clock cannot be shown
Testing programme DORA 24(4), (6), 25; 2025/305 Art. 9(b) Yearly test plan; penetration-test reports covering admin, custody and APIs; scans; remediation tracker Only the public website tested; findings still open
ICT third-party register, contracts, exit DORA 28(3), 28(8), 30(3); ITS 2024/2956; MiCA 73 Register covering hosting, KYC, transaction monitoring, node or RPC providers and software vendor; contracts with audit rights; exit plan Node providers and the software vendor missing from the register
Continuity plans with recovery objectives, tested annually MiCA 68(7); DORA 11(6), 12; 2025/299 Art. 4–5 Recovery time and point objectives per function; timed restore drill on separate hardware; switchover test; outage notice templates Backups taken but never restored, or restored onto the same host
Records that cannot be altered MiCA 68(9); 2025/1140 Art. 2 Retention settings; reconstruction of each order and transaction stage; corrections kept with prior values Records overwritten on correction or deleted with log rotation
Complaints record MiCA 71; 2025/294 Art. 1, 6, 8 Complaints register with receipt, admissibility, decision date, category and processing-time reports Complaints mixed into support tickets without categories or deadlines
Market abuse detection (trading platforms) MiCA 76(7)(g), 76(15), 92; 2025/885 Art. 2, 3, 6 Full order event feed kept five years; surveillance alerts, case notes, report log Only fills exported, so cancelled and modified orders cannot be replayed
Ability to stop malicious transactions ESMA peer review, July 2025 Withdrawal pause per asset, whitelists and delays; drill record The control exists but needs the vendor to operate it

What should an applicant do now?

  1. List your critical or important functions and map each one to systems and providers. Build the register of information from that list, not from the purchase ledger.
  2. Produce evidence from the system you will run: a timed restore on separate hardware, an access review, a log export, approval logs for real withdrawals and a week of reconciliation reports.
  3. Book an independent penetration test that covers the admin console, custody and the APIs as well as the website, and close the findings before you file.
  4. Write the custody policy from the configuration. Export the approval policy and compare it line by line with the document.
  5. Run the incident clock as a drill: detection, classification, then an initial notification inside four hours.
  6. Rehearse the return of client assets and keep the result with the wind-down plan.

MiCA CASP application FAQ

Does DORA apply to crypto-asset service providers?

Yes. DORA Article 2(1)(f) names CASPs authorised under MiCA, and DORA has applied since 17 January 2025. CASPs are not on the Article 16 list for the simplified framework, and the application itself must describe how you comply.

What ICT information does a MiCA CASP application need?

Article 9 of Delegated Regulation 2025/305 asks for technical documentation of the ICT systems and security arrangements, how you comply with DORA, the ICT services that support critical or important functions and their providers and contracts, incident management, any third-party cybersecurity audit and a non-technical summary.

Can a CASP outsource custody or key management to its software vendor?

Custody can be delegated only to an authorised CASP (MiCA Article 75(9)). ESMA’s 2025 briefing lists key management among functions that need special scrutiny when outsourced. If a vendor would hold or operate your keys, have counsel assess the arrangement before you describe it in the file.

How long does MiCA CASP authorisation take?

The authority checks completeness within 25 working days and decides within 40 working days of a complete application (Article 63(2) and (9)). Missing information and updates to the file move the start of that period, so the real time depends on how complete the file is.

Does licence-ready software make a CASP application compliant?

No. Software provides controls and the records that evidence them. Authorisation depends on the company, its people, its policies and how it operates, and the competent authority decides.

How BitPolaris helps

BitPolaris builds the exchange, wallet and custody software that has run in production at the reference exchange since 2024. The exchange’s operations console has deny-by-default roles (superadmin, admin and support), a second approver for sensitive actions and an audit log of who changed what and when for every settings change and money action, exportable for auditors. The support console holds live chat and a ticket queue with status and assignment; map your complaints procedure onto it and check that admissibility, category and decision date are recorded. The exchange captures Travel Rule data on deposits and withdrawals with an export for your Travel Rule provider. The matching engine has self-trade prevention, and reports separate market-maker from organic volume.

Custody is self-hosted only, so key generation, storage and approvals stay inside your perimeter. It has hot, warm, cold, fee and deposit wallets, with fee wallets, market-maker float and Earn treasury kept apart from customer funds. Approvals are M-of-N per asset and amount band, each a 2FA event by a named officer, and new withdrawal addresses wait 24 hours by default. Policy changes are versioned with who, what and when. The custody panel cannot withdraw, generate addresses or rotate keys. A reserve monitor compares on-chain balances for every custody address with the ledger and reports a check it cannot complete as unknown, and proof-of-reserves exports are signed. Backups are encrypted and sent off-site every night, and a restore drill on new hardware is part of every delivery.

The deployment model changes your register of information. On our cloud model the exchange runs on dedicated servers at Hetzner in Falkenstein or Helsinki. Its keys are encrypted inside the instance, our access is operational and logged, and exit is 90 days’ notice with a full data export. On that model we provide the ICT services that run your exchange, and its keys sit in an instance we operate; counsel should assess that against MiCA Article 73 and the ESMA briefing. On the self-hosted model we have no standing access, and support uses time-limited credentials you issue. List us in the register either way; whether the service supports a critical or important function is your assessment.

List prices, EUR excluding VAT, as published on 7 November 2026: custody self-hosted €15,400 one-time (€14,000 with the exchange) plus 20% a year for updates and support; exchange self-hosted €24,500 plus €4,900 a year; standby site €4,200 and HSM integration €5,250, both one-time. The Licence Technical Pack writes the technical sections: Lite €1,250 one-time for platform customers; Pro €6,300 one-time, mapped to MiCA with DORA, with an ICT third-party register and a recorded restore drill; Regulator Q&A €1,450 a month while the file is under review. A first draft takes two weeks from the scoping call. Background: what regulators ask for.

We are not a law firm and do not file applications; your counsel does. The pack is not an audit or a penetration test, so it does not replace the independent testing DORA requires. Market-abuse surveillance and Travel Rule messaging are not listed on our product pages; contract them separately. Installing our software does not make anyone compliant or authorised.

Preparing a MiCA CASP application? Keep keys and approvals inside your perimeter with self-hosted custody, and see every licence, module and Licence Technical Pack price on the pricing page.

Licence Technical Pack

Sources

  1. Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA), Articles 62, 63, 68, 70, 71, 73, 75, 76, 92 and 143, EUR-Lex, read 7 November 2026
  2. Commission Delegated Regulation (EU) 2025/305, information to be included in an application for authorisation as a CASP, Articles 5, 6, 9, 10, 11, 12 and 13, EUR-Lex, read 7 November 2026
  3. Commission Implementing Regulation (EU) 2025/306, standard forms and templates for the CASP application, Article 4, EUR-Lex, read 7 November 2026
  4. Regulation (EU) 2022/2554 on digital operational resilience (DORA), Articles 2, 4, 9, 11, 12, 16, 17, 19, 24, 25, 28, 30 and 64, EUR-Lex, read 7 November 2026
  5. Commission Delegated Regulation (EU) 2024/1774, ICT risk management tools, methods, processes and policies, Articles 7, 12 and 21, EUR-Lex, read 7 November 2026
  6. Commission Delegated Regulation (EU) 2025/301, content and time limits for major ICT-related incident reports, Article 5, EUR-Lex, read 7 November 2026
  7. Commission Implementing Regulation (EU) 2024/2956, templates for the register of information, EUR-Lex, read 7 November 2026
  8. Commission Delegated Regulation (EU) 2025/299, continuity and regularity in the performance of crypto-asset services, Articles 2 to 5, EUR-Lex, read 7 November 2026
  9. Commission Delegated Regulation (EU) 2025/1140, records of crypto-asset services, activities, orders and transactions, Article 2, EUR-Lex, read 7 November 2026
  10. Commission Delegated Regulation (EU) 2025/294, complaints handling by CASPs, Articles 1, 6 and 8, EUR-Lex, read 7 November 2026
  11. Commission Delegated Regulation (EU) 2025/885, arrangements to prevent, detect and report market abuse, Articles 2, 3 and 6, EUR-Lex, read 7 November 2026
  12. ESMA, Statement on the end of transitional periods under MiCA, ESMA75-113276571-1679, 17 April 2026, read 7 November 2026
  13. ESMA, List of grandfathering periods decided by member states under MiCA, read 7 November 2026
  14. ESMA, Supervisory briefing on the authorisation of CASPs under MiCA, ESMA75-453128700-1263, 31 January 2025, read 7 November 2026
  15. ESMA, Fast-track peer review on a CASP authorisation and supervision in Malta, ESMA42-2004696504-8164, and press release, 10 July 2025, read 7 November 2026

დაჯავშნეთ 30-წუთიანი შეფასების ზარი

Crypto exchange, payments, wallet, custody and token launch software, already running in production. Run it on your own servers, license the source code, or let us host it under your brand.