Complaint-channel source file
Track the competent-authority complaint channel URL, Member State, accepted languages, electronic or written intake route, source URL, retrieval date, and owner responsible for periodic source checks.
MiCA complaints-channel evidence
A source-backed, conservative evidence checklist for CASPs, providers, advisers, insurers, auditors, and internal-risk teams preserving competent-authority complaint-channel records under Regulation (EU) 2023/1114 Article 108.
Informational only. Not legal, regulatory, brokerage, underwriting, or insurance advice.
Complaints-handling by competent authorities: ESMA's Interactive Single Rulebook publishes Regulation (EU) 2023/1114 Article 108 with the title “Complaints-handling by competent authorities”. The public text says competent authorities shall set up procedures that allow clients and other interested parties, including consumer associations, to submit complaints about alleged infringements of the Regulation by offerors, persons seeking admission to trading, issuers of asset-referenced tokens or e-money tokens, or crypto-asset service providers.
Public Article 108 text says complaints are accepted in writing, including electronically, and in an official language of the Member State where the complaint is submitted or another language accepted by that competent authority. It also says complaint-procedure information is made available on each competent authority website, communicated to EBA and ESMA, and ESMA publishes hyperlinks to those competent-authority website sections in the Article 109 crypto-asset register.
This page is a record-preparation checklist. It is not a legal interpretation, complaint-submission instruction, supervisory-response instruction, complaint outcome prediction, provider endorsement, broker recommendation, or assurance about any firm, authority, complainant, alleged infringement, language route, Member State, website link, register entry, or fact pattern.
Track the competent-authority complaint channel URL, Member State, accepted languages, electronic or written intake route, source URL, retrieval date, and owner responsible for periodic source checks.
Preserve complainant identity category, complaint subject matter, alleged-infringement description, involved CASP or issuer name, crypto-asset or service scope, date received, and evidence-source provenance without turning the record into a legal conclusion.
Connect Article 108 complaint-channel records to Article 93 authority routing, Article 94 response files, Article 95 cooperation records where cross-border context exists, and Article 109 register hygiene for ESMA-published complaint-procedure hyperlinks.
Assign owners for triage, response coordination, legal review, complaints-policy updates, incident or conduct remediation, Article 66 client-communication links, and unresolved external-advice questions.
Article 108 is publicly titled “Complaints-handling by competent authorities”. Public text covers procedures for clients and other interested parties, including consumer associations, to submit complaints to competent authorities about alleged infringements of MiCA.
Complaint channels can become an operational-risk and supervisory-response dependency. A useful evidence pack should preserve the authority route, source URL, retrieval date, language-route assumptions, subject matter, evidence owner, and handoffs to Article 93, Article 94, Article 66, and Article 109 records.
No. This page does not choose a competent authority, file a complaint, assess an alleged infringement, predict an outcome, or provide legal/regulatory advice. It helps teams keep source-backed records for qualified legal, regulatory, competent-authority, partner, broker, insurer, auditor, or internal-risk review.