Canton assets can now be managed through Ripple Custody's API. The 1.43 release, dated October 5, adds support for holding and transferring Canton Coin and tokens using the CIP-56 standard.
The integration connects to a Canton validator operated by the customer or its node provider. Ripple does not supply the validator. Each account's signing key stays in the custody vault, and transactions are checked against the customer's custody policies before signing.
Incoming transfers can use pre-approvals, allowing an account to receive an asset without signing every receipt. For transfers that require acceptance, customers can accept or reject incoming offers and withdraw outgoing offers the recipient has not acted on.
Support is available for on-premises deployments and the hybrid SaaS model, but it requires phase two of Ripple's ledger accounting upgrade. Canton management is API-only in this release. The SaaS version is being deployed progressively, and customers must contact their Ripple liaison with validator details to enable the hybrid connection.
The Canton integration guide also defines the limits: it does not support arbitrary Canton application commands or delivery-versus-payment workflows. CIP-56 token support covers tokens published through the Digital Asset Registry.
Customers planning an integration can review the official release notes and validator connection requirements before enabling Canton support.
