> 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-2578-commingling-client-assets.md). # Commingling client assets | | | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | **Authority** | ESMA | | **Q\&A ID** | ESMA\_QA\_2578 | | **Status** | Answer Published | | **Published** | June 2025 | | **Legal basis** | [Article 70](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-70.md) MiCA | | **Source** | [ESMA Q\&A](https://www.esma.europa.eu/publications-data/questions-answers/2578) | ### Question Some [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers (CASPs) [providing custody and administration of crypto-assets on behalf of clients](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/providing-custody-and-administration-of-crypto-assets-on-behalf-of-clients.md) (as defined in [Article 3](/mica/title-i-subject-matter-scope-and-definitions-art.-1-3/article-3.md)(1)(17) of MiCA) have sister companies that may provide certain services to the CASP's clients, for instance, liquidity or offer lending services. These sister companies may be using the CASP as their custodian and the CASP will hold their crypto-assets within the same wallet(s) to custody other clients' crypto-assets. Under MiCA, is a CASP [providing custody and administration of crypto-assets on behalf of clients](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/providing-custody-and-administration-of-crypto-assets-on-behalf-of-clients.md) allowed to hold clients' crypto-assets within the same wallets as crypto-assets belonging to entities of the same [group](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/group.md)? ### Answer According to [Article 75(7)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-3/article-75.md) of MiCA, CASPs are required to ensure that, on the [distributed ledger](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/distributed-ledger.md), clients’ crypto-assets are held separately from their own crypto-assets. In practice, this means that the wallet addresses used for holding clients’ crypto-assets should be different from the wallet addresses used for holding proprietary crypto-assets. Whilst crypto-assets belonging to other entities belonging to the same [group](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/group.md) should not be regarded as “own crypto-assets” of the CASP for the purpose of [Article 75(7)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-3/article-75.md) of MiCA, the fact that a CASP-custodian commingles its clients’ crypto-assets with crypto-assets belonging to entities of the same group introduces conflicts of interest and potential risks for clients. For instance, due to information asymmetry, the sister company may gain an advantage over other clients by becoming aware of circumstances or incidents that would prompt it to withdraw its crypto-assets from the CASP’s custody. Such circumstances may include, for example, a potential shortfall in crypto-assets or the imminent insolvency of the CASP. As many CASPs use omnibus wallets, a significant withdrawal by a sister company can negatively impact other clients. In accordance with [Article 72](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-2/article-72.md) of MiCA, CASPs shall implement and maintain effective policies and procedures, taking into account the scale, the nature and range of crypto-asset services provided, to identify, prevent, manage and disclose conflicts of interest. In addition, Article 4(1) of Commission Delegated Regulation (EU) …/… of 27 February 2025 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying the requirements for policies and procedures on conflicts of interest for [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers and the details and methodology for the content of disclosures on conflicts of interest provides that “the conflict of interest policies and procedures shall be set out in writing and shall take into account: (a) \[…]; (b) where the [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) is a member of a group, any circumstances which may give rise to a conflict of interest due to the structure and business activities of other entities within the group”. This obligation applies to cases described above where a CASP-custodian holds crypto-assets that belong to entities of the same group (as defined in Article 2, point (11), of Directive 2013/34/EU of the European Parliament and of the Council1). The CASP-custodian should, for instance, avoid commingling clients’ crypto-assets with crypto-assets held on behalf of entities of the same group. However, this would not be in itself sufficient and the CASP-custodian should take all measures to ensure “that the risks of damage to the interests of the [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) provider or its clients will be prevented or appropriately mitigated” (Article 4(7) of the Commission Delegated Regulation on conflicts of interest of CASPs). If the CASP-custodian is not able to do so, it should refrain from providing the service to its sister entities. *** **Source:** [ESMA original document](https://www.esma.europa.eu/publications-data/questions-answers/2578) ### Related * [providing custody and administration of crypto-assets on behalf of clients](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/providing-custody-and-administration-of-crypto-assets-on-behalf-of-clients.md) — defined term used on this page * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) — defined term used on this page * [distributed ledger](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/distributed-ledger.md) — defined term used on this page * [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) — defined term used on this page * [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset.md) — defined term used on this page --- # 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-2578-commingling-client-assets.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.