Ripple's RLUSD Guide Puts CFTC Collateral Eligibility in Focus

What does Ripple’s September 11 RLUSD guide establish?

Ripple’s September 11 guide explains RLUSD’s issuer supervision, but it does not establish blanket CFTC approval for the stablecoin. The relevant collateral framework also includes February’s replacement staff letter and March’s clarifications. Institutions must distinguish a regulated issuer, an eligible asset category, and acceptance by their particular broker or clearinghouse. [1][2][4]

The immediate development is a new explanation from Ripple, rather than a new rule, charter or trading launch. Ripple identifies Standard Custody & Trust Company as RLUSD’s issuer under New York supervision and separates that status from derivatives collateral treatment. Its discussion cites December 2025 Staff Letter 25-40. Reading the subsequent regulatory record adds operational limits that matter to anyone evaluating the claim. [1][3]

This report checks the guide against the CFTC’s February and March records, New York’s stablecoin guidance, the OCC’s charter decision and independent coverage. Confirmed facts below describe those documents. Analysis explains their practical implications. Uncertainty remains around institution-specific acceptance, actual usage and future approvals; none can be inferred merely from the publication of an issuer’s guide.

Section sources[1][2][3][4]

CFTC Letter 26-05 is the successor to the cited December letter

The CFTC’s Market Participants Division reissued 25-40 as Letter 26-05 on February 6, 2026. The stated revision added national trust banks to the issuer categories in its payment-stablecoin definition. The agency said the other conditions were reproduced without change. Ledger Insights independently reported the February update when covering the March clarification. An operating checklist should therefore identify the successor document instead of treating the December letter as the last word. [2][3][6]

The letter sets a conditional staff position on enforcement recommendations involving futures commission merchants, or FCMs. These firms handle customer futures and related derivatives business. The document addresses how qualifying collateral can be counted and segregated. It does not contain a named RLUSD approval. The distinction matters because meeting an issuer-category description is only one part of a larger set of conditions. [3][5]

Analysis: a useful evidence chain runs from the applicable staff conditions to the broker’s policies and then to the customer agreement. A token’s marketing page cannot supply all three. For a treasury team, the actionable question is which specific account and transaction the broker will support, with what valuation, controls and withdrawal terms.

Section sources[2][3][5][6]

Customer collateral and a broker’s own stablecoins have different rules

The CFTC’s March 20 FAQ addresses a distinction that disappears in broad claims about stablecoin acceptance. A customer may post qualifying crypto collateral under the framework, while an FCM may place its own payment stablecoins in segregated customer accounts as residual interest. Residual interest is the firm’s contribution to those accounts. The FAQ does not allow the FCM to invest customer funds in stablecoins under this relief. Greenberg Traurig’s analysis corroborates that boundary. [4][5]

Consider an illustrative operations request: a customer asks to deliver an existing RLUSD balance, while a broker proposes converting customer cash into RLUSD. These requests require different review. Permission relevant to the first cannot simply be copied into the second. The example is an analytical comparison of the rules, not evidence that a particular broker offers either workflow.

For affected customers, acceptance documentation should identify who owns the posted assets, where they are held and what happens when collateral must be returned. For FCMs, internal procedures should distinguish receipt of customer property from deployment of the firm’s own assets. Otherwise, an apparently small change in a cash-management instruction can cross a substantive regulatory boundary.

Section sources[4][5]

The 2% capital figure does not price every RLUSD margin account

The March FAQ discusses a 2% capital treatment for proprietary payment-stablecoin positions and at least 2% for proprietary stablecoins deposited as residual interest. Those are scoped capital provisions. They are not a universal customer-margin haircut. Separately, clearing organizations remain responsible for collateral haircuts that reflect relevant risks. Ledger Insights reports the capital treatment; Greenberg Traurig separately explains clearinghouse haircut responsibilities. [4][5][6]

A haircut reduces the amount of an asset’s value recognized for a particular purpose. A capital calculation concerns the broker’s financial resources; a customer margin schedule concerns the collateral required for a position. Analysis: copying a percentage from one calculation into the other can produce a funding plan that the broker will not honor. The fact that both calculations concern stablecoins does not make them interchangeable.

An institution should request the actual collateral schedule for its legal entity, account and product, including any concentration limit and the process for changing terms. This report provides no quoted RLUSD haircut from an operating broker. That is an explicit information gap, not an assumption that any published percentage applies to every customer.

Section sources[4][5][6]

Uncleared swaps remain a separate collateral question

Another boundary appears in FAQ question 5: Letter 26-05 does not expand the eligible-margin list for uncleared swaps. The FAQ distinguishes crypto assets, including payment stablecoins, from a tokenized representation of an already eligible asset that preserves the required rights. Greenberg Traurig’s independent explanation makes the same distinction. This is a material limit for firms whose derivatives activity extends beyond centrally cleared contracts. [4][5]

Analysis: the instrument and transaction must be identified before choosing the collateral rule. A stablecoin backed by reserve assets is not automatically interchangeable with a tokenized claim carrying rights in a particular eligible security. Similar technology or dollar denomination cannot resolve that legal difference. A proposal covering futures, cleared swaps and bilateral swaps needs separate conclusions for each use case.

Section sources[4][5]

NYDFS supervision and the OCC charter answer different questions

RLUSD’s New York regulatory history predates this guide: The Block reported its NYDFS approval in December 2024. Ripple’s September 11 account identifies Standard Custody as the issuer under a limited-purpose trust charter. New York’s June 2022 guidance addresses reserve backing, segregation, redemption and independent attestations. Davis Polk independently explained those requirements in June 2022. These are issuer safeguards, rather than an instruction to derivatives brokers to accept the token. [1][7][10][11]

The redemption clock also has conditions. NYDFS describes timely redemption as no more than two full business days after the business day the issuer receives a compliant order, including completed onboarding and other necessary conditions; DFS may permit an exception in extraordinary circumstances. Selling through an exchange is therefore not the same operational request as redeeming with the issuer. Analysis: a liquidity plan needs the route to dollars and its prerequisites, not only a statement about reserve backing. [7][11]

The OCC’s December 12, 2025 decision granted Ripple National Trust Bank preliminary conditional approval and withheld permission to commence business until preopening requirements were satisfied. Reuters independently reported the preliminary nature of that decision. Ripple’s new guide still describes a conditional stage. The historical approval should not be represented as proof that a completed federal charter or a new operating service arrived on September 11. [1][8][9]

Section sources[1][7][8][9][10][11]

What this means for RLUSD users and XRP Ledger readers

The practical output is a documented acceptance decision. Treasury teams need the issuer record and redemption route; trading desks need their broker’s eligible-collateral terms; risk teams need custody, valuation and stress procedures that fit the exact transaction. Those documents should agree on the asset, account and governing framework. A favorable answer about supervision cannot substitute for a missing answer about operational access.

Uncertainty: the records reviewed here do not establish new RLUSD collateral volumes, acceptance by every FCM, or additional XRP purchases. Ripple’s guide does not announce a new XRP Ledger deployment. For XRP readers, a possible future connection between institutional stablecoin use and network activity remains an inference requiring separate transaction and venue evidence. This article therefore makes no price prediction or adoption estimate. [1]

The next meaningful evidence would be a dated broker collateral schedule identifying RLUSD and the covered product, a published change to the applicable CFTC conditions, or an OCC record establishing a later charter milestone. Each would answer a different unresolved question. Until then, the strongest conclusion is specific: the regulatory documents support a conditional framework with identifiable limits, and institutions must verify their own access within it.

Section sources[1][3][4][8]