> 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-v-information-data-protection-record-retention/article-26-record-retention.md). # Article 26 — Record retention 1. Information on the [payer](https://www.mica.wtf/definitions/definitions/tofr/payer) and the [payee](https://www.mica.wtf/definitions/definitions/tofr/payee) or on the [originator](https://www.mica.wtf/definitions/definitions/tofr/originator) and [beneficiary](https://www.mica.wtf/definitions/definitions/tofr/beneficiary) shall not be retained for longer than strictly necessary. [Payment service providers](https://www.mica.wtf/definitions/definitions/tofr/payment-service-provider) of the payer and of the payee shall retain records of the information referred to in Articles 4 to 7, and [crypto-asset service providers](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-service-provider) of the originator and beneficiary shall retain records of the information referred to in Articles 14 to 16, for a period of five years. 2. Upon expiry of the retention period referred to in paragraph 1, [payment service providers](https://www.mica.wtf/definitions/definitions/tofr/payment-service-provider) and [crypto-asset](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset) service providers shall ensure that the personal data is deleted, unless otherwise provided for by national law which determines under which circumstances payment service providers and [crypto-asset service providers](https://www.mica.wtf/definitions/definitions/tofr/crypto-asset-service-provider) may or shall further retain such data. Member States may allow or require further retention only after they have carried out a thorough assessment of the necessity and proportionality of such further retention, and where they consider it to be justified as necessary for the prevention, detection or investigation of [money laundering](https://www.mica.wtf/definitions/definitions/tofr/money-laundering) or [terrorist financing](https://www.mica.wtf/definitions/definitions/tofr/terrorist-financing). That further retention period shall not exceed five years. 3. Where, on 25 June 2015, legal proceedings concerned with the prevention, detection, investigation or prosecution of suspected [money laundering](https://www.mica.wtf/definitions/definitions/tofr/money-laundering) or [terrorist financing](https://www.mica.wtf/definitions/definitions/tofr/terrorist-financing) are pending in a Member State, and a payment service provider holds information or documents relating to those pending proceedings, the payment service provider may retain that information or those documents in accordance with national law for a period of five years from 25 June 2015. Member States may, without prejudice to national criminal law on evidence applicable to ongoing criminal investigations and legal proceedings, allow or require the retention of such information or documents for a further period of five years where the necessity and proportionality of such further retention has been established for the prevention, detection, investigation or prosecution of suspected money laundering or terrorist financing. --- # 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-v-information-data-protection-record-retention/article-26-record-retention.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.