NewsCryptoRipple Mint: How Institutions Use RLUSD for Minting, Redemption and Payments

Ripple Mint: How Institutions Use RLUSD for Minting, Redemption and Payments

Author: CryptoDaily·

Key Takeaways

  • Ripple Mint launched on July 23, 2026, as a unified interface and API enabling eligible institutions to mint, redeem, bridge, and track RLUSD.
  • RLUSD is issued on the XRP Ledger by Standard Custody & Trust Company, LLC, which holds a New York Department of Financial Services limited-purpose trust charter.
  • Ripple announced a strategic investment in Notabene, integrating RLUSD with Notabene Flow to support Travel Rule and VASP screening within regulated payment workflows.
  • As of July 25, 2026, RLUSD's market capitalization was approximately $1.59–1.60 billion, while reported on-chain transfer volume fell roughly 25% month-over-month from about $14.6 billion to $11 billion.
  • Ripple Mint is available only to eligible institutional customers that complete know-your-business onboarding, and is not offered as a retail product.
Ripple Mint: How Institutions Use RLUSD for Minting, Redemption and Payments

Ripple Mint is designed for eligible institutional customers that need an operational way to create, redeem, bridge and monitor RLUSD, Ripple’s dollar-referenced stablecoin. For treasurers, exchanges, funds, OTC desks, payment service providers and fintechs, the central questions are how onboarding works, how fiat and tokens move through the system, how compliance checks are integrated, and where RLUSD may fit alongside existing settlement rails. Stablecoins have become a meaningful part of institutional payment and settlement infrastructure, with major dollar-referenced assets like USDC and USDT collectively processing trillions in annual transfer volume, so institutional-grade tooling around issuance and compliance has become a competitive focus area across the sector.

Ripple launched Ripple Mint on July 23, 2026, describing it as a unified user interface and API for institutions to mint, redeem, bridge and track RLUSD (Ripple). RLUSD is issued on the XRP Ledger by Standard Custody & Trust Company, LLC, a New York Department of Financial Services-chartered trust company cited by Ripple. The NYDFS limited-purpose trust charter has been used by other dollar stablecoin issuers and requires adherence to state-level oversight of custody and reserve practices. Ripple has also announced a strategic investment in Notabene, with RLUSD integrating into Notabene Flow for regulated payment workflows (TMCNet / PR Newswire).

As of July 25, 2026, RLUSD’s market capitalization was around $1.59 billion to $1.60 billion, with a similar circulating supply, according to DefiLlama (DefiLlama). Recent reports also noted an approximately 25% month-over-month decline in on-chain transfer volume around the July announcements, from roughly $14.6 billion to about $11 billion (TradingView.

What Ripple Mint does

Ripple Mint functions as the institutional control panel for creating and retiring RLUSD. It offers both a browser-based dashboard and programmatic APIs, allowing teams to automate minting, redemption, bridging and monitoring while applying permissions and audit trails similar to those used in other finance systems.

The basic workflow is straightforward: an institution sends dollars into the relevant fiat process, mints a corresponding amount of RLUSD, moves the tokens to the required destination, and later redeems RLUSD back into dollars when needed. The product is intended for eligible institutional customers rather than retail users.

The issuer is a central part of the structure. RLUSD is issued by Standard Custody & Trust Company, LLC, which Ripple identifies as a New York Department of Financial Services-chartered trust company. That status provides a specific regulatory framework for the issuer and custody model, but it is not the same as deposit insurance.

Compliance is also built into the institutional flow. Ripple disclosed a strategic investment in Notabene and said RLUSD is integrating with Notabene Flow to support Travel Rule and virtual asset service provider, or VASP, screening obligations inside regulated payment workflows. The Travel Rule stems from FATF Recommendation 16, which has been adopted in various forms by jurisdictions worldwide and requires VASPs to share originator and beneficiary information for transactions above defined thresholds. In practice, that means originator and beneficiary information, counterparty checks and related evidence can accompany payments when required.

Scale and activity remain relevant operational variables. RLUSD had reached roughly $1.59 billion to $1.60 billion in market capitalization by late July 2026, according to DefiLlama. At the same time, reported on-chain transfer activity fell by about a quarter month over month around the launch window. Institutions evaluating execution depth, settlement reliability or payout predictability would need to compare those trends with the specific networks and venues they use.

Key terms

Ripple Mint: The institutional dashboard and API used to mint, redeem, bridge and monitor RLUSD issuance and flows.

RLUSD: Ripple USD, a dollar-referenced stablecoin issued by Standard Custody & Trust Company, LLC.

Minting: The creation of new RLUSD after fiat is sent to the issuer or designated accounts, with tokens received on a one-for-one basis.

Redemption: The return of RLUSD to the issuer in exchange for fiat settlement to an approved bank account.

Travel Rule checks: Compliance processes that share required originator and beneficiary information between virtual asset service providers.

Bridging: Moving RLUSD between supported networks while tracking balances and provenance across the transfer path.

Institutional implementation process

An institution considering RLUSD would first define the business purpose. Typical use cases include exchange settlement, treasury sweeps, on- and off-ramps into trading venues, intercompany settlement and programmable payouts. Establishing the specific function helps keep onboarding and controls aligned with the intended use.

The next step is eligibility and onboarding. Access to Ripple Mint requires engagement with Ripple’s institutional team. Institutions should expect corporate documentation, know-your-business checks and verification of authorized signers before they receive access.

Fiat and custody arrangements then need to be established. Institutions must align accounts for fiat settlement with the issuer, Standard Custody & Trust Company, and register approved bank accounts for redemption proceeds. These bank and custody rails are central to the round trip from dollars to RLUSD and back to dollars.

API integration and permissioning are also important. Teams can connect Ripple Mint’s API to back-office systems and assign roles so that only approved users can mint, redeem or approve transfers. Every action should be logged for reconciliation, audit and risk management.

A small test cycle can help document operational timing. An institution may mint a low-dollar amount of RLUSD, bridge it to a target network if needed, and then redeem it back to fiat. That round trip can identify timing, reconciliation steps, bank windows and any operational dependencies before larger flows are used.

Compliance controls should be connected from the start. Institutions using Notabene or a comparable provider can integrate Travel Rule checks, sanctions screening and counterparty VASP validation into payout logic. Ripple’s announced Notabene integration is intended to support those regulated payment workflows.

Treasury policies should also define how much RLUSD may be held, when balances should be swept back to fiat, which wallets are approved, and which networks or venues may be used. Written thresholds and approvals can simplify future audits and internal reviews.

Finally, institutions should monitor liquidity and activity on the actual routes they use. A broad decline in transfer activity does not affect all corridors in the same way, but lower activity on a relevant network or venue can affect spreads, execution depth or settlement routing.

Where RLUSD fits in an institutional stack

For institutions, RLUSD can function as a programmable dollar balance that is created for specific operational tasks. A firm that reconciles exchange balances daily could mint RLUSD in the morning, use it for venue funding or settlement during the day, and redeem it later to reset cash balances. A payments company serving partners in multiple jurisdictions could bridge RLUSD to a supported network preferred by a counterparty and allow fiat settlement on the other side.

The operational appeal is the single control plane for minting, redemption and bridging. Ripple Mint provides one place to track what has been created, moved and retired, with records that finance, operations, compliance and risk teams can review.

The trade-off is issuer concentration. Standardizing on one issuer can simplify procedures, but it also concentrates operational and counterparty exposure. Many institutional teams maintain more than one stablecoin or settlement rail so that an outage, wallet issue, venue disruption or policy change does not interrupt all payment activity.

RLUSD compared with USDC and USDT

Many institutional crypto teams already use USDC or USDT. RLUSD is not positioned as an immediate replacement for those assets in every setting. It may be used where its issuance workflow, compliance integrations or partner rails are better aligned with a particular use case.

RLUSD is issued by Standard Custody & Trust Company, LLC, which Ripple describes as NYDFS-chartered. USDC is issued by Circle Internet Financial, while USDT is issued by Tether Holdings. RLUSD’s primary positioning is institutional flow management through Ripple Mint’s UI and API. USDC has broad developer and enterprise reach through accounts and APIs, while USDT is widely used for liquidity on trading venues across many networks.

The tooling also differs. Ripple Mint combines minting, redemption, bridging and tracking. USDC offers account dashboards, issuance APIs and payout tooling. USDT supports direct issuance for qualified clients and exchange integrations.

On compliance, Ripple has announced RLUSD integration with Notabene Flow for regulated payments. USDC users may rely on Travel Rule and sanctions tooling through partners and internal controls. USDT-related VASP screening varies by counterparty and venue.

In scale, RLUSD was around $1.59 billion to $1.60 billion in market capitalization as of July 25, 2026, according to DefiLlama. USDC is significantly larger, and USDT is the largest by circulation. For network coverage, Ripple Mint supports bridging across supported networks, while USDC and USDT are available across multiple major networks.

RLUSD may be most useful where auditability and operational clarity are the priorities. A single view of issuance and movement can help keep finance, operations and compliance aligned. Where the main requirement is access to the deepest retail liquidity across many venues, incumbent stablecoins may still dominate.

Operational scenarios

One scenario involves a trading firm that sets a daily cap for pre-funding market makers. The firm mints RLUSD against that cap at 08:00, sends capital to two venues, and redeems overnight to reset cash on hand. Ripple Mint’s ledger can simplify end-of-day reconciliation, while compliance evidence can follow payouts through Notabene Flow where required.

A second scenario involves a payments company managing fragmented corridors. Some partners may accept stablecoins only on particular networks. The company can mint RLUSD, bridge it to the target network, and send programmatic payouts with Travel Rule checks attached to each transfer. That structure is intended to reduce manual exceptions and improve the audit trail.

A third scenario involves a corporate treasurer seeking to minimize on-chain balances. The company can authorize just-in-time minting for approved wallets, maintain a low standing balance, and sweep amounts above a threshold back to fiat. Such a policy can reduce exposure to smart contract and wallet risks while keeping the settlement method available.

Institutions should also consider backup settlement routes. Relying on a single stablecoin can simplify operations but creates dependency on one issuer, one policy set and one group of technical rails. Maintaining a second rail in production, with periodic testing, can reduce the risk of an inactive fallback process.

Operational risks and watch points

Ripple Mint is intended for eligible institutions. Entities that cannot complete KYB and institutional onboarding should not assume access to the product.

Activity cycles also matter. Reported monthly RLUSD transfer volume declined around the launch period. Lower activity in specific corridors can affect spreads, execution depth or settlement timing, depending on the route.

Network compatibility must be verified in advance. A counterparty’s preferred network may not match the institution’s preferred network, and supported networks should be checked in Ripple Mint before operational timelines are promised.

Redemption operations require testing. Cutoff times, bank processing windows and reconciliation procedures can create delays even when token movement is fast. Institutions should test the full mint-to-redeem cycle.

Compliance gaps can create operational problems. Institutions subject to Travel Rule or VASP screening requirements should build those checks into payout workflows rather than trying to reconstruct documentation after transfers occur.

Single-issuer risk should also be assessed. A unified issuer model is operationally clean, but it concentrates counterparty and process risk. Backup rails can help reduce dependence on one provider.

Frequently asked questions

Who can use Ripple Mint?

Ripple Mint is for eligible institutional customers. That typically includes corporates, funds, exchanges, OTC desks, payment service providers and fintechs that complete KYB and onboarding. It is not a retail application.

Is RLUSD regulated or insured?

RLUSD is issued by Standard Custody & Trust Company, LLC, which is chartered by the New York Department of Financial Services. That provides a regulatory framework for the issuer and custody model, but it is not the same as deposit insurance. RLUSD should be treated as a regulated stablecoin product, not a bank account.

How do minting and redemption work?

An institution initiates a mint through the Ripple Mint interface or API, funds the request with fiat to the designated account, and receives RLUSD one for one. For redemption, the institution sends RLUSD back through the platform, and fiat settles to an approved bank account after the request is processed.

What does the Notabene integration change?

The Notabene integration is intended to add Travel Rule and VASP screening to payment flows, allowing originator and beneficiary information to accompany transfers when required. The goal is to support cross-institution payouts without separate ad hoc checks.

How large is RLUSD?

By late July 2026, RLUSD’s market capitalization and circulating supply were around $1.59 billion to $1.60 billion, according to DefiLlama and other market data aggregators tracking the token.

Where can RLUSD move, and how fast does it settle?

Ripple Mint supports bridging and tracking across supported networks. Settlement timing depends on network confirmation times, platform processing windows and the bank rails used for redemption. Institutions can test the full cycle with a small amount to establish internal timing expectations.

Is RLUSD the same as XRP?

No. RLUSD is a stablecoin referenced to the US dollar and issued on the XRP Ledger by Standard Custody & Trust Company, LLC. XRP is a separate digital asset used for various network and liquidity functions. The two assets serve different roles.

Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial or other advice.