Skip to main content
Treasury management and programmable asset movement follow the custody architecture used for 24/7 payments. The same governing rule applies across all three applications:
A custody provider is used whenever private keys are needed to hold or transfer digital assets on a blockchain that an external party could also access.
The rule separates the system into two parts. The Cosmos Tokenization Suite (CTS) governs balances that exist only inside the bank’s tokenization environment. The custodian holds assets on shared or public networks where another party can transact against the same ledger.

​
The shared pattern

In each application, CTS decides what should move and when. The custodian handles the key material that makes the movement possible:
  1. The Cosmos Tokenization Suite evaluates a condition, whether an accumulated obligation, a treasury policy, or an on-chain trigger.
  2. CTS calls the custodian API with the intended transfer.
  3. The custodian applies the bank’s signing policy, which may require human approval depending on amount, destination, or asset.
  4. The custodian signs and broadcasts the transaction.
  5. CTS observes finality and updates its own records and the core ledger.
The bank’s controls reside in step 3 on the custodian side. They therefore continue to apply when the movement is initiated programmatically.

​
Treasury management

Treasury operations are movements of the bank’s own assets rather than client funds. They include rebalancing across networks, funding settlement wallets ahead of expected volume, and sweeping balances back to a primary account.
The supported policy types, the rebalancing triggers CTS evaluates, and the reporting surface are scoped per deployment. Contact sales@cosmoslabs.io to design a treasury configuration.

​
Programmable asset movement

Programmable asset movement is the execution of transfers in response to conditions rather than manual instructions. Examples include releasing funds when a delivery condition is met or moving balances on a schedule.
The condition types, how policies are authored and approved, and the failure and retry behavior are scoped per deployment. Contact sales@cosmoslabs.io to design a programmable movement configuration.