> 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-2/article-73.md).

# Article 73

|                 |                                                                                 |
| --------------- | ------------------------------------------------------------------------------- |
| **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                                         |

### Outsourcing

1. [Crypto-asset service providers](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service-provider) that outsource services or activities to third parties for the performance of operational functions shall take all reasonable steps to avoid additional operational risk. They shall remain fully responsible for discharging all of their obligations pursuant to this Title and shall ensure at all times that the following conditions are met:

   1. outsourcing does not result in the delegation of the responsibility of the [crypto-asset service](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service) providers;
   2. outsourcing does not alter the relationship between the [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) service providers and their [clients](https://www.mica.wtf/definitions/definitions/mica/client), nor the obligations of the [crypto-asset service providers](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service-provider) towards their clients;
   3. outsourcing does not alter the conditions for the authorisation of the [crypto-asset service](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service) providers;
   4. third parties involved in the outsourcing cooperate with the [competent authority](https://www.mica.wtf/definitions/definitions/mica/competent-authority) of the [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) service providers’ [home Member State](https://www.mica.wtf/definitions/definitions/mica/home-member-state) and the outsourcing does not prevent the exercise of the supervisory functions of competent authorities, including on-site access to acquire any relevant information needed to fulfil those functions;
   5. [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers retain the expertise and resources necessary for evaluating the quality of the services provided, for supervising the outsourced services effectively and for managing the risks associated with the outsourcing on an ongoing basis;
   6. [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) service providers have direct access to the relevant information of the outsourced services;
   7. [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers ensure that third parties involved in the outsourcing meet the data protection standards of the Union.

   For the purposes of point (g) of the first subparagraph, [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) service providers are responsible for ensuring that the data protection standards are set out in the written agreements referred to in paragraph 3.
2. Crypto-asset service providers shall have a policy on their outsourcing, including on contingency plans and exit strategies, taking into account the scale, the nature and the range of crypto-asset services provided.
3. Crypto-asset service providers shall define in a written agreement their rights and obligations and those of the third parties to which they are outsourcing services or activities. Outsourcing agreements shall give crypto-asset service providers the right to terminate those agreements.
4. Crypto-asset service providers and third parties shall, upon request, make available to the [competent authorities](https://www.mica.wtf/definitions/definitions/mica/competent-authority) and other relevant authorities all information necessary to enable those authorities to assess compliance of the outsourced activities with the requirements of this Title.

### Related

* [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
* [client](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/client.md) — definition used in this article
* [Guidelines on the organisational requirements of crypto-asset service providers](broken://pages/c3IutBAyJNO1K8I9tx7v) — national implementation reference
* [Expectations for future crypto-asset service providers](broken://pages/dG0bSEtBVXxqqweGRvYE) — national implementation reference


---

# 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-2/article-73.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.
