Coinbase Adds RLUSD on Three Networks, With a Separate Collateral Plan

What Coinbase’s RLUSD launch changes

Coinbase added Ripple USD (RLUSD) on October 28, 2026, giving customers in supported regions trading access and transfers across XRP Ledger, Base and Ethereum. Its launch notice places Global Exchange collateral support in a later phase. The practical change is wider distribution, while network compatibility and account permissions still require verification.

Confirmed: Coinbase’s dated announcement names its retail app, Coinbase Exchange and Coinbase Prime. Ripple published a matching release, and Reuters independently reported the listing that day. This is an explainer of that documented launch, not a claim that Coinbase announced another expansion on November 2. The distinction matters because an announcement can remain relevant without being presented as breaking news.

The useful question for an existing account holder is whether the new option completes a particular payment or trading workflow. A balance visible inside an app, a withdrawal to an outside wallet and an asset accepted against a trading obligation answer different questions. Treating them as one capability makes it easy to promise a recipient something the sender has not actually checked.

Section sources[1][2][3]

XRP Ledger, Base and Ethereum require a route decision

Coinbase’s October 28 record explicitly lists deposits and withdrawals on XRP Ledger, Base and Ethereum. Crypto.news independently reported that three-network scope on October 29. The evidence establishes available transfer routes in the launch announcement. It does not establish how much customer activity subsequently used each network, or that every customer has identical permissions.

Analysis: the receiving workflow should determine the route. Consider a hypothetical accounts-payable team whose counterparty asks for RLUSD on one named network. The sender should record that network beside the destination details and confirm the receiving service supports the same combination before authorizing a transfer. A shared token name is not a substitute for a complete payment instruction.

This creates a practical documentation task. A treasury payment record should distinguish the asset, chosen network, destination, approval and evidence of receipt. If staff keep only the ticker and amount, a later reviewer may be unable to tell whether an instruction was followed. The announcement is therefore most useful when translated into a repeatable operational procedure, rather than treated as permission to send funds wherever the ticker appears.

Uncertainty: these launch records do not provide network-level customer volumes or a complete matrix of regional restrictions. An analyst should leave those fields unresolved until Coinbase publishes the relevant breakdown or the customer verifies its own account. Three named networks describe product scope, not three equally used settlement markets.

Section sources[1][4]

One-for-one conversion is a quotation, not a completed payment

Coinbase announced conversion from U.S. dollars into RLUSD at a one-for-one rate. Ripple’s release also refers to conversions from other supported dollar-denominated stablecoins. The scope word matters: the announcement does not identify every eligible stablecoin or make a universal statement about all routes out of RLUSD. Reuters corroborates that RLUSD is a dollar-backed stablecoin offered through Coinbase’s retail and institutional platforms.

Analysis: a conversion ratio answers how units are exchanged at the specified step. It does not, by itself, establish the total cost or completion time of an entire business workflow. Before comparing alternatives, a firm should ask for the applicable account terms, an executable conversion quote, transfer charges and the receiving party’s acceptance conditions. Those are questions to resolve, not fees or delays this article claims Coinbase imposes.

Hypothetical example: a business owes a supplier a dollar invoice and proposes sending RLUSD. The business needs agreement on whether delivery of the tokens satisfies that invoice or whether the supplier expects dollars in a bank account. If the parties have not agreed, a successful token transfer may leave the commercial reconciliation question open. This example describes contract planning, not an observed dispute or a legal conclusion about Coinbase customers.

For readers comparing stablecoins, the relevant output is usable funds at the agreed destination. A neat conversion ratio should be recorded alongside that outcome. It should not replace the outcome in a cost comparison or operational acceptance test.

Section sources[1][2][3][5]

Coinbase’s launch notice leaves Global Exchange collateral for later

The launch notice says availability for Coinbase Global Exchange customers, including RLUSD collateral use, will follow. Ripple’s release and Crypto.news describe the same staged scope. Confirmed fact: the October 28 announcement separates those capabilities from its initial rollout. Unresolved: the cited records do not specify a firm activation date or a complete collateral rulebook.

Analysis: a trading desk should maintain separate approval entries for holding an asset, transferring it and pledging it. If a desk wants to use RLUSD against an obligation, it needs the venue’s actual eligibility terms before making that dependency part of its funding plan. Relevant questions include permitted accounts, valuation treatment, any collateral discount, concentration limits and withdrawal conditions. These are due-diligence questions, not claims that particular restrictions have been announced.

A hypothetical desk can make this distinction concrete by documenting a fallback funding route until the planned capability has both launched and been tested in its own account. The decision is about operational dependency: an unconfirmed future feature should not become the sole means of meeting a dated obligation. No launch date is inferred here from the word “later.”

What would change the conclusion is a dated operating notice with applicable terms, followed by evidence that the relevant account can actually use the service. A conference appearance or repeated statement of intent would not answer the same question.

Section sources[1][2][4]

What the launch does and does not establish for XRP readers

RLUSD is the listed dollar stablecoin; XRP Ledger is one of the named transfer networks. Reuters frames the event as an expansion of Coinbase’s stablecoin offering. Those facts support a distribution story. They do not quantify incremental XRP purchases, identify new institutional payment volumes or establish an XRP price effect.

Analysis: separate availability, use and economic impact. Availability asks whether a service offers the asset. Use asks whether customers actually complete transfers or transactions with it. Economic impact asks what additional activity occurred because of that access. Evidence for the first stage cannot automatically answer the next two, even when the platform is prominent.

For a researcher, the next useful dataset would pair dated customer activity with the chosen network and a clear definition of what is counted. A transfer count, a dollar value and an account count measure different things. Repeated movements by one participant should not be described as distinct businesses adopting a service without supporting records. Likewise, total RLUSD activity cannot be assigned to the Coinbase launch merely because it occurred afterward.

For an operations manager, a useful first review is a short evidence log: the date the feature was verified, the account and region tested, the selected network, the receiving service and the unresolved questions. Repeat that review when terms change or a new feature becomes available. This proposed process is an editorial implication of the staged launch, not a description of Coinbase’s internal controls. It turns a broad product announcement into a bounded decision that another team member can inspect and reproduce.

Section sources[1][3][4]