France’s AMF Lists Ripple Payments Europe Under MiCA With Three Services

Direct answer: the AMF record is a service passport, not an XRP approval

France’s financial regulator lists Ripple Payments Europe S.A. as a Luxembourg-authorized MiCA crypto-asset service provider using the passporting route, with three services named: crypto-to-fiat exchange, crypto-to-crypto exchange, and client transfer services. The record supports regulated cross-border activity. It does not approve XRP, RLUSD, or a specific Ripple product for every European customer.

The record is the most useful primary check on Ripple’s broader July announcement. On July 6, Ripple said its Luxembourg Crypto Asset Service Provider authorization completed its MiCA requirements and made its end-to-end regulated crypto payments product available to financial institutions, corporates, and businesses across all 30 European Economic Area countries. CoinDesk independently reported the upgrade the same day. Those statements describe the company’s regional operating position. The AMF entry shows what that position looks like in one destination market.

Ripple’s August 5 follow-up frames the authorization as a platform for scaling stablecoin payments and other digital-asset services. That is a company strategy statement, not a regulator finding about XRP usage. The strongest confirmed conclusion is narrower: Ripple has a Luxembourg MiCA authorization, Ripple Payments Europe is listed for passported services in France, and the public French record does not disclose customers, volumes, asset-level usage, or a commercial rollout timetable.

Section sources[1][2][6]

What France’s official record actually says

The AMF page dated July 9, 2026 identifies the legal entity as Ripple Payments Europe S.A. It labels the status as a MiCA-licensed CASP, gives the licensing country as Luxembourg, and shows the licensing number as N/A, Passport. That wording matters. France is recording a cross-border authorization rather than presenting a separate French license number for this entity.

The page names three authorized services: exchange of crypto-assets for funds, exchange of crypto-assets for other crypto-assets, and provision of transfer services for crypto-assets on behalf of clients. It also displays June 29, 2026 as the licensing date, then explains that this date is the starting date on which the entity intends to provide crypto-asset services in France. The page does not publish a customer list, transaction minimum, asset volume, or product-level service terms.

This is why the phrase three services is more precise than saying that France approved Ripple’s entire digital-asset business. The public entry does not list custody, investment advice, portfolio management, or stablecoin issuance as part of the France passport record. That absence should not be stretched into a claim that Ripple lacks any other authorization elsewhere. It means only that those categories are not named on the regulator page reviewed for this report.

The legal-entity distinction is equally important for readers. Ripple is the group named in the company announcement, while Ripple Payments Europe S.A. is the entity appearing in the French record. A customer, institution, or analyst should match the contracting entity, service category, and jurisdiction before treating a general Ripple statement as proof that a particular product is available.

Section sources[1][2]

Why Luxembourg is the gateway and July’s transition date matters

The Luxembourg connection is not incidental. The CSSF’s CASP overview says a provider authorized in Luxembourg may provide services in other EU Member States or EEA states after completing the required notification procedures. In plain terms, the home authorization and the destination-market notification work together. The AMF’s France entry is a concrete example of that structure, not a new standalone French authorization.

Ripple’s July 6 release says the CSSF authorization allows its regulated crypto payments product to serve institutions, corporates, and businesses across all 30 EEA countries. CoinDesk’s independent report also described the approval as enabling operations across the EU and EEA. The relevant uncertainty is not whether passporting exists. It is how much of Ripple’s described product suite is actually offered, to which counterparties, and under what customer and asset restrictions in each country.

The timing is material because the CSSF said the EU transition period for virtual asset service providers ended on July 1, 2026. Its consumer notice says providers could no longer offer crypto-asset services without CASP authorization and that unauthorized providers had to wind down their EU activity in an orderly way. The same notice tells consumers to check the provider’s official name, authorization, and the ESMA or CSSF registers.

For institutions, the practical change is a clearer compliance path after the transition deadline. It is not a guarantee that onboarding is immediate, that every service is available in every EEA state, or that a passport eliminates ordinary checks around financial crime controls, custody, suitability, complaints, or local implementation. Those are operational questions that belong to the entity and product documents, not to the headline license alone.

Section sources[4][3][1][6]

How the authorization touches XRP and RLUSD without guaranteeing demand

Ripple’s July 6 press release says its solutions span payments, custody, liquidity, and treasury management, and describes RLUSD and XRP as assets that underpin those solutions. Its August 5 follow-up places the CASP milestone inside a strategy for stablecoin payments, cross-border settlement, and institutional digital-asset services. Those are Ripple’s stated commercial uses, and they explain why the license matters to the XRP ecosystem.

The AMF record is more limited. It names service categories and a legal entity. It does not say that XRP must be used in a French payment, that RLUSD is available to every French customer, that a specific bank has onboarded, or that any transaction volume has been generated. The record also does not publish an asset list or an XRP settlement ratio. A service-provider authorization should therefore not be read as an asset endorsement or a demand report.

Bounded inference: a passported CASP authorization can reduce one regulatory barrier for a firm seeking to offer crypto-asset services to eligible European counterparties. It may make regulated integration easier to evaluate than an unlicensed alternative. That does not establish the economics of the integration. A payment can use fiat, RLUSD, XRP, another crypto-asset, or several rails, depending on the product, corridor, counterparty, and risk controls.

This distinction is especially relevant after a series of XRP market-structure stories that treat institutional access as a proxy for token demand. The authorization is evidence of operating permission. It is not evidence of XRP purchases, liquidity demand, price appreciation, or a change in XRP’s legal classification. Those claims would require separate records, such as product terms, customer disclosures, on-chain settlement evidence, or audited flow data.

Section sources[2][5][1][7]

Implications for European institutions, customers, and XRP readers

For European financial institutions, the public record is a due-diligence starting point. The institution should identify whether it is contracting with Ripple Payments Europe S.A. or another Ripple entity, then confirm which of the three AMF-listed services is relevant. It should also ask for jurisdiction coverage, onboarding criteria, custody arrangements, execution rules, complaints handling, and the assets or payment rails supported by the specific product.

For European customers, the license is useful because it makes the provider’s name and home authority easier to check. The CSSF specifically advises customers to consult official provider information, the ESMA register, and national registers. A customer should not assume that a company’s presence in a regulator’s list means every wallet, stablecoin, exchange route, or payment product is offered to that customer. Availability depends on the authorized entity, service, jurisdiction, and terms.

For developers and counterparties, the most important integration boundary is between a licensed service and the underlying asset. A compliant API or payment rail still needs explicit rules for asset support, account eligibility, transfer restrictions, settlement finality, reconciliation, and failure handling. The AMF record does not replace those technical and legal documents. It tells a developer that a regulated service path exists, not how to implement it safely.

For XRP holders and market analysts, the signal is institutional rather than immediate market data. Ripple has added a European regulatory permission that could support future payments and digital-asset services. The next question is whether those services produce measurable activity involving XRP, RLUSD, or neither. Until a primary customer, product, or flow record answers that question, the defensible conclusion is regulatory access, not adoption.

Section sources[1][3][4][5]

Uncertainty label: confirmed facts, bounded inference, and open questions

Confirmed facts: the AMF’s July 9 public entry lists Ripple Payments Europe S.A. as a Luxembourg-authorized MiCA CASP passport in France. It names three service categories and says June 29 is the intended start date for services in France. Ripple announced the underlying Luxembourg authorization on July 6, and the CSSF’s public guidance explains the European passport framework and the end of the transition period.

Bounded inference: the record supports Ripple’s ability to pursue regulated cross-border crypto-asset services through a Luxembourg home authorization and French notification. That should lower uncertainty about the legal route for an eligible institution. It does not show that the service is already operating at scale, that every EEA country has identical availability, or that the activity is economically tied to XRP.

Unresolved questions: the sources reviewed do not disclose Ripple Payments Europe’s French customer count, transaction volume, revenue, supported asset list, XRP share of settlement, RLUSD distribution terms, or the names of institutions using the passported services. The AMF page also does not show whether additional service notifications or product permissions have been added after the record was published. Those gaps are not evidence of failure. They are the reason the authorization should be reported as a regulatory milestone rather than a measured adoption outcome.

The editorial bottom line is simple. Ripple’s Luxembourg MiCA authorization has moved from a company announcement into a visible French regulator record, but the record is narrower than the ecosystem’s broadest interpretation. It confirms a service passport for a named entity and three categories. The next proof point must come from actual products, customers, flows, and asset-level disclosures.

Section sources[1][2][4][6]