XRP

Ripple’s MiCA win is not a full license yet – Here’s what it still has to prove

Regulation & PolicyJune 28, 2026·5 min read

Ripple’s preliminary European approval marks a critical checkpoint rather than full authorization, requiring the company to demonstrate operational and governance capabilities across its payment, custody, and stablecoin services within the next phase of MiCA compliance. For institutional investors and counterparties, this conditional status means regulatory uncertainty persists until the Luxembourg entity proves it can independently run these services under European supervision.

  • Ripple secured a Green Light Letter from Luxembourg’s CSSF on June 23, a conditional preliminary approval before the July 1 MiCA grandfathering deadline.
  • The company must now prove its Luxembourg entity meets capital requirements, governance standards, and operational controls for payments, custody, transfer, and stablecoin services separately.
  • ESMA guidance flags Ripple’s simultaneous operation of stablecoin issuance and crypto services as higher-risk, likely to face intensified supervisory scrutiny during the proof phase.
  • June 23 Date Ripple received Green Light Letter from Luxembourg CSSF regulator
  • $95B+ Volume processed by Ripple’s payments network against broader operational scale
  • July 1 MiCA grandfathering deadline when full authorization becomes mandatory across EEA

Ripple crossed a regulatory threshold on June 23 when Luxembourg’s Commission de Surveillance du Secteur Financier (CSSF) issued a Green Light Letter recognizing the company as a Crypto-Asset Service Provider applicant. The letter signals preliminary approval in principle, but it is neither a full license nor a final authorization.

Combined with the E-Money Institution license Ripple finalized in February in the same jurisdiction, the company now sits within MiCA’s perimeter before the July 1 deadline that closes the European Union’s grandfathering window and makes full authorization mandatory across the 30-state European Economic Area.

For a company that operates more than 75 licenses globally and has moved over $95 billion through its payments infrastructure, this appears to be another institutional checkpoint. Yet the Green Light Letter is conditional, and the conditions are substantial.

Ripple must now prove, service by service, that its Luxembourg-based entity can independently operate the payments, custody, transfer, and stablecoin businesses it has requested permission to run. Global track record does not substitute for local operational capacity under MiCA’s framework.

Luxembourg Entity Must Stand Alone on Capital, Governance, and Business Planning

The distinction that matters most to regulators is that MiCA scrutinizes the local company, not Ripple’s worldwide operations. Article 62 of the regulation requires applicants to specify each service they intend to offer, since permission to move and hold cryptocurrency is a separate regulatory grant from permission to operate a trading venue or issue stablecoins.

The CSSF will also demand a three-year business plan that models both lean years and profitable ones, not just upside scenarios.

Capital requirements pose a concrete hurdle. The European Securities and Markets Authority (ESMA) expects the Luxembourg entity to hold its own funds or maintain insurance sufficient to cover the services it offers. Ripple’s group balance sheet and consolidated capital position do not answer the question of whether the subsidiary standing alone meets that test.

The local company cannot simply rely on parent company reserves; it must demonstrate independent financial adequacy.

Governance is where the CSSF will apply the most rigorous scrutiny, and it directly shapes how Ripple staffs and operates in Europe. ESMA has instructed national regulators that no applicant is low-risk by default, and a licensed firm must run itself inside the EU with real people making real decisions.

That principle exists to prevent shell operations where the office exists on paper while decision-making and operations happen offshore.

In practice, Ripple must name a management team with genuine authority, assign a CEO who devotes substantially all of their time to the Luxembourg entity, and observe strict limits on how much operational responsibility can be delegated back to the San Francisco parent before the entity is deemed hollow.

Operational Evidence and Controls Over Stablecoin and Custody Services

Beyond governance structure, Ripple faces a detailed operational evidence checklist. The CSSF will conduct background checks on managers and major shareholders, map the control structure to identify who ultimately owns and directs the company, and require a plan for keeping client assets entirely segregated from Ripple’s own balance sheet.

Wallet security, cryptographic key handling, and asset recovery procedures must all be documented and approved by supervisors before they are deployed.

The stablecoin overlay presents the most complex challenge. ESMA has explicitly flagged one combination as higher-risk: a company that simultaneously issues a stablecoin and provides crypto asset services. Ripple fits that profile precisely.

RLUSD, Ripple’s USD-backed stablecoin, exists alongside the company’s payment, custody, and exchange functionalities. This overlap heightens conflict-of-interest risk from ESMA’s perspective and increases the probability of intensive supervisory questioning during the proof phase.

Stablecoin issuers face separate reserve requirements under MiCA Article 41, obligating them to hold adequate euro reserves or equivalent backing to redeem every token issued.

When a single entity issues the stablecoin and also provides custody or trading services, supervisors must verify that stablecoin reserves are genuinely ring-fenced and cannot be commingled with operational capital or customer assets.

For Ripple, proving this operational separation across RLUSD, its euro custody business, and its payment services will be central to moving from Green Light Letter to full authorization.

Path to Full Authorization and Timeline Uncertainty Ahead

The July 1 deadline gave Ripple a window to escape the mandatory full application process by holding preliminary approval. The Green Light Letter achieves that by treating the company as a MiCA applicant at the moment the grandfathering period closes. However, preliminary approval does not equal authorization, and the proof phase now begins in earnest.

The CSSF has not published a specific timeline for moving from Green Light Letter to full authorization, creating regulatory uncertainty for institutional users and counterparties.

Ripple’s path from here depends on delivering evidence that its Luxembourg operations meet ESMA standards for capital adequacy, governance independence, and operational controls, all while managing the regulatory complexity of operating a stablecoin alongside payment and custody services in the same entity.

The company must demonstrate that its local team has genuine decision-making authority, that reserves are properly held, and that client assets are protected. For institutional investors and settlement partners, this proof phase determines whether Ripple’s European authorization becomes solid ground or remains conditional.

The CSSF’s next move, formal approval, conditional approval with modifications, or a request for additional documentation, will likely emerge over the coming months and will signal how demanding the regulator intends to be on operational and governance evidence, particularly around the stablecoin-plus-services combination ESMA flagged as higher-risk.

Get this in your inboxThe Crypto Coin Show newsletter covers the policy and market moves institutional crypto investors are pricing in.

Subscribe