> 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/pending-questions/eba-qa-7457-psd2-applicability-emt-issuance.md).

# PSD2 applicability to EMT issuance/redemption

|                 |                                                                                                                                                       |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authority**   | EBA                                                                                                                                                   |
| **Q\&A ID**     | 2025\_7457                                                                                                                                            |
| **Status**      | Under Review                                                                                                                                          |
| **Submitted**   | 15 May 2025                                                                                                                                           |
| **Legal basis** | [Article 49](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-49.md) [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md) |
| **Source**      | [EBA Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2025_7457)                                                                 |

### Question

1. An EMI is acting solely as an [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) of EMTs ("EMTI") to its customers - crypto asset service providers (CASPs), these then provide the EMTs to their retail customers to be used for cryptoassets trading. EMTI does not maintain any fiat currency [payment account](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/payment-account.md) for CASPs, nor provide any cryptocurrency services to them within the meaning of [Articles 60(4)](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-60.md) and [62](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-62.md) of the [MICAR](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md). Does the issuance of EMTs lead to a contractual relationship between the EMT holder (CASP, to whom the EMT is issued) and the EMTI within the meaning of PSD2 and EMD2? Is this contract passed on to the subsequent EMT holders who will acquire the EMTs from CASPs?
2. What is the legal nature of the acts of issuance and redemption of the EMTs?
3. Which provisions of PSD2, if any, apply to issuance and redemption of the EMTs?

### Background

The EMTI mentioned in the query intends to issue EMTs only to CASPs within the meaning of MiCAR.

1. In the described case, the issuance of EMTs does not create a contractual relationship within the meaning of PSD2, as there is no contract as per Article 11(3) of EMD2. The main difference between EMTs and non-tokenized [electronic money](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/emd2/electronic-money.md) (NtEM) is that EMTs do not require the holder to have a direct contractual relationship with the EMTI. At the same time, however, any holder of an EMT may, at any time, exercise their right against the EMTI to redeem the EMTs at par value in equivalent fiat currency, as set forth in [Article 49(4)](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-49.md) of the MICAR.

The issuance and redeemability of EMTs is governed exclusively by [Article 49](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-49.md) of MiCAR, which provides for the application of MiCAR instead of the provisions of Article 11 of EMD2. The conditions for the issuance and redemption are therefore set out in the White Paper as per [Article 51](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-51.md) of MiCAR. Unlike NtEM, the issuance and redemption of EMTs by EMTI is not linked to the provision of a payment service, as in this case the EMTI does not maintain any payment accounts for token holders from which [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/funds.md) (in this case EMTs) are debited (credited).

2. Both issuance and redemption of EMTs are two bilateral legal relationships. In the case of issuance, upon payment of [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/funds.md) in fiat currency by the EMTI customer, the EMTI discharges its debt to the future EMT holder by issuing them an EMT at an equivalent monetary value. Similarly, in the case of redemption, the EMTI discharges its debt to the EMT holder by transferring them the equivalent monetary value of their EMT in the given fiat currency, after the EMT holder has exercised their legal right of redemption and sent the EMTs to the relevant DLT address.
3. In light of the above, Titles III and IV of PSD2 do not apply to the issuance and redemption of EMTs at all.

*Submitted by:* [*Competent authority*](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) *· Answer prepared by the European Commission because it is a matter of interpretation of Union law*

***

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

### Related

* [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.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
* [payment services](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/payment-services.md) — defined term used on this page
* [payment services](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/psd2/payment-services.md) — defined term used on this page
* [payment account](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/payment-account.md) — defined term used on this page
* [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) — defined term used on this page
* [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/funds.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/pending-questions/eba-qa-7457-psd2-applicability-emt-issuance.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.
