This page summarizes notable changes made to Ripple Payments Direct 2.0. This change history is arranged in order from the most recent change and it corresponds to the month and year the enhancements and fixed issues were made available.
Click to expand
New Quote v3 endpoints
The quote endpoints have been updated to /v3/quotes/*. Key changes from the previous version:
payoutCategoryanddestinationBlockchainNetworkare no longer accepted in quote requests.- A new optional
paymentRailfield is available in quote requests. When specified, only quotes for the given payment rail are returned. When omitted, quotes for all supported rails are returned. - The fee breakdown in quote responses now includes a
paymentRailfield identifying the rail associated with each fee.
For more information, see Quotes and Create a payment.
New funding model: Just-in-time (JIT) funding
A new payinCategory value, JIT_FUNDING, is now available when creating quotes. JIT-funded payments enter a new AWAITING_FUNDING state after creation and proceed once funds are received in your Ripple ledger account before the jitFundingExpiresAt deadline. For more information, see Funding model and Payment states.
New payinCategory values: PRE_FUNDING and CREDIT_FUNDING
Two new payinCategory values are introduced as the preferred replacements for the deprecated values:
PRE_FUNDINGreplacesFUNDEDCREDIT_FUNDINGreplacesT_PLUS_ONE
The deprecated values FUNDED and T_PLUS_ONE continue to be accepted on v2 quote endpoints and are not being removed at this time. New integrations should use the new values.
New payment state: AWAITING_FUNDING
A new non-terminal payment state, AWAITING_FUNDING, is introduced for JIT-funded payments. For more information, see Payment states.
New payment response fields: payoutExecutionDetails and jitFundingExpiresAt
The GET /v3/payments/{paymentId} response now includes two new fields:
payoutExecutionDetails(optional): metadata about how a payment was executed, includingpaymentRailUsed,payoutStartTime,payoutEndTime, andtrackingReferences(network-specific identifiers such as IMAD/OMAD for Fedwire). Coverage varies by corridor and partner. For more information, see Payment execution details.jitFundingExpiresAt: present on JIT-funded payments; indicates the deadline by which funds must be transferred to your Ripple ledger account for the payment to proceed.
Renamed financial instrument type: AFRICA_BANK_PAYOUT is now NG_BANK_PAYOUT
The Africa bank payout financial instrument type has been renamed from AFRICA_BANK_PAYOUT to NG_BANK_PAYOUT. Update any integration code, identity validatePayoutRails arrays, or internal tooling that references the old value. For more information, see Financial instruments.
Click to expand
Documentation versioning: v2026.03 and v2025.11
The Ripple Payments Direct 2.0 documentation is now versioned. Use the version selector to switch between versions:
- v2026.03 - Documents the Ripple Payments Direct 2.0 API with Identity Management v3, including the v3 identity and financial instrument endpoints.
- v2025.11 - Documents the Ripple Payments Direct 2.0 API with Identity Management v2.
Click to expand
New API endpoint: GET /v2/ledger-transactions
Provides a paginated list of ledger transactions and running balances for a specified UTC time range, supporting customer reconciliation and operational reporting. For more information, see Ledger transactions.
New payment state: RETURNED
Payments that were previously marked as COMPLETED but later reversed by the payout partner or network are now marked as RETURNED. For more information, see Payment lifecycle and Payment returns.
Feature enhancement: Tax transparency
We have introduced a detailed tax breakdown structure to both Quote and Payment responses to support transparent reporting of tax liabilities and service fees.
Click to expand
Enhancements and payout network expansions
- Released the Transaction Memo feature for EUR/GBP payouts
- Payouts enabled: PHP, CN-USD, and INR
Click to expand
Enhancements and payout network expansions
- Released the Transaction Memo feature for USD payouts
- Payouts enabled: AED, AUD, CLP, COP, JPY, IDR, KRW, PEN, THB, and VND
Click to expand
Enhancements
- Released FedWire payouts with Lead Bank
- Released FX benchmark improvements to reduce price gaps with stablecoins
Click to expand
Enhancements
- Released Maker/Checker feature in Ripple Payments Direct 2.0, enabling payment approval workflows
- Released the OpenAPI specification for Ripple Payments Direct 2.0, available for download here.
Click to expand
Enhancements
- Released off-ramp capabilities to deliver RLUSD
Click to expand
Additional payout markets enabled
- RTP payouts enabled in the US
- EUR/GBP payouts enabled
Click to expand
Additional payout markets enabled
- Payouts enabled for BRL, CNY, GHS, NGN, RWF, ZAR, UGX, and ZMW
Click to expand
Enhancements and network expansions
- ACH payouts enabled using iPayout
- Ripple Payments Direct 2.0 on-ramps launched for customers to send in stablecoins, beginning with USDC and USDT
- Re-designed payment flow in Ripple Payments Direct 2.0 to simplify and enhance the user experience
Click to expand
Off-ramps Beta launched
Off-ramps beta launched for Ripple Payments Direct 2.0 customers, allow customers to pay-in stablecoins in key payout markets
Click to expand
Offical launch of Ripple Payments Direct 2.0
Ripple Payments Direct 2.0, allows you to connect to Ripple as a payments provider. Ripple takes care of delivering payments to beneficiaries, managing payout partners, providing funds to payout partners, and paying charges in exchange for payment delivery to the beneficiaries. With Ripple Payments Direct 2.0, you can send payments and manage beneficiaries using the Ripple Payments UI.
For more information, see the following topics: