Canton Policy Rules

Policy rules control who can send, receive, and approve Canton transactions, and which Canton contracts your workspace can interact with. This article explains the two kinds of Canton Policy rules and how to set them up.

Transfer Policy rules

Transfer Policy rules apply to outgoing Canton transfers. To control who accepts or rejects incoming transfers, use Offer response Policy rules. You can set transfer rules for specific vault accounts or across the workspace. For how outgoing and incoming transfers work, see Send Canton transfers and Approve or reject incoming Canton transfers.

To set up a transfer Policy rule for Canton:

1. Go to the Policy Editor in the Console. For general steps, see Create, edit, and publish a Policy.
2. Define the initiator and approver rules: who can create a Canton transfer and who must approve it.
3. Scope the rule by asset (CC, USDCx, or a CIP-56 token), vault account, or counterparty.
4. To restrict destinations, whitelist the Party IDs that transfers are allowed to go to.
5. For high-value flows, require a quorum of approvers.

Offer response Policy rules

Offer response Policy rules control who can accept or reject incoming Canton offers, including transfer offers when you use 2-step approval, and app requests such as onboarding or allocations. Most setups that use Canton applications need these rules.

To set up an Offer response Policy rule:

1. In the Policy Editor, create an Offer response rule.
2. Define who can respond to offers and who must approve the response.
3. Scope the rule by source (vault account).
4. For high-value flows, require a quorum of approvers.

Canton call Policy rules

Canton call Policy rules control how your workspace interacts with Canton templates and contracts, such as app onboarding or settlement actions. They apply to outgoing transactions and are set per vault account. For the apps these calls connect to, see Connect to Canton applications.

To set up a Canton call Policy rule:

1. Go to the Policy Editor in the Console.
2. Define who can create a Canton call, and whether the rule allows or blocks it.
3. Scope the rule by asset (CC, USDCx, or a CIP-56 token).