# Change history 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. ### April 2026 details summary Click to expand **New `payinCategory` values (preferred) and deprecation notice** Two new preferred `payinCategory` values are now available on v2 quote and payment endpoints: - `PRE_FUNDING` — replaces the deprecated `FUNDED` value. - `CREDIT_FUNDING` — replaces the deprecated `T_PLUS_ONE` value. - `JIT_FUNDING` — for just-in-time funded payments (see below). The legacy values `FUNDED` and `T_PLUS_ONE` continue to be accepted on v2 endpoints but are deprecated and will be removed in a future release. New integrations should use the new values. For details, see [Quotes](/products/payments-direct-2/v2025.11/api-docs/concepts/quotes#funding-model-payincategory). **New field: `jitFundingExpiresAt`** Payment objects now include an optional `jitFundingExpiresAt` field (date-time, UTC) indicating the deadline by which funds must arrive for a `JIT_FUNDING` payment. This field is present only on JIT-funded payments. **New field: `payoutExecutionDetails`** `GET /v2/payments/{paymentId}` responses now include an optional `payoutExecutionDetails` object when available. This object provides: - `paymentRailUsed` — the payment rail used to execute the payout (for example, ACH, Fedwire, SEPA). - `payoutStartTime` / `payoutEndTime` — payout timing in UTC. - `trackingReferences` — network-specific identifiers such as IMAD/OMAD for Fedwire, useful for audit and reconciliation. This field is informational only. Availability varies by corridor and payout partner. For details, see [Create a v2 payment](/products/payments-direct-2/v2025.11/api-docs/tutorials/create-a-v2-payment). **New optional field: `paymentMemo`** The `paymentMemo` field is now documented on the payment request body. It is an optional transaction-specific memo forwarded with the payment for beneficiary reconciliation. Validation rules (allowed characters, maximum length) vary by corridor. **Deprecated ledger operations** The ledger operations `VOID_PREFUND_BALANCE` and `OVERRIDE_PREFUND_BALANCE` are deprecated. They may appear in historical ledger records but are no longer generated for new transactions. For details, see [Ledger transactions](/products/payments-direct-2/v2025.11/api-docs/concepts/ledger-transactions). ### March 2026 details summary 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 (this version)** - 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**. ### January 2026 details summary 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](/products/payments-direct-2/v2025.11/api-docs/concepts/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](/products/payments-direct-2/v2025.11/introduction/concepts/payment-lifecycle) and [Payment returns](/products/payments-direct-2/v2025.11/api-docs/concepts/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. ### November 2025 details summary Click to expand **Enhancements and payout network expansions** - Released the Transaction Memo feature for EUR/GBP payouts - Payouts enabled: PHP, CN-USD, and INR ### October 2025 details summary 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 ### September 2025 details summary Click to expand **Enhancements** - Released FedWire payouts with Lead Bank - Released FX benchmark improvements to reduce price gaps with stablecoins ### August 2025 details summary 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](https://github.com/ripple/payments-direct/blob/main/openapi_spec/rpd2_spec.yml). ### July 2025 details summary Click to expand **Enhancements** - Released off-ramp capabilities to deliver RLUSD ### June 2025 details summary Click to expand **Additional payout markets enabled** - RTP payouts enabled in the US - EUR/GBP payouts enabled ### May 2025 details summary Click to expand **Additional payout markets enabled** - Payouts enabled for BRL, CNY, GHS, NGN, RWF, ZAR, UGX, and ZMW ### April 2025 details summary 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 ### March 2025 details summary 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 ### February 2025 details summary 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: - [Ripple Payments Direct 2.0](/products/payments-direct-2/v2025.11/introduction/ripple-payments-direct) - [Send an individual payment](/products/payments-direct-2/v2025.11/user-interface/tutorials/send-an-individual-payment)