> 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-3/article-82.md).

# Article 82

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

### Providing transfer services for crypto-assets on behalf of clients

1. [Crypto-asset service providers](https://headlesslaw.com/definitions/mica/crypto-asset-service-provider/) [providing transfer services for crypto-assets on behalf of clients](https://headlesslaw.com/definitions/mica/providing-transfer-services-for-crypto-assets-on-behalf-of-clients/) shall conclude an agreement with their clients to specify their duties and their responsibilities. Such agreement shall include at least the following:
   1. the identity of the parties to the agreement;
   2. a description of the modalities of the transfer service provided;
   3. a description of the security systems used by the [crypto-asset service provider](https://headlesslaw.com/definitions/mica/crypto-asset-service-provider/);
   4. fees applied by the [crypto-asset service](https://headlesslaw.com/definitions/mica/crypto-asset-service/) provider;
   5. the applicable law.
2. ESMA, in close cooperation with EBA, shall issue guidelines in accordance with Article 16 of Regulation (EU) No 1095/2010 for [crypto-asset](https://headlesslaw.com/definitions/mica/crypto-asset/) service providers providing transfer services for crypto-assets on behalf of [clients](https://headlesslaw.com/definitions/mica/client/) as regards procedures and policies, including the rights of clients, in the context of transfer services for crypto-assets.

***

**Level 2 instruments**

* [ESMA35-1872330276-1936 — Investor Protection Requirements](/mica-level-2-and-level-3/guidelines/final-report-on-the-guidelines-specifying-certain-requirements-of-mica-on-investor-protection-thir.md) — Guidelines
* [ESMA35-1872330276-2032 — CASP Transfer Services](/mica-level-2-and-level-3/guidelines/guidelines-casp-transfer-services-article-82.md) — Guidelines
* [Transfer: standalone or ancillary](/mica-level-2-and-level-3/q-and-a/esma-qa-2071-crypto-transfer-standalone-vs-ancillary.md) — Q\&A

### Related

* [providing transfer services for crypto-assets on behalf of clients](https://headlesslaw.com/definitions/mica/providing-transfer-services-for-crypto-assets-on-behalf-of-clients/) — definition used in this article
* [crypto-asset service provider](https://headlesslaw.com/definitions/dora/crypto-asset-service-provider/) — definition used in this article
* [crypto-asset service provider](https://headlesslaw.com/definitions/mica/crypto-asset-service-provider/) — definition used in this article
* [crypto-asset service provider](https://headlesslaw.com/definitions/tofr/crypto-asset-service-provider/) — definition used in this article
* [crypto-asset service](https://headlesslaw.com/definitions/mica/crypto-asset-service/) — definition used in this article
* [crypto-asset](https://headlesslaw.com/definitions/mica/crypto-asset/) — definition used in this article
* [crypto-asset](https://headlesslaw.com/definitions/tofr/crypto-asset/) — definition used in this article
* [client](https://headlesslaw.com/definitions/mica/client/) — 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-3/article-82.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.