ESMA MiCA Q&A: Pre-Funding Client Orders with Client Crypto-Assets

ESMA has published a new MiCA Q&A on pre-funding clients’ orders with clients’ crypto-assets. Although the published item is concise, the topic is significant for crypto-asset service providers (CASPs) operating under the Markets in Crypto-Assets Regulation (MiCA).

The Q&A addresses a specific operational practice: using a client’s crypto-assets to pre-fund that client’s orders. For firms active in execution, custody, or related crypto-asset services, this is not a technical detail. It goes directly to how client assets are handled and how firms structure their order-handling and settlement processes.

What does this regulatory development mean?

In practical terms, “pre-funding” generally refers to arrangements where assets are set aside, transferred, or otherwise used in advance to enable the execution or settlement of a client order. When those assets belong to the client, the legal question becomes especially sensitive: under what conditions may a CASP use or move those assets for that purpose, and how should that practice be reflected in internal controls, client arrangements, and recordkeeping?

Even where MiCA does not change the commercial logic of order execution, it does impose a regulatory framework for the handling of client assets. ESMA’s MiCA Q&A therefore matters because it helps clarify how supervisory expectations may apply to this operational model. Firms should read the Q&A not only as interpretive guidance, but also as a signal that regulators are paying close attention to asset handling practices within CASP services.

More specifically, ESMA considers the pre-funding of client transactions using clients’ crypto-assets to constitute sub-custody. A CASP applying such an arrangement must therefore comply with Articles 70 and 75 MiCA. Pursuant to Article 75(9) MiCA, pre-funding is permissible only where the third party holding the client’s crypto-assets is authorised under Article 59 MiCA to provide custody and administration of crypto-assets on behalf of clients, and the client has been informed of that arrangement. ESMA distinguishes pre-funding from the transfer of crypto-assets to a third party after a transaction has already been executed, solely to settle a specific order: such a transfer does not constitute sub-custody.

Why is this important in practice?

For compliance teams, the immediate question is whether current procedures on order execution and asset flows remain aligned with MiCA expectations. Firms that pre-fund orders using clients’ crypto-assets should review how those arrangements work in practice, which entities control the assets at each stage, and whether the firm’s legal documentation accurately describes the process.

Legal and product teams should also pay attention. If a service model relies on pre-funding, it may be necessary to reconsider how the service is structured, disclosed, and monitored. The new ESMA MiCA Q&A may therefore affect not only compliance manuals, but also onboarding materials, client terms, internal escalation procedures, and control testing.

Closing thoughts

ESMA’s new MiCA Q&A on pre-funding clients’ orders with clients’ crypto-assets is a focused but important development for CASPs. It highlights that the use of client crypto-assets in execution-related processes is a regulatory issue under MiCA, not merely an operational one.

Crypto firms should review the ESMA source carefully and assess whether their internal procedures require adjustment. For businesses already preparing or refining their MiCA compliance framework, this is the right moment to examine pre-funding arrangements in detail.