DIGITAL ASSETS

The asset is digital. The responsibilities remain.

Connect issuance, wallets, payments and settlement to the people and systems that operate the financial product.

01ASSET LIFECYCLE

One event. Two sides of the system.

Explore three illustrative architectures. Select a stage to see the business event, its control boundary and the infrastructure response.

Business event ↔ system stateIllustrative architectures · no live transactions

Choose a scenario

Switch to compare assets, networks and controls.

Asset: USDC
Network: Public network
Custody boundary: Policy-controlled treasury wallet

Business event

Instruction

Treasury sets the amount and beneficiary.

Control boundary

Network and asset must match the approved treasury route.

Infrastructure response

System record

Resolve the selected asset contract and destination network.

These are design examples, not client deployments or product recommendations. Network membership, asset representation, settlement and governing documents must be specified for each implementation.

02PAYMENTS, TREASURY & CUSTODY

A payment needs more than a transaction hash.

One payment / two connected recordsIllustrative reconciled payment · no live transaction

Instruction & accounting

Business record

Purpose: Treasury rebalancing
Amount: 125,000 USDC
Beneficiary: Allowlisted treasury wallet
Authority: Within delegated limit

Ledger entry matched to receipt

Execution & evidence

On-chain record

Route: USDC / Ethereum
Wallet control: Policy-controlled MPC signing
Evidence: Transaction receipt linked
Confirmation: Required confirmation policy met

Receipt matched to instruction

PAY-024 / shared instruction reference

Wallets, MPC & custody

Signing authority is a system boundary.

Select a role to see what it controls.

Approval boundary

Check the beneficiary, funding route and transaction limit before authorising this instruction. Approval is recorded separately from the wallet signature.

03BLOCKCHAIN & SETTLEMENT

Choose the network around the operating model.

Public networks

Integrate asset contracts, transaction submission, indexing and network-specific confirmation policies.

Open network · application-level controls

Private networks

Define membership, validator responsibilities, upgrades and interfaces to external systems.

Permissioned access · controlled operations

Sovereign environments

Specify jurisdiction, operator control and infrastructure dependencies alongside the network’s access model.

Governance requirement · not a token standard

Contracts and protocols define asset behaviour. Oracles, external data and interoperability need their own trust and failure boundaries. Moving an asset between networks is a separate design decision.

Explore tokenisation delivery

START A CONVERSATION

Start with one asset or one rail.

Define the lifecycle, the control owners and the first integration boundary.

Discuss a project