Change history

New financial instrument types: China

Four new financial instrument types support additional China payout scenarios:

• CN_TRADE (cnTrade) — CNY trade payouts via CNAPS (purpose code restricted to GDDS or SCVE)
• CN_INDIVIDUAL (cnIndividual) — CNY payouts to individual accounts via CUP or CNAPS
• CN_INDIVIDUAL_TRADE (cnIndividualTrade) — CNY individual trade payouts via China UnionPay (CUP)
• CN_CFXPS (cnCfxps) — USD payouts to China via Cross-Border Foreign Exchange Payment System (CFXPS)

New financial instrument types: Crypto wallets

Three new financial instrument types support stablecoin payouts to crypto wallet addresses:

• ETH_WALLET (ethWallet) — USDT, USDC, and RLUSD payouts on the Ethereum network
• TRON_WALLET (tronWallet) — USDT payouts on the Tron network
• SOL_WALLET (solWallet) — USDC payouts on the Solana network

All crypto wallet instruments return ZZ for the country metadata field.

New financial instrument type: Hong Kong bank payout

HK_BANK_PAYOUT (hkBankPayout) enables HKD payouts to Hong Kong bank accounts via CHATS. Required fields include bankName, accountNumber, accountHolderName, and swiftCode. Pre-clearance is required for all senders.

New financial instrument types: Africa bank payouts

Five new financial instrument types for African bank payouts are now available, enabling NGN-era corridor expansion to additional markets:

• GH_BANK_PAYOUT (ghBankPayout) — Ghana (GHS), via GIS
• RW_BANK_PAYOUT (rwBankPayout) — Rwanda (RWF), via RSwitch. Supported use case: C2B2C only.
• ZA_BANK_PAYOUT (zaBankPayout) — South Africa (ZAR), via PayShap. Supported use case: C2B2C only.
• UG_BANK_PAYOUT (ugBankPayout) — Uganda (UGX)
• ZM_BANK_PAYOUT (zmBankPayout) — Zambia (ZMW), via ZECHL

For field-level details on all new instrument types, see Financial instruments.

Bank Codes lookup

The Bank Codes lookup utility now covers all supported bank code corridors in a single interface. Select the destination country to view supported bank codes; for countries with multiple currencies, select the currency to narrow results.

• Nigeria (NGN): Returns Ripple Bank Codes (RBCs) in the format RPL:NG:[ALIAS]:BNK.
• China (CNY): Returns CNAPS codes (China National Advanced Payment System).
• China (USD): Returns SWIFT/BIC codes.

For more information, see Bank Codes.

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_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.

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.
• 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.

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.

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.

Reduced data requirements for US ACH

Based on customer feedback, the following identity fields are no longer required when creating identity tokens for US ACH payments:

• registration — no longer required for BUSINESS ORIGINATOR and BUSINESS BENEFICIARY identities
• identityDocuments — no longer required for INDIVIDUAL BENEFICIARY identities

For an updated list of required fields by corridor, use the Payload Schema Utility.

Corrected GET /v2/ledger-transactions response schema

The response schema for GET /v2/ledger-transactions was incorrectly defined as an array. It has been corrected to an object containing pagination metadata (offset, pageSize, pageElements, total) and a statementTransactions array. Customers using OpenAPI generators against a previous version of this spec may need to regenerate their client code. The text/csv response schema has also been corrected and now includes column documentation and an example row.

Documentation versioning: v2026.03 and v2025.11

The Payments Direct documentation is now versioned. Use the version selector to switch between versions:

• v2026.03 (this version) - Documents the Payments Direct API with Identity Management v3, including the v3 identity and financial instrument endpoints.
• v2025.11 - Documents the Payments Direct API with Identity Management v2.

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.

Enhancements and payout network expansions

• Released the Transaction Memo feature for EUR/GBP payouts
• Payouts enabled: PHP, CN-USD, and INR

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

Enhancements

• Released FedWire payouts with Lead Bank
• Released FX benchmark improvements to reduce price gaps with stablecoins

Enhancements

• Released Maker/Checker feature in Payments Direct, enabling payment approval workflows
• Released the OpenAPI specification for Payments Direct, available for download here.

Enhancements

• Released off-ramp capabilities to deliver RLUSD

Additional payout markets enabled

• RTP payouts enabled in the US
• EUR/GBP payouts enabled

Additional payout markets enabled

• Payouts enabled for BRL, CNY, GHS, NGN, RWF, ZAR, UGX, and ZMW

Enhancements and network expansions

• ACH payouts enabled using iPayout
• Payments Direct on-ramps launched for customers to send in stablecoins, beginning with USDC and USDT
• Re-designed payment flow in Payments Direct to simplify and enhance the user experience

Off-ramps Beta launched

Off-ramps beta launched for Payments Direct customers, allow customers to pay-in stablecoins in key payout markets

Offical launch of Payments Direct

Payments Direct, 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 Payments Direct, you can send payments and manage beneficiaries using the Payments Direct UI.