← current version of this provision
MiCA Article 82 — held text
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.
Article 82 Providing transfer services for crypto-assets on behalf of clients 1. Crypto-asset service providers providing transfer services for crypto-assets on behalf of clients shall conclude an agreement with their clients to specify their duties and their responsibilities. Such agreement shall include at least the following: (a) the identity of the parties to the agreement; (b) a description of the modalities of the transfer service provided; (c) a description of the security systems used by the crypto-asset service provider; (d) fees applied by the crypto-asset service provider; (e) the applicable law. 2. ESMA, in close cooperation with EBA, shall issue guidelines in accordance with Article 16 of Regulation (EU) No 1095/2010 for crypto-asset service providers providing transfer services for crypto-assets on behalf of clients as regards procedures and policies, including the rights of clients, in the context of transfer services for crypto-assets. CHAPTER 4 Acquisition of crypto-asset service providers
CELEX: 32023R1114 · provision: 82
Locator: Article 82; PDF page 62; derived-text line 4201
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/ART_82/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': 3 · 'must': 0 · 'may not': 0 · 'may': 0 · 'should': 0
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.