Table of Contents
Ripple Mint is Ripple's institutional platform for minting, redeeming, bridging, and tracking Ripple USD (RLUSD). Eligible customers use a web console or the Ripple Mint API instead of manual ticketed issuance.
Ripple published the product on July 23, 2026. RLUSD is issued by Standard Custody & Trust Company, LLC, a New York Department of Financial Services (NYDFS) chartered trust company.
Teams that already read the launch write-up still need the operational sequence: confirm customer access, generate credentials, run issuance and redemption workflows, then wire webhooks for lifecycle events.
Key Takeaways
- Ripple Mint is the institutional UI + API for minting, redeeming, bridging, and tracking RLUSD.
- Launch date: July 23, 2026; available today to existing RLUSD customers per Ripple.
- Transaction types: ISSUANCE (USD to RLUSD), REDEMPTION (RLUSD to USD), and BRIDGE (crypto to crypto).
- API base URL is https://api.ripple.com; UAT sandbox is api.test.ripple.com without moving real funds.
- Named downside: Flexible redemption holds inbound RLUSD PENDING up to 3 hours until you approve FIAT or CRYPTO.
What Ripple Mint is (and is not)
Ripple Mint expands RLUSD access beyond the older platform-only flow. Institutions can operate through a web console for oversight or through APIs and webhooks for automation.
With Ripple Mint, customers can mint and redeem RLUSD from the source, bridge RLUSD across supported chains, track the full transaction lifecycle, and integrate those workflows into internal systems.
This object is not Circle Mint for USDC, not a secondary-market exchange sell, and not a self-serve retail on-ramp. Primary sources: Ripple Insights: Meet Ripple Mint and docs.ripple.com Ripple Mint API get started.
Who this is for (and who should skip it)
Use Ripple Mint when the firm is already an RLUSD customer (or completing Ripple institutional onboarding) and needs direct mint, redeem, bridge, and programmatic reconciliation.
Skip it when the job is Circle USDC Mint, when the team only needs a venue cash-out, or when no Ripple customer relationship exists yet. Ripple states Ripple Mint is available to existing RLUSD customers today.
Mint and redeem checklist (2026)
1. Confirm Ripple Mint access and Admin role
Log in to the Ripple Mint UI with an Admin user. API credential generation requires Admin. If the console is missing, finish institutional onboarding with Ripple before any mint or redeem attempt.
Keep the launch context handy: Ripple Mint launch and Notabene investment. Supply and jurisdiction context for RLUSD lives in the RLUSD Q2 2026 report.
2. Generate API credentials (Production or UAT)
In Ripple Mint UI: Settings gear → Integration → API Credentials. Select UAT (sandbox) or Production, then New Credential → Save and Generate Key.
Copy the Client ID and Client Secret immediately. Ripple docs state the client secret is shown only once and cannot be retrieved later. A maximum of three API credentials can be created per account.
3. Obtain a Bearer access token
Exchange credentials for a JWT with POST https://api.ripple.com/v2/oauth/token. Use grant_type=client_credentials plus client_id, client_secret, and audience urn:ripplexcurrent-prod:<your_tenant_id>.
Tokens expire after 1 hour (expires_in: 3600). Ripple does not issue a refresh token; request a new token before expiry. Send Authorization: Bearer <access_token> on every API call. Source: Ripple Mint authentication docs.
OAuth scopes: rlusd_customers:read for transaction reads; rlusd_customers:write to approve pending redemptions (and, in UAT, to create sample transactions).
4. Understand transaction types before moving funds
| Type | Source → Destination | What happens |
|---|---|---|
| ISSUANCE | FIAT → CRYPTO | USD received; RLUSD minted to your crypto wallet |
| REDEMPTION | CRYPTO → FIAT | RLUSD burned; fiat settled to your default bank account |
| BRIDGE | CRYPTO → CRYPTO | Cross-chain RLUSD transfer between two wallets |
Statuses you will see: PROCESSING, PENDING (flexible redemption only), COMPLETED, and FAILED. Production base URL is https://api.ripple.com. Source: Ripple Mint transactions docs.
5. Mint RLUSD (issuance path)
Issuance is USD → RLUSD. Ripple mints RLUSD automatically after confirmed fiat receipt. Webhook lifecycle for issuance: USD received → PROCESSING → on-chain settlement → COMPLETED.
Operationally: fund via the bank instructions Ripple configures for your account, confirm the destination wallet in the console or integration, then track with GET /v1/stablecoin/transactions (filter transactionTypes=ISSUANCE) or GET /v1/stablecoin/transactions/{id}.
On COMPLETED, webhook eventData.destinationHash carries the on-chain transaction hash for reconciliation.
6. Redeem RLUSD (default auto-redemption)
Default redemption is RLUSD → USD. Ripple redeems and initiates fiat settlement automatically when on-chain RLUSD is received: RLUSD received → PROCESSING → fiat settled → COMPLETED.
Fiat payouts settle to your default bank account as configured in the Ripple Mint UI. Query completed redemptions with transactionTypes=REDEMPTION&statuses=COMPLETED.
For a broader issuer-vs-secondary-market frame, see how to redeem a stablecoin for dollars. That guide is issuer-general; this checklist is Ripple Mint specific.
7. Optional: Flexible redemption and approve destination
Flexible redemption holds inbound RLUSD in PENDING for up to 3 hours until you approve destination. Enable it in Ripple Mint UI: Settings → Stablecoin → Manage settings → Enable flexible redeem → On.
Approve with PUT /v1/stablecoin/transactions/{id}/destination and scope rlusd_customers:write. Body {"type":"FIAT"} creates a REDEMPTION to the default bank. Body {"type":"CRYPTO","walletRipId":"RIP0000001"} creates a BRIDGE to that wallet id.
Only PENDING transactions can be updated. Changing destination after PROCESSING or COMPLETED returns 409 Conflict. Once type is set, it cannot be changed.
8. Wire webhooks and test in UAT
Ripple delivers HTTPS webhooks when transaction state changes. Endpoint registration is handled by Ripple during onboarding; contact your Ripple representative to register or update the URL. HTTP and authenticated callback URLs are not supported.
Expect at-least-once delivery and possible duplicate PROCESSING events. Deduplicate on transaction id and updatedAt. Return HTTP 200 or Ripple retries with exponential backoff up to about 72 hours (up to 75 attempts). Source: Ripple Mint webhooks docs.
UAT lives at api.test.ripple.com for integration testing without real funds. UAT can POST /v1/stablecoin/transactions sample ISSUANCE, REDEMPTION, BRIDGE, or PENDING scenarios. See UAT sandbox docs.
Stablecoin Insider's take
If the stack is USDC payout rails instead, use how to send a Circle stablecoin payout. Keep issuer products separate in runbooks so ops never mix Circle Mint and Ripple Mint credentials.
Need the launch context before you open a ticket with Ripple?
FAQ
What is Ripple Mint used for?
Ripple Mint is Ripple's institutional platform to mint, redeem, bridge, and track RLUSD through a web console or API.
It is available to existing RLUSD customers, per Ripple's July 23, 2026 announcement.
How do you mint RLUSD with Ripple Mint?
Fund USD per Ripple's bank instructions for your account, then track ISSUANCE transactions until COMPLETED after on-chain settlement.
Ripple mints RLUSD automatically after confirmed fiat receipt; use GET /v1/stablecoin/transactions to reconcile.
How do you redeem RLUSD with Ripple Mint?
Send RLUSD on-chain into the configured flow; default auto-redemption moves PROCESSING to COMPLETED when fiat settles to your default bank account.
If Flexible redemption is on, approve PENDING with PUT /v1/stablecoin/transactions/{id}/destination and type FIAT or CRYPTO.
What API endpoints does Ripple Mint document for transactions?
Production base URL is https://api.ripple.com. Documented transaction routes include GET /v1/stablecoin/transactions, GET /v1/stablecoin/transactions/{id}, and PUT /v1/stablecoin/transactions/{id}/destination.
Auth uses POST /v2/oauth/token with client credentials. Do not invent undocumented create-mint routes for Production.
Is Ripple Mint the same as Circle Mint?
No. Ripple Mint is for RLUSD under Ripple's institutional stack. Circle Mint is Circle's product for USDC mint and redeem.
Keep credentials, bank rails, and runbooks separate.
What happens if Flexible redemption stays PENDING?
Inbound RLUSD can remain PENDING for up to 3 hours until you approve a FIAT or CRYPTO destination.
Only PENDING rows accept the approve call; other statuses return 409 Conflict. Reconcile with GET transaction and your Ripple liaison if the window is missed.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}