> 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/eba-qa-7078-emt-issuer-aml-kyc-scope.md).

# EMT issuers: AML/KYC obligations

|                 |                                                                                        |
| --------------- | -------------------------------------------------------------------------------------- |
| **Authority**   | EBA                                                                                    |
| **Q\&A ID**     | EBA\_QA\_2024\_7078                                                                    |
| **Status**      | Answer Published                                                                       |
| **Published**   | 22 May 2026                                                                            |
| **Legal basis** | [Article 48(2)](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-48.md) MiCA |
| **Source**      | [EBA Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7078)  |

### Question

To what extent should [electronic money](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/emd2/electronic-money.md) institutions (EMIs) that issue e-money tokens (EMTs) under MiCAR comply with the obligations in relation to anti-[money laundering](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/money-laundering.md) and [terrorist financing](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/terrorist-financing.md) under Directive 2015/849/EU (as amended, AMLD5)? More specifically, should holders of EMTs be considered as clients of the EMI within the meaning of AMLD5, so that the relevant KYC requirements apply on an ongoing basis in respect of holders of EMTs (not only at the time of issuing but also following trading on the secondary market)?

### Background

MiCAR does not specifically address the applicability of AML regulations to issuers of EMTs. If an [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) of EMTs is required to know the identity of the current holder of the EMTs on an ongoing basis, this has implications for their tradability on the secondary market. If the issuer needs to know the identity of the holder of the EMT on a continuous basis (including customer due diligence in respect of any successive new holders) and continuous monitoring needs to take place, it will need to be involved in any transfer of the EMTs following the initial issue. It is important to create clarity on this to the market.

As a result of MICAR, the scope of AMLD5 has been enlarged based on Article 38 of the revised Regulation 2023/1113/EU (TFR). A new category of obliged entities has been added to AMLD5, namely [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers (CASPs). However, distribution of EMTs can also take place without the involvement of a regulated CASP, as in the case of peer-to-peer transactions or exchanges that operate outside the scope of MiCAR regulation. The position of the CASP should further be distinguished from the position of the EMI or [credit institution](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/crr/credit-institution.md) issuing EMTs. The latter financial institutions have independent obligations under AMLD5. Also, under MiCAR and TFR, there is no reporting obligation from the CASP to the [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) for EU denominated EMTs as to the identity of a new holder of the EMT (i.e. following a transaction).

In view of the application from next June 30 2024 of the new regime under MiCAR for issuing EMTs, it is requested that answers to the above questions be provided urgently. It is of great importance that a uniform application will be followed in this regard, given its substantial practical impact on the actual characteristics of the product range to be developed in the market with regard to EMTs.

*Submitted by: Law firm (Eurius) on behalf of a licensed EMI (Quantoz Payments) (The Netherlands) · 3 May 2024*

***

### Answer

*Answer prepared by the European Commission*

Yes, according to [Article 48(2)](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-48.md) MiCAR, EMTs can only be issued by EMIs or credit institutions. Since EMIs and credit institutions are obliged entities under Directive (EU) 2015/849 as amended by Directive (EU) 2018/843 (AMLD5), it follows that they should comply with the customer due diligence rules prescribed for obliged entities under the Union AML/CFT framework. No exception can be found in MiCAR or Directive (EU) 2015/849 as amended by Directive (EU) 2018/84 with regard to AML/CFT obligations for issuers of EMTs.

***

*The answers clarify provisions already contained in the applicable legislation. They do not extend in any way the rights and obligations deriving from such legislation nor do they introduce any additional requirements for the concerned operators and competent authorities. The answers are merely intended to assist natural or legal persons, including competent authorities and Union institutions and bodies in clarifying the application or implementation of the relevant legal provisions. Only the Court of Justice of the European Union is competent to authoritatively interpret Union law.*

***

**Source:** [EBA Single Rulebook Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7078)

### Related

* [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) — defined term used on this page
* [terrorist financing](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/terrorist-financing.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
* [electronic money](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/emd2/electronic-money.md) — defined term used on this page
* [electronic money](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/electronic-money.md) — defined term used on this page
* [money laundering](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/money-laundering.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/eba-qa-7078-emt-issuer-aml-kyc-scope.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.
