Ripple announced on October 26, 2026, that the Office of the Comptroller of the Currency (OCC) had granted final approval to establish Ripple National Trust Bank (RNTB). The decision follows preliminary conditional approval in December 2025. RNTB’s approved activities include managing reserves that support Ripple USD (RLUSD), acting as collateral trustee for RLUSD holders, and providing fiduciary digital-asset custody. Ripple says the custody service will be authorized upon the bank’s opening.
The question is no longer whether Ripple can pursue a federal trust charter. It is whether the approved structure will make RLUSD easier for institutions to hold, redeem and use in payments. That requires looking at the work assigned to each entity—not treating “bank approval” as a single solution to every stablecoin risk.
What changed with final OCC approval?
The December 2025 decision approved RNTB’s application conditionally. Final approval advances the bank past that chartering stage, giving Ripple a federally supervised entity for the functions set out in its approved plan. It does not mean every service was live on October 26; Ripple describes fiduciary custody as a capability available upon opening.
RNTB is not becoming the issuer of RLUSD. Standard Custody & Trust Company (SCTC), Ripple’s New York-regulated subsidiary, continues to issue the token. RNTB’s planned work sits beside the issuer: managing a segregated reserve on SCTC’s behalf, serving as collateral trustee for holders, and offering fiduciary digital-asset custody.
That separation is the central institutional story. A bank evaluating RLUSD can identify which company creates the redemption obligation, which entity has duties connected to the reserve, and which institution holds reserve assets. The charter makes those roles more defined. It does not turn RLUSD into an insured bank deposit or give a payment partner automatic access to banking services.
How would the RLUSD reserve structure work?
Start with the parties involved:
| Function | Entity identified in Ripple’s structure |
|---|---|
| Issues and redeems RLUSD | SCTC, supervised by New York’s Department of Financial Services |
| Manages the segregated reserve and acts as collateral trustee | RNTB, under its OCC-approved plan |
| Serves as primary reserve custodian | BNY |
The OCC described RNTB’s proposed reserve management as a directed activity. That word matters: managing the reserve is not the same as issuing RLUSD or necessarily holding every reserve asset. Ripple identifies BNY as RLUSD’s primary reserve custodian. The practical question for a prospective client is how instructions, asset custody, recordkeeping and redemption requests pass between these entities.
The collateral-trustee role warrants attention. A monthly reserve report can show the assets reported against tokens in circulation. It does not, by itself, explain who owes duties to holders if the issuer faces financial distress. The OCC’s approval letter says RNTB plans to perform collateral-trustee services for the benefit of RLUSD holders on a fiduciary basis. Institutions will still need to examine the governing documents to understand how that arrangement operates and what claims holders would have in a stress event.
None of this replaces ordinary stablecoin diligence. A treasury team still needs current attestations, redemption terms, information about where reserve assets are held, and a process for reconciling issued tokens with liabilities. The approval adds a supervised bank to the structure; it does not substitute a charter for evidence that the structure works.
Why does fiduciary custody matter for adoption?
RNTB’s approved business plan also covers cryptocurrency custody for Ripple affiliates and unaffiliated institutional customers, carried out in a fiduciary capacity. The OCC stated that the proposed custody service would be subject to fiduciary duties and standards of behavior. That could give an institution a way to evaluate digital-asset custody as part of the same broader relationship through which it assesses RLUSD-related services.
Consider a firm that receives tokenized collateral, holds it overnight and sends it to a counterparty as part of settlement. Its risk review extends beyond whether the blockchain transfer succeeds. It must establish who controls the asset before transfer, who can authorize movement, how positions are recorded, and how an error or compromise would be handled. A fiduciary custodian may address part of that workflow. It cannot remove the need to test controls or agree on the legal treatment of client assets.
That is why custody is more than an adjacent product. Payments, collateral and treasury processes all depend on assets being held and released according to documented instructions. If RNTB opens and institutions adopt its custody service, Ripple could connect more steps of those processes. Whether that occurs is a matter of client onboarding and execution, not a consequence that follows automatically from final approval.
How does Ripple’s approach compare with Circle’s?
Circle provides a useful comparison because it also pursued a national trust bank. Circle announced final OCC approval for Circle National Trust on July 10, 2026, after receiving conditional approval in December 2025. Its stated initial focus is fiduciary digital-asset custody for Circle and its affiliates. Circle describes management of USDC reserves by the trust bank as a future capability.
Ripple’s approved plan, by contrast, specifies RLUSD reserve management and a collateral-trustee role alongside custody. It also contemplates custody for unaffiliated institutional customers. These are differences in the companies’ stated bank plans, not a ranking of their stablecoins. Both continue to distinguish the stablecoin issuer from the national trust bank.
The comparison illustrates two routes into the banking system. Circle is building a federally supervised custody layer around an established stablecoin network, with reserve management planned for later. Ripple is connecting a new trust bank more directly to the governance of RLUSD’s reserve while adding an institutional custody option. For a payment firm selecting a token, those distinctions may affect its diligence. They do not settle questions about liquidity, partner acceptance or the cost of moving funds at either end of a payment.
What does this mean for XRP?
The OCC decision concerns RNTB’s approved banking activities. It does not make XRP a reserve asset backing RLUSD, nor does it require an institution to use XRP as the principal in every RLUSD payment. Ripple identifies RLUSD as a dollar-backed stablecoin used in its payments infrastructure and as collateral within Ripple Prime. Those uses should be evaluated on their own terms.
XRP may still have a role where a payment route or XRP Ledger application uses it. But that is a question about the route chosen, available liquidity and the services a client uses. More RLUSD activity could expand activity around Ripple’s products or the XRP Ledger; it does not establish a direct relationship between this charter approval and demand for XRP. Keeping that distinction clear makes the institutional case easier to assess without turning a banking development into a token-price forecast.
What would make the approval matter for payments?
A cross-border payment illustrates the remaining work. Suppose a business obtains RLUSD, sends it to a partner, and the partner converts it into funds its recipient can use. A token transfer can move a dollar-denominated claim between supported wallets. But the complete payment also needs a means to obtain the token, controls at each counterparty, sufficient liquidity at the destination and a workable redemption or conversion path.
RNTB’s approved functions may help answer questions about the claim and the assets supporting it. Custody may help firms safeguard assets while a payment is prepared or settled. Neither function, on its own, guarantees local payout, reduces every conversion cost or ensures that a recipient’s bank will accept the arrangement.
For institutions, the most useful next questions are concrete:
- Has RNTB opened and begun offering the approved services?
- How are RNTB’s instructions coordinated with SCTC and BNY?
- What do the collateral-trustee documents provide for RLUSD holders?
- Which custody services are available to unaffiliated clients, and under what terms?
- Can payment partners demonstrate routine issuance, transfer and redemption—not just an on-chain transfer?
These questions also set a test for adoption. Announcements and charters establish what an entity is authorized to do. Repeat payment flows, documented controls and client use show whether the structure solves an operating problem.
The significance of Ripple’s approval
Ripple’s final-approval announcement moves its federal trust-bank plan beyond the preliminary stage. Its significance is specific: an OCC-supervised entity can take on proposed reserve-management, trustee and custody functions while SCTC remains the New York-regulated RLUSD issuer. Compared with Circle’s stated plan, Ripple has assigned its trust bank a more immediate role in stablecoin reserve governance.
The next milestone is not another description of what a regulated stablecoin should be. It is evidence that these separate entities can operate together in ways payment firms and banks can verify. If they can, RLUSD may become easier to integrate into institutional workflows. The effect on XRP remains indirect and depends on which networks and payment routes clients choose.
