DriveWealth Adopts RLUSD for Settlement and Cross-Border Payments

Brokerage infrastructure firm DriveWealth has integrated Ripple's RLUSD stablecoin into its settlement and collateral-funding stack, using the XRP Ledger to move money around the clock. The partnership, announced on 14 October 2026, launches first in Europe and is set to extend to the United States, marking a significant step in embedding stablecoin accounting workflows into regulated brokerage operations. For accounting firms, auditors, and CFOs already grappling with digital asset accounting software choices, the move raises concrete questions about how stablecoin settlement flows should be recorded, controlled, and reported.

What the DriveWealth and Ripple Deal Actually Covers

The partnership is broader than a single payment rail. DriveWealth is integrating three distinct capabilities from Ripple: stablecoin settlement using RLUSD, cross-border payment infrastructure, and digital asset custody services. The firms are also exploring equity financing through Ripple Prime, which would extend the relationship into balance-sheet territory beyond pure payments.

Around-the-clock collateral funding

The core operational change is collateral management. DriveWealth clients will be able to fund and manage collateral accounts using RLUSD, with those balances converting to cash in near real time. DriveWealth's CEO Naureen Hassan framed the problem directly: the firm already offers 24/5 trading, and the funding infrastructure needs to match. Stablecoins sitting idle overnight or over a weekend represent an operational drag that this integration is designed to remove.

That is a meaningful shift. Traditional settlement cycles leave capital stranded at weekends and outside banking hours. A stablecoin-denominated collateral account that converts on demand compresses that idle period dramatically, though it also means treasury teams need controls that operate continuously rather than within a standard business-day window.

Cross-border settlement starting in Europe

The geographic sequencing is deliberate. Europe goes first, likely because the regulatory environment under MiCA provides a clearer framework for stablecoin use in settlement than the still-evolving US picture. Ripple's SVP of stablecoins Jack McDonald noted that what started as a specific cross-border settlement challenge quickly revealed a wider opportunity across trading, custody, and settlement infrastructure combined.

The phased rollout gives both firms time to embed compliance and reporting workflows in one jurisdiction before scaling. For European counterparties, that means stablecoin settlement with DriveWealth clients could be live sooner than many firms have planned for in their own treasury roadmaps.

RLUSD's Growing Institutional Footprint

This deal does not sit in isolation. Earlier in the same week, Standard Chartered launched RLUSD custody services on the XRP Ledger, a development covered in our Standard Chartered RLUSD custody on the XRP Ledger analysis. Ripple also secured $150 million in financing earlier in 2026 to support institutional stablecoin adoption. The pattern is clear: RLUSD is being positioned as an institutional-grade settlement asset, not a retail payments token.

Why brokerage infrastructure matters here

DriveWealth is not a retail broker in the conventional sense. It provides the underlying brokerage infrastructure that other fintechs and neobrokers build on top of. When DriveWealth embeds stablecoin settlement into its rails, the downstream effect reaches every firm using those rails. That amplifies the accounting and operational implications considerably. A fintech that white-labels DriveWealth's infrastructure may find stablecoin flows appearing in its own ledger without having made an explicit decision to adopt stablecoins itself.

Stablecoin Accounting Implications for Finance Teams

The DriveWealth integration crystallises several accounting questions that firms have been able to defer until now. As stablecoin settlement moves from pilot to production infrastructure, those deferrals become costly.

Classification: cash equivalent or financial asset?

Under IFRS, a stablecoin held for settlement purposes is not automatically a cash equivalent. IAS 7 requires that a cash equivalent be readily convertible to a known amount of cash and subject to an insignificant risk of changes in value. A stablecoin that converts to cash in near real time via an integrated platform comes closer to meeting that test than one held speculatively, but the conversion mechanism, any gate or delay conditions, and the credit risk of the issuer all affect the classification. Firms using RLUSD for collateral funding need a documented accounting policy before the first transaction settles.

Under US GAAP, the FASB's ASC 350-60, which introduced fair-value measurement for crypto assets held by entities, would generally apply to stablecoin holdings unless they qualify for a specific exception. Even where RLUSD trades at a stable dollar peg, the standard requires fair value measurement unless the asset meets the definition of cash or a cash equivalent under ASC 230. Given that RLUSD is not legal tender, most firms will account for it as an intangible or financial asset, depending on their specific facts.

Settlement timing and recognition

Near-real-time conversion creates its own recognition challenge. If a stablecoin is received as settlement and converts to cash within seconds, is the transaction a stablecoin receipt followed by a disposal, or simply a cash receipt? The answer affects whether a gain or loss on conversion is recognised, how the transaction is presented in the cash flow statement, and what disclosure is required. Firms operating across multiple standards need consistent policies, particularly if European entities are settling first while US entities come online later.

Treasury controls for 24/7 settlement cycles

Most treasury control frameworks assume batch processing within banking hours. An around-the-clock stablecoin settlement rail breaks that assumption. Authorisation limits, reconciliation cadence, and counterparty exposure monitoring all need to be redesigned for continuous settlement. Internal auditors reviewing DriveWealth-connected entities should test whether existing controls actually operate outside normal business hours or whether there is an unmonitored window overnight and at weekends.

The FSB cross-border stablecoin risk report and what it means for treasury teams sets out the systemic risks the Financial Stability Board has identified in this area, including liquidity mismatches and cross-border contagion channels that are directly relevant to firms using stablecoin-denominated collateral accounts at scale.

AML and Compliance Considerations

Travel Rule obligations on stablecoin transfers

Cross-border stablecoin transfers on the XRP Ledger are subject to Travel Rule obligations in both the EU (under TFR, the Transfer of Funds Regulation) and in the US (under FinCEN rules). DriveWealth and Ripple will need to ensure that originator and beneficiary information travels with each RLUSD transfer above the applicable thresholds. For firms using DriveWealth's infrastructure, the practical question is whether their own Travel Rule data flows integrate cleanly with the XRP Ledger's on-chain settlement, or whether there is a gap between the blockchain record and the compliance data attached to it.

Collateral account monitoring

Using stablecoins to fund collateral accounts introduces a new vector for transaction monitoring teams. The near-real-time conversion feature means that a stablecoin transfer and its conversion to cash may appear as two separate ledger entries, each needing to be assessed for suspicious activity. Compliance teams should confirm with their vendor that the monitoring system is configured to link these legs rather than treating them independently.

What Firms Should Do Before the US Rollout

The European launch gives US-facing firms a window. That window should be used to establish accounting policies rather than scramble when the US integration goes live. Four actions stand out.

Document your stablecoin accounting policy now

Whether your firm holds RLUSD directly or receives it as settlement through a downstream provider, you need a written policy covering classification, measurement, derecognition, and presentation before the first transaction. Waiting until the US rollout is announced removes the time needed for audit committee approval and systems configuration.

Map your exposure to DriveWealth's infrastructure

If you operate a neobroker, trading app, or fintech platform that uses DriveWealth's rails, stablecoin settlement flows may already be in scope. Map that dependency and confirm with DriveWealth what data and transaction records will be available for your own reconciliation and reporting processes. Robust digital asset accounting software should be able to ingest XRP Ledger transaction data and match it against your internal records.

Review treasury policy authorisation limits

If existing treasury policy caps overnight digital asset exposure, a 24/7 stablecoin settlement rail may require board or audit committee sign-off to increase those limits or to create a specific carve-out for near-cash stablecoin instruments. Do not assume that operational adoption precedes policy approval.

Brief your auditors early

Auditors assessing crypto asset balances and stablecoin flows under emerging guidance will need to understand the conversion mechanism, the counterparty chain, and the classification rationale. Early briefing avoids year-end surprises and gives your external auditors time to plan appropriate procedures, especially if this is the first year stablecoin settlement appears on the balance sheet.

Source: The Block