Ripple Custody adds Canton Network support for institutions

Ripple Custody now supports the Canton Network. Institutions can hold and move Canton assets without leaving the custody platform they already use.

What version 1.43 actually does

The support arrives in Ripple Custody version 1.43, which launched on October 5, 2026. The headline feature is the ability to hold and transfer Canton Coin (CC), which also goes by the name Amulet.

Canton Coin is not the only asset covered. The release also handles any CIP-56 tokens issued through the Digital Asset (DA) Registry, the token standard used for assets created on Canton.

The architecture is the more interesting part. Ripple is using a bring-your-own-validator (BYOV) model, which means clients connect the custody platform to validators that they, or their node providers, already operate.

Signing keys stay put. They remain in the customer’s own vault, whether that is a hardware security module (HSM) or a key management service (KMS), so Ripple is not holding the keys to anyone’s kingdom.

Existing custody policies and approval workflows carry over to every Canton transaction on the platform.

The release also adds pre-approvals for incoming assets and two-step transfer offers. In practice, a transfer is proposed first and accepted second, rather than landing in an account unannounced.

Prepared transactions come with a 24-hour signing window. That gives approvers a full day to review and sign before a transaction goes stale.

There are limits. Canton support is available only through the API for now, with no direct support for arbitrary Canton application commands or delivery-versus-payment (DvP) workflows.

On deployment, the integration works with both on-premises installations and hybrid SaaS environments.

Why Canton matters to regulated finance

Canton is a public Layer 1 blockchain that has found favor with regulated financial institutions. The network offers sub-transaction privacy and runs on what it describes as a “network of networks” structure. Participant nodes only see the data relevant to them, rather than broadcasting every detail to the entire world.

Major financial institutions including Goldman Sachs and BNY Mellon are using Canton infrastructure for tokenized assets.

What this means for institutions and Ripple

The most direct impact is consolidation. Institutions can now manage Canton assets alongside their other digital holdings without bringing on a separate custodian just for Canton.

The BYOV approach lets institutions bring their own validators and keep signing keys in their own HSM or KMS. Ripple’s platform enforces the rules, but the client holds the cryptographic keys that authorize anything moving.

Still, the current version has clear boundaries. API-only access means institutions need the technical capacity to integrate, and the lack of DvP and arbitrary application command support keeps more advanced Canton use cases outside the platform for now.