MiCA and CySEC supervision
CySEC is the National Competent Authority (NCA) that authorises CASPs in Cyprus. ESMA does not issue the license. That distinction matters because many commercial pages describe ESMA as if it were the licensing body, which is incorrect.
The supervisory roles are split as follows:
- CySEC reviews the application, grants or refuses authorisation, supervises the firm, and receives ongoing notifications and reports.
- ESMA coordinates supervisory convergence at EU level and maintains public registers relevant to MiCA.
- EBA is particularly relevant for prudential and stablecoin-related issues, especially around ARTs and EMTs.
For founders, the practical implication is straightforward: the application strategy must be built for CySEC review, but the legal interpretation should also be consistent with evolving ESMA/EBA technical standards, guidelines, and supervisory expectations. This is one reason why a Cyprus MiCA application should not rely only on local filing mechanics.
AML law, MOKAS and Travel Rule obligations
A CASP authorised in Cyprus remains fully exposed to AML/CFT obligations. The firm must be able to identify clients, assess risk, monitor transactions, escalate unusual activity, and file suspicious transaction reports to MOKAS where required.
The Travel Rule is operationally separate from MiCA but commercially inseparable from it. If your model involves crypto transfers, you should plan for:
- collection and verification of originator and beneficiary data;
- screening and exception handling for incomplete or non-compliant transfers;
- integration with Travel Rule providers using standards such as IVMS101;
- record retention and auditability for regulator review.
One underappreciated issue is interoperability failure. Even where a firm has a Travel Rule vendor, poor data mapping between wallet systems, KYC profiles, and transfer messaging can create unresolved exceptions and manual backlogs. CySEC will care less about the vendor brand than about whether your workflow actually works.
DORA, outsourcing and ICT resilience
DORA is not optional background noise for serious CASPs. In 2026, Cyprus applicants with custody, exchange, or platform exposure should expect scrutiny of ICT risk management, vendor dependency, incident classification, recovery procedures, and testing discipline.
At minimum, a mature Cyprus MiCA application should show:
- ICT asset inventory and system ownership;
- outsourcing register with criticality assessment;
- incident response plan and escalation matrix;
- business continuity and disaster recovery logic;
- access control, logging, and change-management evidence;
- exit strategy for critical ICT providers.
A practical nuance often missed by applicants: if your exchange engine, wallet stack, KYC, and customer support are all outsourced to different vendors, the real risk is not each vendor alone but control fragmentation. Regulators increasingly test whether management can oversee the chain as a whole.