> 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/tofr/transfer-of-funds-regulation/chapter-iii-casp-obligations/article-14-information-accompanying-transfers-of-crypto-assets.md). # Article 14 — Information accompanying transfers of crypto-assets 1. The [crypto-asset service provider](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-service-provider) of the [originator](https://www.mica.wtf/definitions/definitions/tofr/originator) shall ensure that transfers of crypto-assets are accompanied by the following information on the originator: 1. the name of the [originator](https://www.mica.wtf/definitions/definitions/tofr/originator); 2. the originator's [distributed ledger address](https://www.mica.wtf/definitions/definitions/tofr/distributed-ledger-address), in cases where a [transfer of crypto-assets](https://www.mica.wtf/definitions/definitions/tofr/transfer-of-crypto-assets) is registered on a network using [DLT](https://www.mica.wtf/definitions/definitions/tofr/distributed-ledger-technology) or similar technology, and the [crypto-asset account](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-account) number of the originator, where such an account exists and is used to process the transaction; 3. the originator's [crypto-asset](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset) account number, in cases where a [transfer of crypto-assets](https://www.mica.wtf/definitions/definitions/tofr/transfer-of-crypto-assets) is not registered on a network using [DLT](https://www.mica.wtf/definitions/definitions/tofr/distributed-ledger-technology) or similar technology; 4. the originator's address, including the name of the country, official personal document number and customer identification number, or, alternatively, the originator's date and place of birth; and 5. subject to the existence of the necessary field in the relevant message format, and where provided by the originator to its [crypto-asset service provider](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-service-provider), the current [LEI](https://www.mica.wtf/definitions/definitions/tofr/legal-entity-identifier) or, in its absence, any other available equivalent official identifier of the originator. 2. The [crypto-asset](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset) service provider of the originator shall ensure that transfers of crypto-assets are accompanied by the following information on the [beneficiary](https://www.mica.wtf/definitions/definitions/tofr/beneficiary): 1. the name of the [beneficiary](https://www.mica.wtf/definitions/definitions/tofr/beneficiary); 2. the beneficiary's [distributed ledger address](https://www.mica.wtf/definitions/definitions/tofr/distributed-ledger-address), in cases where a transfer of crypto-assets is registered on a network using DLT or similar technology, and the beneficiary's [crypto-asset account](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-account) number, where such an account exists and is used to process the transaction; 3. the beneficiary's crypto-asset account number, in cases where a transfer of crypto-assets is not registered on a network using DLT or similar technology; and 4. subject to the existence of the necessary field in the relevant message format, and where provided by the originator to its crypto-asset service provider, the current [LEI](https://www.mica.wtf/definitions/definitions/tofr/legal-entity-identifier) or, in its absence, any other available equivalent official identifier of the beneficiary. 3. By way of derogation from paragraph 1, point (c), and paragraph 2, point (c), in the case of a transfer of crypto-assets not registered on a network using DLT or similar technology and not made to or from a crypto-asset account, the crypto-asset service provider of the originator shall ensure that the transfer of crypto-assets is accompanied by a [unique transaction identifier](https://www.mica.wtf/definitions/definitions/tofr/unique-transaction-identifier). 4. The information referred to in paragraphs 1 and 2 shall be submitted in advance of, or simultaneously or concurrently with, the transfer of crypto-assets and in a secure manner and in accordance with Regulation (EU) 2016/679. The information referred to in paragraphs 1 and 2 shall not be required to be attached directly to, or be included in, the transfer of crypto-assets. 1. In the case of a transfer of crypto-assets made to a [self-hosted address](https://www.mica.wtf/definitions/definitions/tofr/self-hosted-address), the crypto-asset service provider of the originator shall obtain and hold the information referred to in paragraphs 1 and 2 and shall ensure that the transfer of crypto-assets can be individually identified. Without prejudice to specific risk mitigating measures taken in accordance with Article 19b of Directive (EU) 2015/849, in the case of a transfer of an amount exceeding EUR 1 000 to a [self-hosted address](https://www.mica.wtf/definitions/definitions/tofr/self-hosted-address), the crypto-asset service provider of the originator shall take adequate measures to assess whether that address is owned or controlled by the originator. 1. Before transferring crypto-assets, the crypto-asset service provider of the originator shall verify the accuracy of the information referred to in paragraph 1 on the basis of documents, data or information obtained from a reliable and independent source. 2. Verification as referred to in paragraph 6 of this Article shall be deemed to have taken place where one of the following applies: 1. the identity of the originator has been verified in accordance with Article 13 of Directive (EU) 2015/849 and the information obtained pursuant to that verification has been retained in accordance with Article 40 of that Directive; 2. Article 14(5) of Directive (EU) 2015/849 applies to the originator. 3. The crypto-asset service provider of the originator shall not allow for the initiation, or execute any transfer, of crypto-assets before ensuring full compliance with this Article. --- # 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/tofr/transfer-of-funds-regulation/chapter-iii-casp-obligations/article-14-information-accompanying-transfers-of-crypto-assets.md?ask=&goal= ``` `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.