> 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/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-18.md).

# Article 18

|                 |                                                                                 |
| --------------- | ------------------------------------------------------------------------------- |
| **Instrument**  | Regulation (EU) 2023/1114 (MiCA)                                                |
| **Source**      | [EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32023R1114) |
| **Status**      | In force                                                                        |
| **Review rule** | Legal-text changes require human review                                         |

### Application for authorisation

1. Legal persons or other undertakings that intend to [offer to the public](https://www.mica.wtf/definitions/definitions/mica/offer-to-the-public) or seek the admission to trading of [asset-referenced tokens](https://www.mica.wtf/definitions/definitions/mica/asset-referenced-token) shall submit their application for an authorisation referred to in [Article 16](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-16.md) to the [competent authority](https://www.mica.wtf/definitions/definitions/mica/competent-authority) of their [home Member State](https://www.mica.wtf/definitions/definitions/mica/home-member-state).
2. The application referred to in paragraph 1 shall contain all of the following information:
   1. the address of the [applicant issuer](https://www.mica.wtf/definitions/definitions/mica/applicant-issuer);
   2. the [legal entity identifier](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/legal-entity-identifier.md) of the applicant [issuer](https://www.mica.wtf/definitions/definitions/mica/issuer);
   3. the articles of association of the [applicant issuer](https://www.mica.wtf/definitions/definitions/mica/applicant-issuer), where applicable;
   4. a programme of operations, setting out the business model that the applicant [issuer](https://www.mica.wtf/definitions/definitions/mica/issuer) intends to follow;
   5. a legal opinion that the [asset-referenced token](https://www.mica.wtf/definitions/definitions/mica/asset-referenced-token) does not qualify as either of the following:
   6. a [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) excluded from the scope of this Regulation pursuant to [Article 2](/mica/title-i-subject-matter-scope-and-definitions-art.-1-3/article-2.md)(4); or
   7. an [e-money token](https://www.mica.wtf/definitions/definitions/mica/electronic-money-token);
   8. a detailed description of the [applicant issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/applicant-issuer.md)’s governance arrangements as referred to in [Article 34](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-2/article-34.md)(1);
   9. where cooperation arrangements with specific [crypto-asset service providers](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service-provider) exist, a description of their internal control mechanisms and procedures to ensure compliance with the obligations in relation to the prevention of [money laundering](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/money-laundering.md) and [terrorist financing](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/terrorist-financing.md) under Directive (EU) 2015/849;
   10. the identity of the members of the [management body](https://www.mica.wtf/definitions/definitions/mica/management-body) of the applicant [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md);
   11. proof that the persons referred to in point (h) are of sufficiently good repute and possess the appropriate knowledge, skills and experience to manage the [applicant issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/applicant-issuer.md);
   12. proof that any shareholder or member, whether direct or indirect, that has a [qualifying holding](https://www.mica.wtf/definitions/definitions/mica/qualifying-holding) in the applicant [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) is of sufficiently good repute;
   13. a [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) white paper as referred to in [Article 19](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-19.md);
   14. the policies and procedures referred to in [Article 34](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-2/article-34.md)(5), first subparagraph;
   15. a description of the contractual arrangements with the third-party entities as referred to in [Article 34](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-2/article-34.md)(5), second subparagraph;
   16. a description of the applicant issuer’s business continuity policy referred to in [Article 34](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-2/article-34.md)(9);
   17. a description of the internal control mechanisms and risk management procedures referred to in [Article 34](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-2/article-34.md)(10);
   18. a description of the systems and procedures in place to safeguard the availability, authenticity, integrity and confidentiality of data as referred to in [Article 34](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-2/article-34.md)(11);
   19. a description of the applicant issuer’s complaints-handling procedures as referred to in [Article 31](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-2/article-31.md);
   20. where applicable, a list of [host Member States](https://www.mica.wtf/definitions/definitions/mica/host-member-state) where the applicant issuer intends to offer the [asset-referenced token](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/asset-referenced-token.md) to the public or intends to seek admission to trading of the asset-referenced token.
3. Issuers that have already been authorised in respect of one [asset-referenced token](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/asset-referenced-token.md) shall not be required to submit, for the purposes of authorisation in respect of another asset-referenced token, any information that was previously submitted by them to the [competent authority](https://www.mica.wtf/definitions/definitions/mica/competent-authority) where such information would be identical. When submitting the information listed in paragraph 2, the issuer shall expressly confirm that any information not resubmitted is still up-to-date.
4. The [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) shall promptly, and in any event within two working days of receipt of an application pursuant to paragraph 1, acknowledge receipt thereof in writing to the applicant issuer.
5. For the purposes of paragraph 2, points (i) and (j), the applicant issuer of the asset-referenced token shall provide proof of all of the following:
   1. for all members of the [management body](https://www.mica.wtf/definitions/definitions/mica/management-body), the absence of a criminal record in respect of convictions or the absence of penalties imposed under the applicable commercial law, insolvency law and financial services law, or in relation to anti-[money laundering](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/money-laundering.md) and counter-[terrorist financing](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/terrorist-financing.md), to fraud or to professional liability;
   2. that the members of the [management body](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/management-body.md) of the applicant issuer of the asset-referenced token collectively possess the appropriate knowledge, skills and experience to manage the issuer of the asset-referenced token and that those persons are required to commit sufficient time to perform their duties;
   3. for all shareholders and members, whether direct or indirect, that have [qualifying holdings](https://www.mica.wtf/definitions/definitions/mica/qualifying-holding) in the applicant issuer, the absence of a criminal record in respect of convictions and the absence of penalties imposed under the applicable commercial law, insolvency law and financial services law, or in relation to anti-money laundering and counter-terrorist financing, to fraud or to professional liability.
6. EBA, in close cooperation with ESMA and the ECB, shall develop draft regulatory technical standards to further specify the information referred to in paragraph 2.

   EBA shall submit the draft regulatory technical standards referred to in the first subparagraph to the Commission by 30 June 2024.

   Power is delegated to the Commission to supplement this Regulation by adopting the regulatory technical standards referred to in the first subparagraph of this paragraph in accordance with Articles 10 to 14 of Regulation (EU) No 1093/2010.
7. EBA, in close cooperation with ESMA, shall develop draft implementing technical standards to establish standard forms, templates and procedures for the information to be included in the application in order to ensure uniformity across the Union.

   EBA shall submit the draft implementing technical standards referred to in the first subparagraph to the Commission by 30 June 2024.

   Power is conferred on the Commission to adopt the implementing technical standards referred to in the first subparagraph in accordance with Article 15 of Regulation (EU) No 1093/2010.

***

**Level 2 instruments**

* [2025/1125 — ART Authorisation Info](/eu-level/technical-standards/rts/regulatory-technical-standards-information-in-application-art-authorisation.md) — RTS
* [2025/1126 — ART Authorisation Forms](/eu-level/technical-standards/its/implementing-technical-standards-forms-templates-art-authorisation.md) — ITS
* [EBA/RTS/2024 and EBA/ITS/2024 — ART Authorisation Information](/eu-level/technical-standards/final-reports/ts-on-information-for-authorisation-as-issuers-of-arts-under-micar.md) — Final Report (adopted, awaiting OJ publication)
* [Passporting procedure for non-CI ART issuers](/eu-level/q-and-a/eba-qa-7167-passporting-art-issuers.md) — Q\&A

### Related

* [legal entity identifier](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/legal-entity-identifier.md) — definition used in this article
* [asset-referenced token](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/asset-referenced-token.md) — definition used in this article
* [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) — definition used in this article
* [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) — definition used in this article
* [offer to the public](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/offer-to-the-public.md) — definition used in this article
* [terrorist financing](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/terrorist-financing.md) — definition used in this article
* [qualifying holding](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/qualifying-holding.md) — definition used in this article
* [home Member State](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/home-member-state.md) — definition used in this article


---

# 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/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-18.md?ask=<question>&goal=<endgoal>
```

`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.
