> 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-2088-notification-tied-agents.md).

# Tied agents: notification

|                 |                                                                                                                                               |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authority**   | ESMA                                                                                                                                          |
| **Q\&A ID**     | ESMA\_QA\_2088                                                                                                                                |
| **Status**      | Answer Published                                                                                                                              |
| **Published**   | September 2024                                                                                                                                |
| **Legal basis** | [Article 60](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-60.md) MiCA |
| **Source**      | [ESMA Q\&A](https://www.esma.europa.eu/publications-data/questions-answers/2088)                                                              |

### Question

Must [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers (CASPs) notify competent authorities when appointing tied agents under MiCA?

***

### Answer

A [credit institution](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/crr/credit-institution.md) can provide any [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) services on the basis of an Article 60 notification.

A [credit institution](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/crr/credit-institution.md) however needs to submit a notification to its [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md), including all the information listed in Article 60(7) (e.g. a program of operations, internal control mechanisms, procedures for segregation, custody, AML and ICT). In practice, if a credit institution holds no license for a type of service (e.g. custody), it may have difficulties to provide the information required in relation to this service.

Also note that recital 78 states that “the notification procedure for credit institutions intending to provide [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) services under MiCA should be without prejudice to the provisions of national law transposing Directive 2013/36/EU (CRD) that set out procedures for the authorisation of credit institutions to provide the services listed in Annex I to that Directive.”

National implementation of CRD differs across Member States, with some banking licenses granted being more general and others more narrow – any notification under Article 60 will have to be in line with national rules transposing CRD.

***

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

### Related

* [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) — defined term used on this page
* [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) — defined term used on this page
* [credit institution](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/crr/credit-institution.md) — defined term used on this page
* [credit institution](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/credit-institution.md) — defined term used on this page
* [credit institution](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/credit-institution.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-2088-notification-tied-agents.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.