Version 1.27 is a SaaS release that introduces a new Ripple Custody feature:
- Unspent transaction output (UTXO) allowlisting
Version 1.27 contains the initial, API-only release of our new UTXO change address strategy. This feature supports the critical operational needs of financial institutions by allowing transaction change from assets like Bitcoin (BTC) to be sent to a consistent, primary address.
Previously, Ripple Custody followed the standard BIP32 convention of generating a new change address for every UTXO transaction. Now, when you propose an intent to create a transaction or transfer, you can set the parameter addressForChange as PrimaryAddress or GenerateNewAddress enabling you to send any leftover funds (the unspent "change") back to the first-ever generated address in the wallet, i.e. the PrimaryAddress. If you select GenerateNewAddress everything will remain BIP32 compliant.
- Simplified address allowlisting: By sending change to a single, predictable primary address, you can now easily allowlist this address with counterparties and for regulatory purposes.
- Reliable internal transfers: This new strategy ensures that outgoing transactions always originate from the same address (once UTXOs are consolidated), allowing for reliable validation of internal transfers across different domains.
- Granular API control: In v1.27, you can enable this behavior on a per-transaction basis via a new field in the API, giving you full control over your UTXO flows.
A specific upgrade order is required to avoid service disruption when using the new PrimaryAddress feature.
First, upgrade the Ripple Custody platform to v1.27. Then, upgrade the vault component.
If your vault was upgraded before the platform, you must restart the vault after you upgrade the platform to v1.27.
The 1.27 version will be progressively deployed across SaaS environments starting on October 24, 2025 with production environments scheduled for deployment on November 10, 2025.
Ripple takes great care in testing its applications and ensuring that there are no regressions or breaking changes. Should you experience unexpected behavior, reach out to the Support team by creating a ticket on our Support Portal or contact your Customer Partner Engineer (CPE).