Skip to main content

RLUSD MiCA Compliance: Ripple's Path to EU Approval in 2026

Where Ripple's USD stablecoin stands with EU regulators, the likely EMI-license route through an EU subsidiary, and how the path compares to USDC, EURC, and USDP authorization.

Written by Eco


Ripple's USD stablecoin (RLUSD) launched on December 17, 2024 under a New York Department of Financial Services (NYDFS) limited-purpose trust charter held by Standard Custody & Trust Company, a Ripple subsidiary. The token has grown past $300M in circulation as of Q1 2026 (per DeFiLlama), but it is not yet authorized under the EU's Markets in Crypto-Assets Regulation (MiCA). This article walks through where RLUSD stands with European regulators, how Ripple's authorization path likely runs through a MiFID-licensed or e-money-licensed EU subsidiary, and how that path compares to USDC and EURC, which Circle cleared in July 2024.

What Is RLUSD and Who Issues It?

RLUSD is a USD-pegged stablecoin issued by Standard Custody & Trust Company, a Ripple-owned trust chartered by NYDFS. It launched December 17, 2024 on Ethereum and the XRP Ledger, with reserves held in cash deposits and short-dated US Treasuries. Audits are published monthly. It is not currently authorized under MiCA.

Standard Custody received its NYDFS limited-purpose trust charter in 2022, which Ripple acquired in June 2024 specifically to issue RLUSD under regulated custody. Reserves are attested monthly by an independent accounting firm and published on Ripple's transparency page. The token is denominated in US dollars and redeemable 1:1 for institutional counterparties holding direct redemption agreements with Standard Custody. Retail holders redeem through exchanges and market makers rather than the issuer.

Initial distribution went through Uphold, Bitstamp, MoonPay, Bullish, Independent Reserve, CoinMENA, and Archax. Notably absent from the launch list: most large EU-domiciled exchanges, which cited MiCA uncertainty as the reason for waiting.

How Does MiCA Treat USD-Denominated Stablecoins?

MiCA classifies USD-pegged stablecoins as "e-money tokens" (EMTs) when they reference a single fiat currency. To offer an EMT to EU users, the issuer must hold either an Electronic Money Institution (EMI) license or a credit institution license in an EU member state, plus publish a MiCA-compliant white paper notified to the home regulator. Non-EU issuers cannot self-authorize. The EMT rules took effect June 30, 2024.

This is the same rule that pushed USDT off most regulated EU exchanges in December 2024 and that Circle satisfied by securing an EMI license in France through the Autorité de Contrôle Prudentiel et de Résolution (ACPR) in July 2024, covering both USDC and EURC. Per the ESMA MiCA register, only issuers with an authorized EU entity appear in the EMT list. RLUSD is not listed as of May 2026.

Daily transaction caps also bite. MiCA Article 23 imposes a cap of 1M transactions or €200M per day for "significant" non-euro EMTs used as a means of exchange within the EU. Once a USD EMT crosses that threshold, the issuer must restrict EU usage, an unusual structural constraint that Tether cited when declining to seek MiCA authorization.

What Is Ripple's Likely MiCA Authorization Path?

Ripple has signaled it will pursue MiCA authorization through an EU-domiciled subsidiary holding either an EMI license or a credit institution license, rather than passporting from an existing entity. As of Q1 2026, Ripple has not publicly named the target member state, but Ireland and Luxembourg are the most-discussed candidates given Ripple's existing operations there. No authorization date has been announced. The path is pending.

Ripple already holds a Central Bank of Ireland authorization for its payments business (acquired through the Metaco and Standard Custody integration work) and operates a Luxembourg entity. Either jurisdiction is a plausible host for an EMI license application. Reuters reported in October 2024 that Ripple was "exploring MiCA authorization" for RLUSD but did not name the regulator (see Reuters coverage).

Industry observers expect the application timeline to mirror Circle's: roughly 12 to 18 months from filing to authorization, given the white-paper review, reserve-segregation requirements, and home-regulator coordination through ESMA. If Ripple filed in early 2025, an authorization decision could land in 2026. Treat any specific date as speculative until Ripple or the home regulator confirms.

Where Can EU Users Access RLUSD Today?

EU residents currently cannot legally hold RLUSD on a MiCA-regulated exchange. The token is not listed on Bitstamp EU, Kraken EU, Coinbase Europe, or Bitvavo for retail customers. Some EU users access RLUSD through self-custody wallets and decentralized exchanges on Ethereum or the XRP Ledger, but regulated on-ramps and off-ramps are unavailable until Ripple secures MiCA authorization.

Bitstamp, despite being one of the original RLUSD launch venues globally, restricts the pair from its EU-licensed entity. Uphold offers RLUSD outside the EEA. This creates a workaround pattern familiar from the USDT delisting wave: EU users either move to non-EU venues, hold via self-custody, or wait. None of those options give institutional treasurers the reporting and audit trail they need to run RLUSD as a working-capital instrument.

How Does RLUSD's MiCA Path Compare to USDC, EURC, and USDP?

USDC and EURC are fully MiCA-authorized through Circle's French EMI license, with both tokens listed on the ESMA EMT register since July 2024. USDP (Pax Dollar, issued by Paxos) gained MiCA authorization through Paxos's Finnish entity in 2025. RLUSD is pending. The table below summarizes each issuer's authorization route, host regulator, and EU exchange availability.

Stablecoin

Issuer

MiCA Status

EU Authorization Route

Major EU Exchange Listings

RLUSD

Standard Custody (Ripple)

Pending as of May 2026

Expected EMI license via EU subsidiary, jurisdiction not yet announced

None (retail)

USDC

Circle

Authorized July 2024

French EMI license (ACPR)

Coinbase EU, Bitstamp EU, Kraken EU, Bitvavo

EURC

Circle

Authorized July 2024

French EMI license (ACPR)

Coinbase EU, Bitstamp EU, Kraken EU, Bitvavo

USDP

Paxos Issuance Europe Oy

Authorized 2025

Finnish EMI license (FIN-FSA)

Limited; expanding through 2026

The structural difference: Circle and Paxos both established a single EU entity that issues a euro-denominated version (EURC, EURCV) and a passportable USD version under one EMI license. Ripple does not yet have an announced euro stablecoin, so its EU entity will likely launch USD-only at first. That mirrors USDP's early posture.

What Reserve and Disclosure Requirements Apply Under MiCA?

MiCA requires EMT issuers to back tokens 1:1 with reserves held in segregated accounts at EU credit institutions, with at least 30 percent held as cash deposits and the remainder in highly liquid, low-risk instruments such as short-dated sovereign bonds. Issuers must publish quarterly reserve attestations, a MiCA white paper notified to the home regulator, and ongoing disclosure of any material changes. RLUSD's current monthly attestations already meet the cadence, but reserve location and counterparty mix would need restructuring.

RLUSD's current reserves sit primarily with US-based custodians and short-dated US Treasuries, which would need partial relocation to EU credit institutions to satisfy the segregated-account rule. Standard Custody is not an EU credit institution, so a parallel reserve pool held by an EU-licensed Ripple entity would be the most likely structure. Circle solved this by holding EURC and the EU-allocated portion of USDC reserves at French and Belgian banks, per the Circle transparency reports.

Why Does MiCA Compliance Matter for Ripple's Business?

MiCA authorization unlocks the regulated EU exchange market, payment institution partnerships, and institutional treasury adoption, three segments where Ripple competes directly with Circle on payments and remittance corridors. Without MiCA, RLUSD cannot serve as a settlement asset for EU-domiciled financial institutions using Ripple Payments, undermining the original strategic rationale for issuing a stablecoin.

Ripple Payments (formerly On-Demand Liquidity) routes cross-border value through digital assets, and Ripple has stated RLUSD is intended to complement XRP as a settlement leg. The EU corridor is one of Ripple's largest payments markets by volume, so a multi-year MiCA gap effectively forces EU counterparties to settle in USDC or wait. That is the competitive pressure driving the authorization push.

How Does Eco Route Stablecoins Across MiCA-Compliant and Non-Compliant Tokens?

Eco Routes treats MiCA-authorized stablecoins (USDC, EURC, USDP) and non-authorized USD stablecoins (USDT, RLUSD as of May 2026) as separately routable assets across the 15 chains it supports. When an EU counterparty requires a MiCA-compliant settlement leg, applications using Eco can route a transfer through USDC even when the originating asset is RLUSD or USDT on another chain.

This matters for any application serving both EU and non-EU users on the same payment rail. The routing logic respects the regulatory perimeter, swapping into a MiCA-authorized asset before the EU leg of a multi-hop transfer, then settling the user's preferred unit of account at destination. Eco's intent-based settlement model is designed for exactly this kind of asset-substitution requirement.

Methodology and Sources

This article draws on the Ripple RLUSD launch announcement (December 17, 2024), the NYDFS limited-purpose trust charter framework, the MiCA regulation text (Articles 16 through 47 covering EMTs and ARTs), the ESMA MiCA EMT register as of May 2026, Circle's July 2024 EMI authorization disclosure through ACPR, Paxos Issuance Europe Oy's 2025 FIN-FSA authorization, and Reuters and Bloomberg coverage of Ripple's EU authorization plans. Reserve composition figures are drawn from Standard Custody's monthly attestation reports. Where authorization dates remain unconfirmed for RLUSD, claims are marked "pending" or "as of [date]."

Primary sources cited:

Related Reading

Did this answer your question?