> 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/q-and-a/esma-qa-2608-pre-funding-clients-orders-clients-crypto-assets.md).

# Pre-funding clients’ orders with clients’ crypto-assets

|                 |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authority**   | ESMA                                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Q\&A ID**     | ESMA\_QA\_2608                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Status**      | Answer Published                                                                                                                                                                                                                                                                                                                                                                                                                    |
| **Published**   | 9 July 2025                                                                                                                                                                                                                                                                                                                                                                                                                         |
| **Legal basis** | [Article 75(9)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-3/article-75.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md); [Article 59](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-59.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md) |
| **Source**      | [ESMA Q\&A](https://www.esma.europa.eu/publications-data/questions-answers/2608)                                                                                                                                                                                                                                                                                                                                                    |

### Question

Does the Markets in Crypto-Assets Regulation (MiCA) allows crypto-asset service providers (CASPs) to use clients’ crypto-assets for pre-funding client orders?

***

### Answer

Pre-funding client transactions using clients’ crypto-assets qualifies as the sub-custody of client’s crypto-assets. As such, CASPs pre-funding clients’ transactions with clients’ crypto-assets must adhere to the requirements outlined in [Articles 70](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-70.md) (Safekeeping of clients’ crypto-assets and funds) and 75 (Providing custody and administration of crypto-assets on behalf of clients) of MiCA. In accordance with [Article 75(9)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-3/article-75.md) of MiCA, the pre-funding of clients’ transactions using clients’ crypto-assets may thus only be done where the third party holding the clients’ crypto-assets is a CASP authorised in accordance with [Article 59](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-59.md) of MiCA and clients have been informed accordingly. Consequently, the pre-funding of client transactions using client’s crypto-assets is only permissible under MiCA where the third-party holding the client’s crypto-assets is authorised to provide the crypto-asset service of custody and administration of crypto-assets on behalf of clients in accordance with MiCA.

Where clients’ crypto-assets are sent to a third party for the settlement of a transaction that has already been executed for the specific purpose of settling a specific order, this should not be seen as sub-custody.

***

**Source:** [ESMA original document](https://www.esma.europa.eu/publications-data/questions-answers/2608)


---

# 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/q-and-a/esma-qa-2608-pre-funding-clients-orders-clients-crypto-assets.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.
