# Article 14 — Information accompanying transfers of crypto-assets **Source:** [Regulation (EU) 2023/1113 — EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023R1113) 1. The crypto-asset service provider of the originator shall ensure that transfers of crypto-assets are accompanied by the following information on the originator: 1. the name of the originator; 2. the originator's distributed ledger address, in cases where a transfer of crypto-assets is registered on a network using DLT or similar technology, and the 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 account number, in cases where a transfer of crypto-assets is not registered on a network using DLT 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, the current LEI or, in its absence, any other available equivalent official identifier of the originator. 2. The crypto-asset service provider of the originator shall ensure that transfers of crypto-assets are accompanied by the following information on the beneficiary: 1. the name of the beneficiary; 2. the beneficiary's 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 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 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. 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, 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, 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. ## What this means in practice Article 14 is **the operational heart of ToFR for CASPs**. It governs every outgoing transfer initiated by a customer of an EU-registered CASP — regardless of amount, regardless of whether the destination is another CASP, a non-EU entity providing CASP-like services, or a self-hosted address. Three structural points worth internalising: 1. **Information != on-chain payload.** Para 4 second subparagraph is explicit: the information *need not* be attached to or included in the transfer itself. It may be submitted through a separate secure channel, provided it is submitted in advance of, simultaneously with, or concurrently with the transfer and in accordance with GDPR. 2. **The originator information has two layers: what to *****send***** (para 1) and what to *****verify***** (para 6).** Verification of the originator can rely on AMLD5 CDD where the Article 14(7) conditions are met; Article 14 does not require fresh verification for every transfer as a standalone step. That does not displace risk-sensitive monitoring, sanctions controls, or updates where customer information has changed. Verification of the *beneficiary* is not imposed on the originator's CASP by Article 14; the originator's CASP submits the beneficiary information provided by the originator. 3. **Self-hosted address ownership check (para 5).** The trigger is **above EUR 1 000** and the duty is to take adequate measures to assess whether the address is owned or controlled by the originator. The EBA Travel Rule Guidelines specify acceptable methods, including attended or unattended remote verification displaying the address, sending a predefined amount to or from the self-hosted address, digitally signing a specific message with the corresponding key, or other suitable technical means that allow a reliable and secure assessment. Note also that para 5 first subparagraph imposes an obligation that applies **at any amount** to self-hosted transfers: the CASP must *obtain and hold* the originator and beneficiary information **and** ensure the transfer can be individually identified. The EUR 1 000 trigger sits *on top of* that baseline, only for the ownership-control assessment. ## Compliance checklist A CASP acting as originator-side CASP must, for every outgoing transfer of crypto-assets: * [ ] **Collect originator data** — name, DLT address (where applicable), crypto-asset account number (where applicable), address+ID-number or DoB+place-of-birth, and LEI/equivalent identifier where available and supported by the message format. * [ ] **Collect beneficiary data** — name, DLT address (where applicable), crypto-asset account number (where applicable), and LEI/equivalent identifier where available and supported by the message format. Source: the originator (Recital 39). * [ ] **Verify originator information** from a reliable and independent source before transferring (or rely on AMLD5 CDD, if completed for the originator). * [ ] **Submit the information securely** in advance of, simultaneously with, or concurrently with the transfer, using a channel that allows the CASP to comply with ToFR and GDPR. Comply with [GDPR Chapter V](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679) for third-country transmission. * [ ] **For transfers to a self-hosted address above EUR 1 000**, take adequate measures to assess that the address is owned or controlled by the originator, using one or more EBA-recognised verification methods where needed. * [ ] **For all self-hosted transfers**, ensure the transfer can be individually identified and that originator/beneficiary information is held by the CASP. * [ ] **Refuse to initiate or execute** the transfer until full compliance with Article 14 is confirmed (para 8 — a hard stop). * [ ] **Document the assessment** trail (verification source, self-hosted ownership check, choice of Travel Rule transmission method, retention period) — both for [Art. 26 record retention](/tofr/transfer-of-funds-regulation/chapter-v-information-data-protection-record-retention/article-26-record-retention.md) and for [MiCA Art. 68 (operating conditions)](broken://pages/6SZpsLKLnGxyb93Lt5nI) audit trails. ## Cross-references * [MiCA Art. 82 (providing transfer services for crypto-assets)](broken://pages/tfHwUd1WYacCBxDkEObE) — the MiCA service that most directly triggers Article 14. * [ToFR Art. 16 (beneficiary-side detection)](/tofr/transfer-of-funds-regulation/chapter-iii-casp-obligations/article-16-detection-of-missing-information.md) — mirror provisions on the beneficiary CASP. * [ToFR Art. 23 (restrictive measures)](/tofr/transfer-of-funds-regulation/chapter-iv-common-measures/article-23-internal-policies-restrictive-measures.md) — internal policies screening transfers against EU and national sanctions. * AMLD5 Art. 19a (heightened CDD for self-hosted addresses) — inserted by ToFR Art. 38. --- # Agent Instructions: 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: ``` GET https://www.mica.wtf/tofr/transfer-of-funds-regulation/chapter-iii-casp-obligations/article-14-information-accompanying-transfers-of-crypto-assets.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.