# 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 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](/products/payments-direct-2/api-docs/concepts/quotes#funding-model-payincategory) and [Payment states](/products/payments-direct-2/api-docs/concepts/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_FUNDING` replaces `FUNDED` - `CREDIT_FUNDING` replaces `T_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](/products/payments-direct-2/api-docs/concepts/payment-states). **New API endpoint: `GET /v3/identities/by-internal-id/{internal-id}`** You can now retrieve an active identity using your own client-provided `internalId`, without needing the Ripple-generated `identityId`. The endpoint returns only identities in the `ACTIVE` state and always returns the latest version. For more information, see [Create and manage identities](/products/payments-direct-2/api-docs/tutorials/create-and-manage-identities). **New financial instrument type: `SWIFT`** `SWIFT` is now a supported financial instrument type for cross-border wire transfers via the SWIFT network. Required fields: `bankName`, `swiftCode`, `accountHolderName`, and `accountNumber`. Settlement is 1–4 business days depending on corridor. For more information, see [Financial instruments](/products/payments-direct-2/api-docs/concepts/financial-instruments). **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, including `paymentRailUsed`, `payoutStartTime`, `payoutEndTime`, and `trackingReferences` (network-specific identifiers such as IMAD/OMAD for Fedwire). Coverage varies by corridor and partner. For more information, see [Payment execution details](/products/payments-direct-2/api-docs/concepts/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](/products/payments-direct-2/api-docs/concepts/financial-instruments). ### 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/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/introduction/concepts/payment-lifecycle) and [Payment returns](/products/payments-direct-2/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/introduction/ripple-payments-direct) - [Send an individual payment](/products/payments-direct-2/user-interface/tutorials/send-an-individual-payment)