> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/eu-level/technical-standards/its/implementing-technical-standards-standard-forms-templates-procedures-application-authorisation-crypt.md). # 2025/306 — CASP Authorisation Forms | | | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Instrument** | Commission Implementing Regulation (EU) 2025/306 (ITS) | | **Drafted by** | ESMA (in close cooperation with EBA) | | **Legal basis** | [Article 62(6) MiCA](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-62.md) | | **Status** | In force | | **In force** | 20 April 2025 (twentieth day after OJ publication on 31 March 2025) | | **Source** | [EUR-Lex](https://eur-lex.europa.eu/eli/reg_impl/2025/306/oj/eng) | ### Recitals 1. To facilitate communication between legal persons or other undertakings seeking authorisation as a [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers in accordance with [Article 62](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-62.md) of [Regulation (EU) 2023/1114](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md) (‘applicants’) and competent authorities, competent authorities should designate a contact point specifically for receiving the applications for authorisation as a [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) and should publish the information on the contact point on their website. 2. The information submitted by the applicant should be true, accurate, complete and up-to-date from the moment of submission of the application until the moment of granting the authorisation. Given that some information may only refer to the future, any future date included in the information should be specifically identified in the application. 3. To ensure a prompt and timely handling of applications for the authorisation of [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) service providers, competent authorities should confirm the receipt of the application by sending electronically, on paper, or in both forms, an acknowledgement of receipt to the applicant. That acknowledgement of receipt should include the contact details of the persons or function in charge of handling the application for authorisation. 4. To allow competent authorities to base their assessment of the application for authorisation on accurate information, applicants should communicate to competent authorities any changes to the information provided in the application for authorisation, without undue delay. In that case, the time limits for the assessment of the application laid down in [Article 63(9)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-63.md) of Regulation (EU) 2023/1114 should start from the date on which the updated information is received by the [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md). 5. Competent authorities should be able to request additional information from the applicant during the assessment in accordance with the criteria and timelines laid down in [Article 63(12)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-63.md) of Regulation (EU) 2023/1114. 6. This Regulation is based on the draft implementing technical standards submitted to the Commission by the European Securities and Markets Authority, in close cooperation with the European Banking Authority. 7. The European Securities and Markets Authority has conducted open public consultations on the draft implementing technical standards on which this Regulation is based, analysed the potential related costs and benefits and requested the advice of the Securities and Markets Stakeholder [Group](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/group.md) established in accordance with Article 37 of Regulation (EU) No 1095/2010 of the European Parliament and of the Council, ### Article 1 — Designation of a contact point Competent authorities shall designate a contact point for receiving the applications for authorisation as a [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) in accordance with [Article 62](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-62.md) of Regulation (EU) 2023/1114. Competent authorities shall keep the contact details of the designated contact point up-to-date and shall make those contact details public on their websites. ### Article 2 — Submission of the application for authorisation 1. A legal person or other undertaking seeking authorisation as a [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) provider in accordance with [Article 62](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-62.md) of Regulation (EU) 2023/1114 (‘applicant’) shall submit to the [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) its application for authorisation by filling in the form set out in the Annex of this Regulation. 2. The legal person or other undertaking shall submit the application in a manner which enables storage of information so that it is accessible for future reference and that allows the reproduction of the information stored. ### Article 3 — Receipt of the application for authorisation and acknowledgement of receipt Competent authorities shall send electronically, on paper, or in both forms, an acknowledgement of receipt to the applicant. That acknowledgement of receipt shall include the contact details of the department, function or staff member of the competent authority handling the application. ### Article 4 — Notification of changes 1. The applicant shall notify the competent authority of any changes to the information provided in the application for authorisation without undue delay. The applicant shall provide the updated information by using the form set out in the Annex. 2. Where the applicant provides updated information in accordance with paragraph 1, the time limit laid down in [Article 63(9)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-63.md) of Regulation (EU) 2023/1114 shall start from the date of receipt of that updated information by the competent authority. 3. [Crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) service providers shall notify the competent authority of any changes to the information based on which the authorisation was granted. ### Article 5 — Communication of the decision Competent authorities shall notify the applicant of their decision granting or refusing the authorisation, as referred to in [Article 63(9)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-63.md) of Regulation (EU) 2023/1114, in paper form, by electronic means or both. ### Article 6 — Entry into force This Regulation shall enter into force on the twentieth day following that of its publication in the *Official Journal of the European Union*. ### Annex — Application form for authorisation as a crypto-asset service provider In accordance with Article 2 and 4 of Commission Implementing Regulation (EU) 2025/306 of 31 October 2024 laying down implementing technical standards for the application of Regulation (EU) 2023/1114 with regard to standard forms, templates and procedures for the information to be included in the application for authorisation as a crypto-asset service provider. Reference number *(to be completed by the competent authority):*\ Date:\ FROM\ Name of the applicant:\ Address of the applicant / applicant’s registered office:\ \&#xNAN;*Contact details of the designated contact person*\ Name:\ Telephone:\ Email:\ TO\ Member State (if applicable):\ Competent authority:\ Address:\ \&#xNAN;*Contact details of the designated contact point*\ Name:\ Telephone:\ Email:\ We, \[*insert applicant’s name*] declare that the submitted information is true, accurate, complete, up to date, and not misleading. If some information relates only to a future date, it is explicitly identified in the application and we undertake to notify the authority in writing without delay if any such information should turn out to be inaccurate, incomplete or misleading. Further, we undertake to inform the competent authority of any change concerning the information provided in this form.\ \&#xNAN;*Person in charge of preparing the application*\ Name:\ Status/position:\ Telephone:\ Email:\ REQUIRED INFORMATION\ General information according to Article 1 of Commission Delegated Regulation (EU) 2025/305\ ...\ Programme of operations according to Article 2 of Delegated Regulation (EU) 2025/305\ ...\ \&#xNAN;*Prudential requirements*\ ...\ Please insert the information referred to in Article 3 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Information about governance arrangements and internal control mechanisms*\ ...\ Please insert the information referred to in Article 4 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Business continuity*\ ...\ Please insert the information referred to in Article 5 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Detection and prevention of* [*money laundering*](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/money-laundering.md) *and terrorist financing*\ ...\ Please insert the information referred to in Article 6 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Identity and proof of good repute, knowledge, skills, and experience and of sufficient time commitment of the members of the management body*\ ...\ Please insert the information referred to in Article 7 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Information relating to shareholders or members with qualifying holdings*\ ...\ Please insert the information referred to in Article 8 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*ICT systems and related security arrangements*\ ...\ Please insert the information referred to in Article 9 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Segregation of clients’ crypto-assets and funds*\ ...\ Please insert the information referred to in Article 10 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Complaints-handling*\ ...\ Please insert the information referred to in Article 11 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Custody and administration policy*\ ...\ Please insert the information referred to in Article 12 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Operating rules of the trading platform and market abuse detection*\ ...\ Please insert the information referred to in Article 13 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Exchange of crypto-assets for* [*funds*](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/funds.md) *or other crypto-assets*\ ...\ Please insert the information referred to in Article 14 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Execution policy*\ ...\ Please insert the information referred to in Article 15 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Provision of advice or portfolio management on crypto-assets*\ ...\ Please insert the information referred to in Article 16 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \&#xNAN;*Transfer services*\ ...\ Please insert the information referred to in Article 17 of Delegated Regulation (EU) 2025/305, by setting out that information here or making reference to the relevant sections of the application.\ \[*signature of legal representative]* ### Related * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) — defined term used on this page * [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) — defined term used on this page * [money laundering](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/money-laundering.md) — defined term used on this page * [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) — defined term used on this page * [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset.md) — defined term used on this page --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.mica.wtf/eu-level/technical-standards/its/implementing-technical-standards-standard-forms-templates-procedures-application-authorisation-crypt.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.