← current version of this provision

MiCA Recital (71) — preamble

This page is a held version, frozen at the capture below. It is a source for review. It is not advice, and it does not determine whether this provision applies to you.

(71) Significant e-money tokens could pose greater risks to financial stability than e-money tokens that are not significant and traditional electronic money. Issuers of significant e-money tokens that are electronic money institutions should therefore be subject to additional requirements. Such issuers of significant e-money tokens should in particular be subject to higher capital requirements than issuers of other e-money tokens, be subject to interoperability requirements and establish a liquidity management policy. They should also comply with some of the same requirements that apply to issuers of asset-referenced tokens with regard to reserve of assets, such as those on custody and investment of the reserve of assets. Those requirements for issuers of significant e-money tokens should apply instead of Articles 5 and 7 of Directive 2009/110/EC. As those provisions of Directive 2009/110/EC do not apply to credit institutions when issuing e-money, neither should the additional requirements for significant e-money tokens under this Regulation.
CELEX: 32023R1114 · provision: 71
Locator: Recital (71); PDF page 9; derived-text line 596
Held artifact: docs_evidence/eu-legislation/eurlex-full-text/20260823T093000Z/32023R1114.pdf
Artifact SHA-256: 32c6d21e712dbb719a9a6b2d39e85133f3059d9e02d8d9ce70d35332bd568b8b
Captured: 20260823T093000Z
Extracted with: pdftotext version 4.00
Official source: EUR-Lex
This version: /celex/32023R1114/RECITAL_71/20260823-32c6d21e/
Corpus Merkle root: 581628a5b36518981241d2b51f048aa46384f30a74bf648ef542c652028cdeff
Membership proof: 10 hashes — see corpus-proof.json
Modal verbs, counted verbatim (not a legal characterisation): 'shall not': 0 · 'shall': 0 · 'must': 0 · 'may not': 0 · 'may': 0 · 'should': 5

To verify independently: fetch the official source above, extract it with the named tool, and confirm the artifact SHA-256 matches. Then check this provision's leaf against the published Merkle root using the proof in corpus-proof.json.