> 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/eu-level/q-and-a/pending-questions/eba-qa-7069-recital-54-article-54-significance.md). # Scope of Recital 54 and Article 54 — significance classification | | | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Authority** | EBA | | **Q\&A ID** | 2024\_7069 | | **Status** | Under Review | | **Submitted** | 29 April 2024 | | **Legal basis** | [Articles 54](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-54.md), Recital 54 [MiCA](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md) | | **Source** | [EBA Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7069) | ### Question Question 1: Recital 54 [MiCAR](https://github.com/jakesenfti/micawtf/blob/main/mica/README.md) seems to presume that the same ART may be issued by EU and third country entity, when speaking of "Issuers of asset-referenced tokens that are marketed both in the Union and in third countries". Does recital 54 mean a technically same fungible token not (externally) attributable to a particular [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) or does this only mean that the token has the same rights attached and is marketed under the same name but is not technically identical and should be attributable to one issuer (in Union or in third countries)? Question 2: Does Recital 54 MiCAR, while referring to ART issuers and their [reserve of assets](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/reserve-of-assets.md) requirements, also apply to EMT issuers (including cases where no reserve requirements under MiCAR apply) and should it be used to interpret prudential requirements for EMT issuers (including [Article 54](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-54.md) MiCAR and EMD)? Question 3: if ever recital 54 was to be extended to all EMT issuers, how would this recital have to be interpreted in relation with article 54, which foresees that EMT issuers should safeguard [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/funds.md) received by issuers of e-money tokens in exchange for e-money tokens in accordance with Article 7(1) of Directive 2009/110/EC? ### Background Recital 54 provides guidance regarding reserve requirement applicable to ART issuers and their [reserve of assets](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/reserve-of-assets.md) in cases where such issuers market their tokens both in the Union and in third countries. This recital provides that, in such cases, these ART issuers "\[...] should ensure that their reserve of assets is available to cover the issuers' liability towards Union holders" and that "The requirement to hold the reserve of assets with firms subject to Union law should therefore apply in proportion to the share of asset-referenced tokens that is expected to be marketed in the Union". This recital raises several interpretation issues. Question 1 First, on the cases it addresses, as it is not entirely clear whether this recital tackles i) an [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) which issues in the Union and in third countries a technically unique token -that could possibly not be attributable to a specific issuers in case of multi issuance- or ii) an issuer that issues different tokens, that could be marketed under the same name but that would not be technically identical -and therefore that could be attributable to a specific issuer in case of multi issuance-. Question 2 Second, on the possible extension of recital 54 to other type of issuers (namely, EMT issuers, whether or not they are subject to reserve of assets requirements). The rationale for such an extension is that EMT issuers could also market tokens both in the Union and in third countries, and could therefore be in the situation described in the recital. Question 3 Third, if ever this recital was to be extended to all EMT issuers, then the articulation of said recital with [article 54](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-54.md) of MICAR would be in question. [Article 54](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-54.md) of MICA foresees that EMT issuers should safeguard [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/funds.md) received by issuers of e-money tokens in exchange for e-money tokens in accordance with Article 7(1) of Directive 2009/110/EC, meaning that said funds should be safeguarded using the instruments described in points (a) and (b) of article 54 by no later than five business days (as per article 7(1) of Directive 2009/110/EC). However, if ever recital 54 was to be interpreted as allowing for cases where one or multiple issuers can issue and market one technically identical token both in the Union and in third countries, then it might prove very difficult -if not technically unfeasible- for issuers to have a comprehensive view of the overall amount of tokens that are in each jurisdiction in real time (and therefore to have an exact assessment of issuers' liability towards Union holders at all time), as tokens would continually circulate between the different jurisdictions on the secondary market, whether through exchanges, hosted wallets or unhosted wallets. The only way for issuers to assess these volumes would be through estimates and reportings from EU exchanges, which would in any case not cover all potential transactions occurring through unhosted wallets. In such a situation, imbalances could be created between the level of funds safeguarded according to recital 54 and the level of funds to be protected as the requirements set per recital 54 (for example, underfunding cases if ever large amount of tokens initially marketed toward third countries would ultimately be held and redeemed by EU holders, said amount exceeding the funds safeguarded pursuant to article 54). *Submitted by: Autorité de contrôle prudentiel et de résolution (France) · Answer prepared by the European Commission because it is a matter of interpretation of Union law* *** **Source:** [EBA Single Rulebook Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7069) ### Related * [reserve of assets](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/reserve-of-assets.md) — defined term used on this page * [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) — defined term used on this page * [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/funds.md) — defined term used on this page * [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/psd2/funds.md) — defined term used on this page * [funds](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/funds.md) — defined term used on this page --- # 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/eu-level/q-and-a/pending-questions/eba-qa-7069-recital-54-article-54-significance.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.