CCP Collateral Tokenisation: ESMA’s 30 Questions Due 15 January 2027

On 9 October 2026 ESMA opened a call for evidence on CCP collateral tokenisation (ESMA91-1505572268-4934), asking whether tokenised securities and tokenised cash could be posted as margin and default fund contributions at EU central counterparties without weakening the safeguards EMIR builds around collateral. Comments are due by 15 January 2027. ESMA says it will assess the feedback in the first quarter of 2027 and then decide on the most appropriate course of action, which its press release says could include regulatory or supervisory convergence action within its remit.

The paper is addressed to CCPs, clearing members and their clients, CSDs, custodians, triparty agents and providers of tokenisation or DLT solutions. Its 30 questions follow collateral through its whole life at a CCP: how a tokenised asset is mobilised and posted, who holds enforceable rights over it, when a transfer becomes final, how quickly it turns into cash after a clearing member default, and which technology components a supervisor should treat as critical. The questions test those arrangements against existing law: the collateral, segregation and default rules in EMIR, the Financial Collateral Directive, the Settlement Finality Directive and DORA.

For a clearing member running a tokenisation pilot, or a CCP being asked to accept a tokenised version of a bond it already takes, the paper sets out how ESMA intends to test those arrangements. ESMA’s own executive summary frames the exercise as gathering evidence “before deciding whether any action under its remit might be necessary”, so no action at all remains one of the possible outcomes.

Related reading: Guarantees as CCP Collateral: What ESMA’s Draft RTS Changes

Key dates for the CCP collateral tokenisation call for evidence

Only the first two rows are fixed dates. The paper sets no application date for anything, because it contains no draft legal text: its two annexes are the list of questions and a set of definitions.

What the paper sets out to test, and the scope it rules out

ESMA states the boundary early. The executive summary confines the exercise to whether tokenisation may affect the way otherwise eligible assets are mobilised, transferred, managed, protected and realised, and whether existing regulatory and supervisory frameworks remain adequate in that context, with the categories of assets eligible as CCP collateral left outside its scope. A footnote widens the object of study to “DLT financial instruments and tokenised forms of cash”, so the cash leg of margining sits inside the scope alongside securities.

The diagram in section 2 of the paper makes the split concrete: initial margin appears as tokenised securities and variation margin as tokenised cash, against a lifecycle that runs from asset eligibility through allocation, mobilisation, posting, collateral management, margining, default management and release. ESMA’s working assumption, set out in paragraph 6, is that tokenisation leaves the underlying legal, credit, market, liquidity and operational risks in place and “should not alter the fundamental requirements applicable to CCP collateral”. The Chair of ESMA’s CCP Supervisory Committee put the same point in the press release: collateral must be of high quality, legally enforceable, highly liquid and easily operationally available, including in stressed conditions and after a clearing member default.

One consequence is easy to misread. In ESMA’s framing, eligibility travels with the underlying asset. Paragraph 52 says a tokenised government bond or share should, as a starting point, reflect the same credit and market risk characteristics as its traditional equivalent, so an instrument that fails the eligibility conditions in traditional form stays outside them on a ledger. The reverse does not hold automatically either: paragraph 54 flags that a tokenised form of a highly liquid asset may still introduce conversion, operational or cyber-loss risk that is relevant, where appropriate, to eligibility, the level of haircuts or other adjustments.

The EMIR rules that frame every question

The paper rarely cites article numbers, but the requirements it describes map onto a short list of provisions. The table below is my mapping of those provisions to the sections and questions of the paper; ESMA cites Article 47 EMIR directly in paragraph 61, which introduces Q19, and Article 2(2) of the Financial Collateral Directive in paragraph 30, ahead of Q9.

The row worth reading twice is Article 47(3). It requires financial instruments posted as margin or default fund contributions to be deposited, where available, with the operator of a securities settlement system, or alternatively in another highly secure arrangement with an authorised financial institution, and Article 44 of Delegated Regulation 153/2013 lists those arrangements as a central bank, an authorised credit institution or a third-country financial institution subject to prudential rules at least as stringent as the EU’s. ESMA has already met an asset that fits none of them. In its February 2026 consultation on guarantees and investment policy (ESMA91-1505572268-4513), it explained that some CCPs accepting emission allowances under Article 46(2) could not comply with Article 47(3), because allowances cannot be deposited with a settlement system operator or any of the Article 44 arrangements, and it proposed adding the Union Registry as a new point (d) in Article 44(1).

My reading is that a natively issued token held only on a DLT platform could raise the same deposit-location question, and that Q28 is where it belongs. That question asks respondents to identify any provision which, “while not excluding DLT, presupposes conventional intermediaries, accounts, settlement structures or transfer formalities”. The emission allowances case shows the kind of fix ESMA has proposed before for an asset that does not fit the deposit list: a targeted addition to Article 44, still at draft stage.

Digital twins, native tokens and the path to cash in a default

ESMA groups tokenised collateral arrangements into two implementation models and asks in Q2 whether its taxonomy of “digital twin”, “native” and “hybrid” matches practice. In a digital twin, the token evidences, mirrors or helps the use of rights recorded in a conventional custody, settlement or CSD infrastructure, and it may or may not be the legally authoritative record. ESMA singles out consistency between the token layer and the underlying “golden record”, and clarity on which record prevails when they disagree, as one of the central operational features of this model. In a native model, the asset is issued, held and transferred only on the ledger, and collateral management depends on the ledger itself, its controls and any linked settlement processes.

The distinction matters most at the moment a CCP needs to sell or repo the collateral. For digital twins, ESMA’s understanding “based on early experience” is that the path from posted collateral to usable liquidity stays closely tied to the traditional infrastructure: the token may speed up identification, allocation and pre-positioning, but disposal after a default is likely to depend on processes inside custodial or CSD systems, with reconciliation, confirmation and messaging steps in between. For native models, the timing would depend on available liquidity, the settlement mechanisms connected to the platform and any reliance on external infrastructures or intermediaries.

That makes a fast token layer a weak guide to stress performance. A digital twin can cut posting times in normal conditions and still leave the default timeline governed by the slowest custodial step. Q4 asks for exactly that sequence: the main steps from posted collateral to liquidity realisation, including bottlenecks and dependencies, for whichever model the respondent prefers.

ESMA’s evidence base is thin, and the paper says so. Footnote 10 records that, by the time the paper was finalised, the only project in central clearing ESMA had seen through its work in EMIR CCP supervisory colleges was HQLAx. Q1 asks respondents to describe any tokenisation initiative relevant to collateralisation in central clearing, and the instruction that follows asks them to indicate, where necessary, which tokenisation solution each later answer applies to. Readers following the wholesale settlement side can compare the BIS work ESMA cites in its executive summary, covered in our Project Agora tokenised wholesale payments article.

Title transfer, security interest and what control means for a wallet

Section 4 of the paper starts from the two legal structures CCP collateral already uses. Under title transfer, the CCP becomes the legal owner on posting and owes equivalent assets back if no default occurs. Under a security interest, such as a pledge or charge, ownership stays with the provider and the CCP holds enforceable rights it can exercise on default. ESMA asks in paragraph 26 whether a transfer of tokenised collateral achieves the first, the second, or “merely a transfer of a digital representation that does not itself confer proprietary rights”.

Holding the keys and holding the rights can come apart. Paragraph 25 states that technical control over a token or its private keys “might not mean legal ownership or legally recognised control”, because those effects depend on the applicable legal and contractual framework. That links directly to the Financial Collateral Directive, which ESMA quotes: financial collateral must “be in the possession or under the control of the collateral taker or of a person acting on the collateral taker’s behalf”. ESMA adds that the FCD is not confined to bilateral arrangements outside market infrastructures, since CCPs, settlement agents and clearing houses are expressly among the entities that may be parties to an FCD arrangement. Q9 asks whether control of a wallet or private key has any legal significance for creating, perfecting or enforcing collateral rights, and under which legal framework.

The conflict-of-laws problem is the second thread. Traditional arrangements locate the governing law through connecting factors such as the law of the account, the location of the intermediary or the location of the asset. A tokenised arrangement can spread the issuer, custodian, tokenisation platform, validator nodes, clearing member, CCP and clients across several jurisdictions, and ESMA notes that the law governing the token, the proprietary effects of ledger entries or the insolvency may differ from the law governing the underlying asset or the collateral agreement. Q8 asks how the applicable property law is determined and whether the method differs from traditional arrangements.

ESMA cites, as an example of layered recording, a Spanish law enacted in 2023 that requires a designated responsible entity to administer and validate the decentralised registries used to record and tokenise financial instruments. Paragraph 20 records that ESMA is running parallel analytical work with national competent authorities on whether and how national legal frameworks have evolved to take account of DLT and whether barriers to tokenisation exist, and the legal questions in the call for evidence are meant to complement that work.

Segregation and porting when the account becomes a wallet

EMIR Article 39 requires CCPs to offer, and clearing members to offer their clients, at least omnibus client segregation and individual client segregation. ESMA’s EMIR Q&A (CCP Answer 8) adds two details that carry straight into a tokenised setting. First, an individually segregated account must identify the specific assets due to the client, for example the particular or equivalent securities; a record of the value due is not enough to meet the individual segregation requirement. Second, individual segregation applies at CCP level and does not have to be mirrored at the level of the securities settlement system or central bank, although Article 47(5) still requires CCP assets to be distinguishable from clearing member assets when deposited with a third party.

The call for evidence restates segregation as a set of functional outcomes. Paragraph 33 lists three: assets clearly attributable to specific participants or clients in a legally and operationally recognisable way; prevention of unauthorised use, rehypothecation or double use; and attribution and control that remain effective and enforceable in stress, including default or insolvency. Wallet separation, permissioned ledger structures and smart contract controls can support those outcomes, but paragraph 34 warns that they “might not necessarily imply legally enforceable attribution of assets”, exclusion from the insolvency estate of custodians or platform operators, or prevention of double use. Q10 asks respondents to keep technical separation and legal separation apart in their answers.

The double-layer risk is specific to digital twins. Where a token coexists with an underlying asset held in a traditional infrastructure, any divergence between the two records can create double pledging, inconsistent records of ownership or control, or uncertainty over which record prevails in insolvency. Paragraph 36 asks who carries legal responsibility for record accuracy, client asset segregation and the prevention of unauthorised transfers across custodians, platform operators, DLT nodes and other intermediaries.

Porting is the part of Article 48 that tokenisation could help or hinder. After EMIR 3, Article 48(5) requires the CCP, at a minimum, to commit contractually to trigger the transfer of omnibus client assets and positions to another clearing member designated by all of those clients, without the consent of the defaulting clearing member, and to transfer them unless all clients object before the transfer is concluded. The receiving clearing member is obliged to accept those assets and positions only where it has previously entered into a contractual relationship with those clients committing it to do so, and if no transfer takes place within the predefined transfer period in the CCP’s operating rules, the CCP may manage its risk on those positions, including by liquidating them. Paragraph 38 of the paper asks whether tokenised arrangements support effective porting “including where wallets, permissions, platform access or identity controls are involved”, and Q11 asks which operational or legal dependencies could affect portability. One dependency worth testing against that list is whether the back-up clearing member is already connected to the relevant platform.

Settlement finality: on-chain confirmation versus the legal moment

ESMA’s position on finality is explicit. Under the Settlement Finality Directive, the system rules determine key moments such as entry into the system and irrevocability, and the law then protects those moments from later insolvency proceedings. Paragraph 43 ties finality to the legal recognition of specific operational events as definitive, a moment which “may or may not coincide with technical settlement finality”. My reading is that this leaves two timestamps to evidence for each transfer: the technical event on the ledger, and the point at which the applicable legal framework treats the transfer as irrevocable.

The evidence from existing DLT projects is limited. Paragraph 44 records that ESMA’s limited experience, largely based on projects authorised under the DLT Pilot Regime, shows these projects have so far implemented “finality-like protections through private law contractual clauses”, that those projects do not concern CCP collateral management, and that at greater scale designation of a system under the SFD “could become crucial for finality protection”. Paragraph 46 lists the design features that can weaken technical finality in practice: mechanisms allowing reversal or amendment in exceptional circumstances, administrative override functions, smart contract logic enabling conditional settlement or unwind, and continued reliance on off-ledger reconciliation with custodial or CSD records.

For a CCP, the moment collateral counts as posted and available for risk management should coincide with the point at which the transfer is legally irrevocable and protected against later challenge. Paragraph 47 warns that misalignment may create timing risk and uncertainty in default management, most acutely under stress when large volumes are processed against deadlines. Q12 to Q14 ask how the point of finality is defined, which infrastructure or governance features help or harm irreversibility, and how multi-layer arrangements keep operational records consistent with legally recognised outcomes. Whether a governance override on a permissioned ledger is compatible with an irrevocability point under designated-system rules is a question the paper leaves open.

Haircuts, liquidity and the tokenised cash leg

Article 46(1) EMIR requires haircuts that reflect the potential decline in value between the last revaluation and the time by which collateral can reasonably be assumed to be liquidated, and requires the CCP to account for liquidity risk after a default and concentration risk. Section 5 of the paper applies that test to tokenised forms. The starting point is neutral: tokenisation “does not alter the economic nature of the underlying asset and should not, in itself, justify a different prudential treatment”. The question in Q15 is whether the tokenised form changes the time, process or certainty with which an already eligible asset converts into cash, including under stress, and whether that warrants safeguards or adjustments to haircut methodology.

Paragraph 54 names the channels. Liquidity risk can arise where access to cash depends on redemption processes, where transfers require specific platforms or settlement assets, where the tokenised security faces constraints on convertibility or transferability, or where the platform is poorly connected to the wider financial system or relies on public infrastructures. Q16 adds wrong-way and concentration risk where value or liquidity depends on specific issuers, platforms or counterparties.

Cash is treated separately. Paragraph 55 lists the candidate settlement assets in a tokenised environment as tokenised central bank money, stablecoins, e-money tokens and tokenised deposits, and states that some of these “may not be considered equivalent to cash by regulatory and/or supervisory frameworks, in particular stablecoins in view of potential deviation from par”. Their effective liquidity, ESMA says, may depend on whether they can legally discharge cash obligations, whether the parties agree to treat them in lieu of payment, how reliable redemption rights are, the issuer’s credit quality and the operational soundness of conversion mechanisms. On the central bank money side, ESMA points to the Eurosystem’s Pontes initiative, which connects DLT platforms with TARGET Services, as a possible route for tokenised collateral settlement in central bank money; our ECB Appia and Pontes article covers that roadmap.

The systemic angle sits in paragraphs 58 and 59. Faster settlement and programmability could shorten the time participants have to source eligible collateral and raise intraday liquidity needs, and automated triggers for mobilisation or substitution could make many participants call or move collateral at once in a stress, potentially increasing demand for the same assets or sources of liquidity at the same time. Q18 asks whether these effects carry broader implications for liquidity risk and procyclicality, and EMIR 3 now requires a CCP, under Article 46(1), to take into account the need to minimise procyclicality effects when revising its haircuts. Q19 then asks whether tokenisation affects a CCP’s ability to manage and invest collateral in accordance with EMIR requirements, which paragraph 61 ties to Article 47.

Operational resilience: the dependency map ESMA wants drawn

Section 6 places tokenised collateral inside the DORA framework that already applies to CCPs, and applies the same operational resilience expectations to it. Paragraph 64 locates the possible effect of tokenisation in the way operational and cyber risks arise and the channels through which they may affect the collateral process. In a digital twin model, the underlying asset may sit safely in a custody or CSD chain while an outage, coding error or reconciliation failure in the tokenisation layer stops it being mobilised, confirmed or made available to the CCP. In a native model, a disruption in node operations, key management, permissions or smart contract execution can block a transfer even though the asset itself remains valid. ESMA flags permissionless ledgers, where network participants and governance may be decentralised and potentially anonymous, as a source of additional dependencies.

Q21 asks which components should count as critical dependencies for supervisory purposes. Paragraph 66 gives ESMA’s provisional list: the ledger or tokenisation platform, smart contracts or other logic governing collateral status, key management and access control, interfaces with custodians, CSDs, triparty agents or collateral management systems, reconciliation and messaging layers, settlement links, synchronisation mechanisms, and the arrangements used for tokenised cash or settlement assets. Paragraph 68 adds third-party concentration, for example several CCPs relying on the same platform, cloud environment, smart contract developer or wallet infrastructure.

The testing list in paragraph 67 is specific enough to plan against: default management simulations, cyber-incident scenarios, loss or compromise of private keys, platform outage, failed reconciliation between token and underlying records, smart contract malfunction, governance intervention, and stressed conversion of tokenised collateral into usable liquidity, run end to end with custodians and technology vendors. Q22 asks what testing, assurance and fallback arrangements would be needed before CCPs could rely on tokenised collateral more broadly, “in particular potential new extreme but plausible scenarios”. The phrase echoes the stress-testing language of Article 49(1) EMIR. Our ESMA CCP fire drill article describes how a multi-CCP default simulation of that kind was scoped.

Interoperability, market structure and who supervises which function

In section 7, “interoperability” means the ability of tokenised collateral to move across platforms, infrastructures and CCPs; footnote 20 distinguishes it from interoperability for CCPs under Title V of EMIR. ESMA argues that an asset already eligible in traditional form should not become operationally captive to one venue, collateral platform or infrastructure arrangement once tokenised. Q23 and Q24 ask whether a lack of interoperability risks fragmenting tokenised collateral and whether common market practices, technical standards or regulatory approaches are needed.

The market structure questions look further along the chain. Paragraph 73 notes that tokenisation can shift influence towards platforms, technology providers, and private governance bodies such as the entities, foundations, consortia or committees that control the rules of a permissioned network, as well as interoperability, custody and wallet service providers. Paragraph 75 lists the EU frameworks that may become relevant depending on the model: EMIR, CSDR, the Settlement Finality Directive, the Financial Collateral Directive, MiCA, DORA and, where applicable, the DLT Pilot Regulation. Q27 asks which entities would perform the critical functions and which of those frameworks would apply to each.

Q28 is the question with the most direct path to rule changes. It asks whether the current framework is technologically and “system neutral”, meaning it allows tokenised collateral regardless of the technology or infrastructure used to issue, hold, transfer or settle it, and invites respondents to name provisions that need amendment or clarification. ESMA asks for coverage of all relevant EMIR requirements, giving segregation, investment policy and settlement as examples, as well as the Settlement Finality Directive. Q29 and Q30 close the paper with open questions on anything missed and on other CCP use cases, which paragraph 79 suggests could include post-trade matching or netting and the integration of tokenised assets into default management.

Turning the 30 questions into a response plan

ESMA’s standard guidance applies: answer the question stated, identify the question each comment relates to, give a clear rationale and describe alternatives ESMA should consider. Submissions go through the consultation webpage using the reply form in Word format, with annexes accepted in other formats, up to five files within a 200 MB limit.

ESMA asks each comment to identify the question it relates to, which leaves room to answer only where a firm holds evidence. The instruction after Q1 asks respondents to say which tokenisation solution an answer refers to, and the reply form gives that instruction its own answer field. The groupings below are my suggestion, built on the paper’s own sections, of where each type of firm is likely to hold first-hand evidence:

• CCPs: Q4 and Q6 on the default path and the exercise of rights, Q19 on investment under Article 47, Q21 and Q22 on critical dependencies and testing.
• Clearing members and clients: Q10 and Q11 on segregation and porting, Q15 to Q17 on conversion to cash and haircut factors.
• CSDs, custodians and triparty agents: Q12 to Q14 on finality in multi-layer arrangements, Q8 on applicable law.
• Tokenisation and DLT providers: Q2 and Q3 on models, Q20 on operational and cyber risk, Q27 on who performs critical functions.
• Legal advisers and industry associations: Q5, Q7 and Q9 on legal structure, cross-border barriers and FCD control, Q28 on technological neutrality.

Answers to Q28 carry the most weight when they cite the provision, explain the conventional structure it presupposes and propose the narrowest change that would fix it. The Article 47(3) and Article 44 deposit arrangements discussed above are one candidate a CCP could test against its own arrangements.

Frequently Asked Questions

Does the call for evidence change anything we report under EMIR?

None of the 30 questions concerns trade reporting or margin reporting to trade repositories, and the paper contains no draft amendment to any reporting standard. Any change to what counterparties report about collateral would need its own legal instrument. Our EMIR reporting requirements guide sets out the current obligations, which this paper leaves as they are.

Can a CCP accept a tokenised version of a bond it already accepts, before ESMA finishes this work?

The paper does not answer that question, and ESMA does not propose any interim position. The EMIR rule on changes to collateral requirements is Article 49, as amended by EMIR 3: Article 49(1) requires a CCP to review the models and parameters used for margin, default fund contributions, collateral requirements and other risk controls and to obtain validation before adopting any significant change, while a change the CCP considers not significant goes through the accelerated validation procedure in Article 49a. Under Article 49(1i), a change is significant where, among other conditions, a change to the methodology for valuing collateral or calibrating haircuts moves the total value of collateral significantly (point (h)) or the change could have a material effect on the CCP’s overall risk (point (i)). The draft RTS under Article 49(5) in ESMA’s final report (ESMA91-1505572268-4323, 9 October 2025) lists a haircut or valuation methodology change made to extend eligible collateral to a new asset class as meeting point (i). Whether accepting a tokenised form of an eligible asset is a change to models and parameters at all, and if so a significant one, for a given CCP is a point the call for evidence leaves open.

Will ESMA publish our response, and can parts of it stay confidential?

All contributions are published after the consultation closes unless the respondent asks otherwise. To keep part of a response out of publication, the submission must clearly and prominently mark that part, or the respondent can tick the box on the submission page asking for the whole response to be treated as confidential; a standard confidentiality statement in an email does not count as a request for non-disclosure. Personal data in an uploaded file is published as submitted, and ESMA’s decision not to disclose a response is reviewable by its Board of Appeal and the European Ombudsman.

Does the DLT Pilot Regime give a CCP a route to run collateral on DLT?

The DLT Pilot Regime defines DLT market infrastructures as DLT multilateral trading facilities, DLT settlement systems and DLT trading and settlement systems, which is the definition the paper repeats in Annex II. CCPs are not one of those categories, so the Regime does not give a CCP a route of its own. The paper lists the DLT Pilot Regulation, where applicable, among the frameworks that may become relevant for other participants in a tokenised collateral chain (paragraph 75). ESMA’s observation from pilot projects is limited to how they handled finality through contractual clauses, and it notes those projects do not concern CCP collateral management.

Are UK CCPs, or EU firms clearing at UK CCPs, covered?

The paper is about EU CCPs under EU EMIR. UK CCPs operate under the onshored UK regime, and the paper itself notes that the FCA and the Bank of England published a joint vision and call for input on tokenisation in wholesale markets in May 2026, covering prudential treatment, settlement arrangements and tokenised collateral. Two UK CCPs, LCH Limited and ICE Clear Europe, are recognised by ESMA as Tier 2 CCPs, and Article 25(2b) EMIR makes compliance with Article 16 and Titles IV and V of EMIR, which contain the collateral, investment, segregation and default rules in Articles 39 and 46 to 48, a condition of their recognition, subject to any comparable compliance ESMA grants under Article 25a. A group clearing at both EU and UK CCPs faces two separate processes with separate legal texts.

How does ESMA’s approach compare with the CFTC’s?

The paper cites CFTC staff guidance issued on 8 December 2025 (Letter No. 25-39) on the use of tokenised assets as collateral in derivatives markets, covering legal enforceability, segregation, custody and control, valuation and operational risk. The CFTC announced it alongside a digital assets pilot programme for tokenised collateral. ESMA’s paper gathers evidence and does not set out conditions under which a CCP may accept any specific tokenised asset.

How does this relate to ESMA’s draft RTS on guarantees and investment policy?

They are separate tracks that touch the same Delegated Regulation 153/2013. The guarantees consultation (ESMA91-1505572268-4513) closed on 30 April 2026 and set out draft RTS implementing the renewed mandate in Article 46(3) EMIR on public, public bank and commercial bank guarantees, together with targeted investment policy changes; ESMA said it expected to submit the final draft RTS to the Commission in Q4 2026. The tokenisation paper contains no draft RTS text, so anything it leads to would come later through a separate process.

Related Articles

• Guarantees as CCP Collateral: What ESMA’s Draft RTS Changes: the EMIR 3 guarantee mandate and the proposed changes to Delegated Regulation 153/2013 on concentration limits, investment policy and deposit arrangements.
• ECB Appia and Pontes: Tokenised Central Bank Money Settlement and the Future of European Payment Infrastructure: the Eurosystem’s two-track plan for settling DLT transactions in central bank money.
• Project Agora: Tokenised Wholesale Payments Reach Real-Value Testing: the BIS project on tokenised central bank reserves and commercial bank deposits.
• ESMA Joins the Global CCP Fire Drill: What the Default Simulation Means for Clearing Members and EMIR Reporting Teams: how a multi-CCP default simulation is scoped and what clearing members are asked to do.
• EMIR CCP Admission Criteria: The New RTS for Clearing Members: the risk-based admission elements CCPs must reflect for financial and non-financial clearing members.

Key Takeaways

• Classify every live or planned tokenised collateral arrangement as digital twin, native or hybrid before drafting, so each answer can name the solution it covers.
• For a digital twin, write down which record prevails on a discrepancy and how long the custodian or CSD leg adds to a default liquidation.
• Get a governing-law opinion on whether wallet or key control amounts to FCD possession or control before asserting equivalence with traditional collateral.
• Record two timestamps per tokenised transfer, ledger confirmation and legal irrevocability, and identify any override or reversal function that sits between them.
• Assess each tokenised cash candidate by redemption route, issuer credit and legal ability to discharge a cash obligation before proposing it for variation margin.
• Check whether a back-up clearing member could take over tokenised client collateral without first being onboarded to the platform.
• Where a provision assumes a settlement system operator, an account or a custodian, cite it in the Q28 answer with the narrowest fix.

Sources and References

• ESMA, Call for evidence on the CCP collateral tokenisation, consultation page (open 9 October 2026 to 15 January 2027): esma.europa.eu
• ESMA, Call for evidence: CCP collateral tokenisation, ESMA91-1505572268-4934, 9 October 2026: PDF
• ESMA, Reply form to the call for evidence on CCP collateral tokenisation, ESMA91-1505572268-5028: DOCX
• ESMA, Press release: ESMA seeks evidence on the use of tokenised collateral in central clearing, ESMA91-1505572268-5023, 9 October 2026: PDF
• ESMA, List of third-country central counterparties recognised to offer services and activities in the Union, ESMA70-152-348, updated 30 June 2026: PDF
• Regulation (EU) No 648/2012 (EMIR), Articles 25, 25a, 39, 46, 47, 48 and 49: EUR-Lex
• Regulation (EU) 2024/2987 (EMIR 3), amending Articles 46, 48 and 49 of EMIR: EUR-Lex
• Commission Delegated Regulation (EU) No 153/2013 (RTS on requirements for CCPs): EUR-Lex
• ESMA, Consultation Paper on draft RTS amending Delegated Regulation 153/2013 (guarantees as collateral, investment policy, highly secure deposit arrangements), ESMA91-1505572268-4513, 23 February 2026: PDF
• ESMA, Final Report on draft RTS under Article 49(5) of EMIR on the conditions and list of documents for validation of changes to models and parameters, ESMA91-1505572268-4323, 9 October 2025: PDF
• ESMA, Questions and Answers on EMIR implementation (CCP Answer 8 on segregation): PDF
• Directive 2002/47/EC on financial collateral arrangements: EUR-Lex
• Directive 98/26/EC on settlement finality in payment and securities settlement systems: EUR-Lex
• Regulation (EU) 2022/2554 (DORA): EUR-Lex
• Regulation (EU) 2022/858 (DLT Pilot Regime): EUR-Lex
• Regulation (EU) 2023/1114 (MiCA): EUR-Lex
• Regulation (EU) No 909/2014 (CSDR): EUR-Lex
• ECB, Pontes: ecb.europa.eu
• CFTC, press release 9146-25, Digital Assets Pilot Program for Tokenized Collateral in Derivatives Markets, 8 December 2025: cftc.gov
• CFTC Staff Letter No. 25-39 (guidance on tokenized collateral), 8 December 2025: cftc.gov

Before 15 January 2027: the evidence a response needs on file

ESMA has kept the eligible asset list out of scope and put the mechanics in. The questions that will shape any follow-up are the ones only operators can answer with data: how long a tokenised asset takes to become cash after a default, which record wins when the token and the custodian disagree, and which provision of EMIR, Delegated Regulation 153/2013, the FCD or the SFD assumes an account or an intermediary that a ledger does not have.

Comments close on 15 January 2027. The document to produce before then, for each tokenised arrangement a firm runs or plans, is a default-path timeline from posting to usable cash, with the legal finality point and every critical dependency marked on it.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.