Ripple USD (RLUSD)

Ripple USD (RLUSD): How the Issuer-Controlled Dollar Token Works

Ripple USD is a fiat-backed stablecoin issued by Standard Custody & Trust Company and distributed across several blockchain networks. Its practical design combines segregated reserves, institution-only primary issuance and redemption, compliance controls, and issuer-administered token contracts.

Issuer, reserve model, and redemption

RLUSD is issued by Standard Custody & Trust Company, LLC, a wholly owned Ripple subsidiary chartered and supervised by the New York Department of Financial Services as a limited purpose trust company. Ripple’s June 2026 whitepaper describes RLUSD as backed one-to-one by high-quality liquid U.S. dollar assets and says only approved institutional customers may interact directly with the issuance and redemption process. Other users generally access the token through secondary markets, exchanges, or payment providers rather than through the issuer itself.

The reserve framework includes short-dated U.S. Treasury bills, government money-market funds, overnight reverse repurchase agreements, and deposits at approved banks. Ripple says non-cash reserve assets are held with Bank of New York Mellon under arrangements intended to separate them from the issuer’s proprietary assets, while monthly CPA attestations report management’s assertions about circulating RLUSD and reserve composition. The whitepaper also describes a 3% initial reserve buffer, although reserve coverage and attestation quality still depend on the issuer’s controls, custodians, valuation process, and disclosures.

How primary issuance and redemption work

The documented issuance flow begins when an approved institutional customer deposits U.S. dollars. Standard Custody moves the funds into the reserve account, performs compliance checks on the related wallet, and authorizes the blockchain transaction that delivers RLUSD. Redemption reverses this process: the customer sends RLUSD to the designated redemption wallet, the issuer checks the transaction and wallet, reduces the token balance onchain, and sends fiat settlement instructions through its banking relationships.

Ripple’s Mint documentation shows that redemption is not simply an automatic retail cash-out available to every holder. Users must use the nominated wallet and supply enough XRP or ETH for network fees. Bank settlement timing can vary, and the documented flexible-redemption feature is an enterprise workflow that can hold inbound RLUSD for up to three hours before fiat settlement or a bridge transfer. These dependencies make banking access, compliance approval, correct wallet handling, and supported jurisdictions part of the token’s practical utility.

Two token designs: XRPL issued currency and EVM proxy

On the XRP Ledger, RLUSD uses the ledger’s native issued-currency system. A wallet must establish a trust line with the issuer before it can receive or hold the token. Ripple’s implementation repository documents issuer settings that enable global freeze and trust-line clawback, while also enabling deposit authorization. Those settings support compliance and recovery procedures but give the issuer meaningful control over token movement and balances.

On Ethereum and other EVM networks, RLUSD follows the ERC-20 standard and uses a proxy upgrade pattern. The proxy is the address users should integrate with, while a separate implementation contract contains the token logic. Ripple’s documentation lists the Ethereum proxy as 0x8292bb45bf1ee4d140127049757c2e0ff06317ed and gives a shared proxy address for Base, Ink, Optimism, Unichain, and the XRPL EVM sidechain. A proxy architecture can simplify upgrades and preserve a stable user-facing address, but it also means contract administration and upgrade authority are material dependencies.

Networks and intended users

The current Ripple documentation lists RLUSD on the XRP Ledger, Ethereum, Base, Ink, Optimism, Unichain, and the XRPL EVM sidechain. This is broader than a two-network description and means users must distinguish native RLUSD deployments, network-specific addresses, bridge or transfer workflows, and the gas asset required on each chain. The same symbol does not remove the operational risk of using an incorrect network or contract address.

The project’s stated audience is institutional and business users that need a dollar-denominated settlement asset for payments, treasury operations, remittances, trading, and selected decentralized-finance applications. Ripple’s whitepaper says distribution is handled through business-to-business relationships rather than direct business-to-consumer issuance. In practical terms, RLUSD’s usefulness depends not only on blockchain transfer speed but also on exchanges, custodians, payment providers, banking rails, wallet support, and sufficient secondary-market liquidity.

Control, compliance, and upgrade governance

RLUSD is not presented in the reviewed materials as a token governed by holder voting or a decentralized autonomous organization. Control is instead divided among the issuer, its regulated subsidiary, operational administrators, compliance systems, custodians, and the smart-contract or XRPL issuer accounts. The whitepaper says the issuer may freeze sanctioned wallets and describes internal teams that support reserve management, compliance, engineering, and transparency. These controls are central to the product’s compliance model, but they also create issuer and administrator concentration.

The whitepaper says code changes affecting onchain behavior will be communicated before upgrades and that the contracts have undergone third-party review, but those statements are project disclosures rather than a guarantee that every future change will be harmless. The EVM proxy design confirms that implementation logic can be separated from the address users interact with. Readers assessing RLUSD should therefore examine current contract permissions, issuer-account settings, upgrade events, reserve reports, and redemption terms rather than treating the token as an immutable bearer asset.

What the stablecoin design does not remove

RLUSD’s dollar objective depends on reserve sufficiency, access to banking and custodial institutions, the issuer’s ability to process redemptions, and confidence in its attestations. A reserve report is an important disclosure but does not eliminate operational, legal, counterparty, liquidity, or settlement risk. The direct redemption pathway is also subject to customer onboarding, compliance checks, applicable conditions, and banking cutoffs.

The multi-chain design adds another layer of dependency. Users must verify the network, official address, wallet compatibility, gas balance, and any bridge or transfer mechanism involved. On XRPL, freeze and clawback controls can affect transferability; on EVM networks, proxy administration and implementation changes can affect contract behavior. These are not necessarily defects in a compliance-focused stablecoin, but they are core facts for anyone evaluating custody, integration, or settlement exposure.

Key takeaways

• RLUSD is issued by Standard Custody & Trust Company, a Ripple subsidiary supervised by the New York Department of Financial Services.
• The reserve model uses cash and short-duration government-related assets, with monthly third-party attestations described by Ripple.
• Direct minting and redemption are primarily institutional processes subject to KYC, AML, wallet checks, banking access, and applicable conditions.
• RLUSD exists across XRPL and several EVM networks, so network and contract verification is essential.
• XRPL issuer controls include global freeze and clawback capabilities, while EVM deployments use upgradeable proxy architecture.
• The token’s practical success depends on reserves, banking partners, custodians, compliance systems, secondary liquidity, and wallet support.

Risks and open questions

• Reserve attestations are management assertions examined by an independent CPA; they should not be treated as a guarantee against issuer, custodian, banking, or valuation risk.
• Direct redemption is restricted to approved customers and depends on compliance approval, nominated wallets, banking rails, and jurisdictional availability.
• XRPL issuer settings permit global freezing and trust-line clawback, creating meaningful centralized control over token balances and transfers.
• EVM deployments use proxy architecture, so contract administration and future implementation upgrades are material technical dependencies.
• The multi-chain structure creates address, network, gas, bridge, and liquidity risks even when the token carries the same RLUSD symbol.
• The reviewed materials do not establish a token-holder governance system or guarantee that every future contract, reserve, or compliance change will preserve current functionality.