← current version of this provision
MiCA Recital (93) — 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.
(93) A provider of transfer services for crypto-assets should be an entity that provides for the transfer, on behalf of a client, of crypto-assets from one distributed ledger address or account to another. Such transfer service should not include the validators, nodes or miners that might be part of confirming a transaction and updating the state of the underlying distributed ledger. Many crypto-asset service providers also offer some kind of transfer service for crypto-assets as part of, for example, the service of providing custody and administration of crypto-assets on behalf of clients, exchange of crypto-assets for funds or other crypto-assets, or execution of orders for crypto-assets on behalf of clients. Depending on the precise features of the services associated to the transfer of e-money tokens, such services could fall under the definition of payment services in Directive (EU) 2015/2366. In such cases, those transfers should be provided by an entity authorised to provide such payment services in accordance with that Directive.
CELEX: 32023R1114 · provision: 93
Locator: Recital (93); PDF page 11; derived-text line 769
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_93/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': 3
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.