Ripple Mint lets institutions mint, redeem and bridge RLUSD

Ripple launched Ripple Mint on July 23, 2026. The platform provides an institutional web console and an API for eligible customers to mint, redeem, bridge and track Ripple USD (RLUSD).

RLUSD is issued by Standard Custody & Trust Company, LLC, a New York Department of Financial Services–chartered trust. Ripple Mint is available to existing RLUSD customers and pairs programmatic workflows with managed onboarding and webhook setup.

The product supports three transaction types: ISSUANCE (fiat to RLUSD), REDEMPTION (RLUSD to fiat) and BRIDGE (cross-chain RLUSD transfers). Transaction statuses include PROCESSING, PENDING (used for flexible redemption), COMPLETED and FAILED.

Administrators must generate API credentials from an Admin account in the Ripple Mint console. Accounts may create up to three client credentials in either UAT or Production. The client secret is shown only once and must be copied immediately after creation.

Integrations exchange client credentials for a JSON Web Token by POSTing to https://api.ripple.com/v2/oauth/token with grant_type=client_credentials and an audience value that includes the tenant ID. Access tokens expire after one hour and Ripple does not issue refresh tokens. Integrations must request new tokens before expiry and include Authorization: Bearer <access_token> on each API call. OAuth scopes include rlusd_customers:read for transaction reads and rlusd_customers:write to approve pending redemptions.

Issuance workflows begin by funding the bank account details provided by Ripple. After Ripple confirms fiat receipt, the platform mints RLUSD to the configured on-chain destination and moves the transaction from PROCESSING to COMPLETED. On completion the webhook payload includes destinationHash for on-chain reconciliation.

Default redemption is automatic. When on-chain RLUSD is received, the transaction advances from PROCESSING to COMPLETED and fiat is paid to the bank account configured in the Ripple Mint UI.

Flexible redemption is optional. When enabled, inbound RLUSD remains in PENDING for up to three hours while the institution sets a destination. Operators enable flexible redemption in the console and approve each PENDING transaction with PUT /v1/stablecoin/transactions/{id}/destination. The approval body must specify type FIAT to create a redemption to the default bank or type CRYPTO with a walletRipId to initiate a bridge. Only PENDING transactions may be updated. Calls against PROCESSING or COMPLETED records return a 409 Conflict. Once a destination type is set it cannot be changed.

Webhook lifecycle events are delivered over HTTPS when transaction state changes. Ripple registers callback endpoints during onboarding rather than offering self-serve registration. Webhooks are delivered at least once and may include duplicates; listeners should deduplicate by transaction id and updatedAt. Ripple expects an HTTP 200 response to stop retries. If a 200 is not returned, it retries with exponential backoff for up to roughly 72 hours and about 75 attempts.

A UAT sandbox is available at api.test.ripple.com for integration testing without moving real funds. The production API base URL is https://api.ripple.com.

The launch announcement also noted an investment by Ripple in Notabene to align the product with identity and compliance tooling used by institutional counterparties.