> 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/mica/recitals/19.md).

# Recital 19

MiCA Recital 19 — Regulation (EU) 2023/1114.

|                 |                                                                                 |
| --------------- | ------------------------------------------------------------------------------- |
| **Instrument**  | Regulation (EU) 2023/1114 (MiCA)                                                |
| **Source**      | [EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32023R1114) |
| **Status**      | In force                                                                        |
| **Review rule** | Legal-text changes require human review                                         |

### (19)

At present, despite their similarities, [electronic money](https://headlesslaw.com/definitions/emd2/electronic-money/) and crypto-assets referencing an [official currency](https://headlesslaw.com/definitions/mica/official-currency/) differ in some important aspects. Holders of electronic money as defined in Directive 2009/110/EC are always provided with a claim against the electronic money [issuer](https://headlesslaw.com/definitions/mica/issuer/) and have a contractual right to redeem, at any moment and at par value, the monetary value of the electronic money held. By contrast, some crypto-assets referencing an official currency do not provide their holders with such a claim against the issuers of such crypto-assets and could fall outside the scope of Directive 2009/110/EC. Other crypto-assets referencing an official currency do not provide a claim at par value with the currency they are referencing or they limit the redemption period. The fact that holders of such crypto-assets do not have a claim against the issuers of such crypto-assets, or that such claim is not at par value with the currency those crypto-assets are referencing, could undermine the confidence of holders of those crypto-assets. Accordingly, to avoid circumvention of the rules laid down in Directive 2009/110/EC, any definition of e-money tokens should be as wide as possible to capture all types of crypto-assets referencing a single official currency. In addition, strict conditions on the issuance of e-money tokens should be laid down, including an obligation for e-money tokens to be issued either by a [credit institution](https://headlesslaw.com/definitions/mica/credit-institution/) authorised under Directive 2013/36/EU of the European Parliament and of the Council (13), or by an [electronic money institution](https://headlesslaw.com/definitions/mica/electronic-money-institution/) authorised under Directive 2009/110/EC. For the same reason, issuers of e-money tokens should ensure that holders of such tokens can exercise their right to redeem their tokens at any time and at par value against the currency referencing those tokens. Because e-money tokens are crypto-assets and can raise new challenges in terms of protection of retail holders and market integrity that are specific to crypto-assets, they should also be subject to the rules laid down in this Regulation to address those challenges.


---

# 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/mica/recitals/19.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.