# Ripple Custody 1.41 (September 14, 2026)

Version 1.41 is a short-term support (STS) SaaS release that introduces the following change:

- Address validation for endpoint creation and update


## Address validation for endpoints

Ripple Custody version 1.41 validates endpoint addresses against the target ledger's format when you create or update an endpoint. An address that isn't valid for the selected ledger is rejected before the endpoint is committed.

Requires ledger accounting refactor phase 2
Endpoint address validation activates together with [ledger accounting refactor phase 2](/products/custody/support/change-history/v140#ledger-accounting-refactor-phase-2), introduced in version 1.40. In an environment where phase 2 is not yet active, endpoint addresses are not validated.

Behavior change
Endpoint creation and update now reject an address that doesn't match the selected ledger's format. Previously, Ripple Custody accepted such addresses, and the problem surfaced later as a stuck transaction. Automations that register endpoints without validating the address first may now receive a rejection. Validate addresses before submission, or handle the rejection. A dry run reports the error before you submit.

Validation applies to endpoints on EVM ledgers, Solana, Stellar, Tron, and XRPL. Endpoints on other ledgers are accepted without address validation. A rejected create or update is refused at intent submission with an HTTP 400 response and `reason: "InvalidEndpointAddressError"`; the message echoes the submitted address and the expected format for the ledger. A dry run reports the same failure in the `errors` array before you submit. This error is distinct from the duplicate-endpoint rejection, so integrations can handle it programmatically. Transaction and transfer flows are unchanged.

For the address formats accepted per ledger, see [Supported blockchain ledgers](/products/custody/reference/supported-ledgers#address-formats-by-ledger). For endpoint procedures, see [Manage endpoints](/products/custody/accounts-and-assets/endpoints/manage-endpoints).

## Distribution and deployment

Ripple progressively deploys Version 1.41 across SaaS environments starting September 14, 2026.

## Activation and support

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](https://metaco.atlassian.net/servicedesk/customer/portal/1) or contact your Customer Partner Engineer (CPE).