DriveWealth is bringing Ripple’s RLUSD stablecoin settlement technology on the XRP Ledger into its brokerage infrastructure, with Europe expected to be the first market before a possible expansion into the United States. The companies announced the collaboration on October 15, 2026.
DriveWealth develops brokerage infrastructure for fintech firms, digital wallet providers and financial institutions that offer customers access to U.S. markets. Its technology supports investment services for more than 100 partners globally, potentially providing a broad channel for distributing the new RLUSD-powered services.
Despite this reach, the partnership does not automatically mean RLUSD will see widespread adoption. The companies have yet to reveal which DriveWealth partners will participate, whether any integrations are already live or whether the service will eventually be offered throughout its entire partner network.
The initiative is designed to address delays associated with funding brokerage accounts through traditional banking systems. International customers can encounter transfer processing times and bank cutoff restrictions that delay access to their money. Stablecoin transfers that can be converted into cash almost immediately could make account funding more efficient and reduce reliance on conventional bank wires.
Ripple and DriveWealth Expand Settlement, Payments and Custody Plans
The settlement infrastructure will rely on RLUSD operating on the XRP Ledger, alongside Ripple’s minting and burning capabilities. DriveWealth says the integration will enable clients to fund their accounts and manage collateral through stablecoins that can be converted into cash in near real time, rather than waiting for traditional bank transfers to clear.
The companies are also incorporating Ripple Payments into the partnership to support cross-border payment acceptance from DriveWealth’s global partners. This component is intended to simplify incoming transfers and improve the movement of funds across international markets.
Digital-asset custody is another area under development. DriveWealth and Ripple are working on custody services in Europe, with the possibility of extending availability to additional markets later. Their plans include moving treasury and custody infrastructure onto Ripple’s network, giving clients a real-time overview of their dollar balances, stablecoins and cryptocurrency holdings, along with the ability to transfer value between these assets.
Potential equity financing services remain at an exploratory stage. DriveWealth and Ripple Prime are examining possible opportunities through Ripple Prime’s Delta One business. Unlike the settlement and payment integrations already announced, no confirmed equity financing rollout has been disclosed.
Europe Leads the Planned RLUSD Settlement Rollout
The companies intend to introduce settlement services in Europe before considering an expansion into the United States. Digital-asset custody will also begin in Europe, with other markets potentially added over time. Ripple says its regulatory footprint includes more than 85 licenses.
DriveWealth CEO Naureen Hassan said the company wants to ensure its funding infrastructure keeps pace with its extended trading capabilities.
“We’ve already enabled 24/5 trading; now we need the funding to match, so clients can move with the markets instead of waiting for them,” Hassan said.
The companies have not announced a specific launch date, transaction-volume projections or a confirmed list of participating partners. Consequently, the timing of the first live deployment and the scale of adoption remain unclear.
The partnership was also scheduled to be discussed at a Ripple Swell fireside chat in New York City on Wednesday, October 28.
For RLUSD and the XRP Ledger, the collaboration could create another route into institutional financial services by connecting stablecoin settlement with brokerage funding, cross-border payments and digital-asset custody. The actual impact will depend on implementation progress, partner participation and measurable usage once the services become operational.
