Authority source record
Keep the public authority page, ESMA competent-authority list reference, retrieval date, Member State, service scope assumptions, and the person responsible for checking updates.
MiCA competent-authority routing evidence
A source-backed, conservative evidence checklist for CASPs mapping Article 93 competent-authority designation, single-contact-point records, EBA/ESMA notification references, and internal ownership before supervisory correspondence or partner diligence.
Informational only. Not legal, regulatory, brokerage, underwriting, or insurance advice.
Competent authorities: Regulation (EU) 2023/1114 Article 93 is titled “Competent authorities”. It states that Member States shall designate the competent authorities responsible for carrying out the functions and duties provided for in the Regulation.
Article 93 also says Member States shall notify those competent authorities to EBA and ESMA. Where more than one competent authority is designated, Member States should determine their respective tasks and designate one competent authority as a single contact point for cross-border administrative cooperation between competent authorities, EBA and ESMA.
The ESMA list of competent authorities notified under MiCA is useful public-source grounding for routing evidence, but CASPs should still verify the current competent-authority source, service scope, jurisdiction, and any counsel-reviewed submission route before relying on an internal contact map.
For operating evidence, treat Article 93 as a routing-control page: source URLs for the relevant authority, single-contact-point notes where applicable, competent-authority correspondence logs, responsibility matrices, Article 62/63/65 filing owners, Article 94 response owners, and Article 109 register-update handoffs.
This page is a source-routing and evidence-control checklist. It is not a legal interpretation, authorisation opinion, filing instruction, supervisory response instruction, provider endorsement, broker recommendation, or assurance about the correct competent authority for any firm, service, Member State, submission, notification, or fact pattern.
Keep the public authority page, ESMA competent-authority list reference, retrieval date, Member State, service scope assumptions, and the person responsible for checking updates.
Where several authorities are involved, document the known contact-point route, task split assumptions, cross-border cooperation handoffs, and unresolved external-advice questions.
Map authorisation applications, completeness questions, cross-border service notifications, register updates, and supervisory correspondence to named internal owners and version logs.
Connect the competent-authority contact map to information-request inventories, document-production owners, suspension-scenario notes, client-impact files, and governance escalation records.
Article 93 is titled “Competent authorities” and covers Member State designation of the competent authorities responsible for MiCA functions and duties, plus notification of those competent authorities to EBA and ESMA.
CASPs need a reliable, source-backed routing map for applications, notifications, supervisory correspondence, register updates, and internal response ownership. A stale authority map can create operational delays even when the underlying evidence pack is strong.
Article 93 helps identify the competent-authority routing and ownership records; Article 94 response files then map information requests, document production, service-suspension scenarios, contract-transfer dependencies, and governance escalation evidence.