> 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-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-65.md). # Article 65 | | | | --------------- | ------------------------------------------------------------------------------- | | **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 | ### Cross-border provision of crypto-asset services 1. A [crypto-asset service provider](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service-provider) that intends to provide crypto-asset services in more than one Member State shall submit the following information to the [competent authority](https://www.mica.wtf/definitions/definitions/mica/competent-authority) of the [home Member State](https://www.mica.wtf/definitions/definitions/mica/home-member-state): 1. a list of the Member States in which the [crypto-asset service](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service) provider intends to provide crypto-asset services; 2. the [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) services that the [crypto-asset service provider](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service-provider) intends to provide on a cross-border basis; 3. the starting date of the intended provision of the [crypto-asset services](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service); 4. a list of all other activities provided by the [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) service provider not covered by this Regulation. 2. The [competent authority](https://www.mica.wtf/definitions/definitions/mica/competent-authority) of the [home Member State](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/home-member-state.md) shall, within 10 working days of receipt of the information referred to in paragraph 1, communicate that information to the single points of contact of the [host Member States](https://www.mica.wtf/definitions/definitions/mica/host-member-state), to ESMA and to EBA. 3. The [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) of the Member State that granted authorisation shall inform the [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) concerned of the communication referred to in paragraph 2 without delay. 4. The [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) provider may begin to provide crypto-asset services in a Member State other than its [home Member State](https://www.mica.wtf/definitions/definitions/mica/home-member-state) from the date of receipt of the communication referred to in paragraph 3 or at the latest from the 15th calendar day after having submitted the information referred to in paragraph 1. ### Related * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) — definition used in this article * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service-provider.md) — definition used in this article * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset-service-provider.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 * [home Member State](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/home-member-state.md) — definition used in this article * [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) — definition used in this article * [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset.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-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-65.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.