Skip to navigation

Wallet Operations

View as Markdown

Use the selected workspace’s menus and permissions as your starting point. Personal and team wallets emphasize wallet assets and device signing; enterprise workspaces also expose business approval and operational views.

Receive assets

Choose the intended network and asset, then use the receiving details supplied for that wallet or business user. Some networks require a memo or tag in addition to an address. Keep these details together and verify them before sending.

An address being allocated does not mean a deposit has arrived. Track the deposit record, chain confirmations and any risk hold separately. A chain transaction can be visible before funds become available in the business account.

Transfer assets

  1. Select the source wallet or balance and enter the destination, amount and required memo.
  2. Review the preview, fee information and destination checks. Ensure the relevant fee asset is available where the wallet model requires it.
  3. Submit once and keep the request identifier. Complete the approvals or device confirmations presented by the product.
  4. Follow signing, broadcasting and chain confirmation until the final result is established.

Approval does not mean the transaction is signed, and broadcasting does not mean it is confirmed. Personal and team flows should not be assumed to use the same web approval process as enterprise withdrawals.

Understand enterprise wallet roles

RolePurpose
Deposit walletReceive incoming assets and support collection workflows
Hot or withdrawal walletHandle operational outgoing transfers
Transit walletMove assets between operating and reserve arrangements
Reserve walletHold assets under a signing arrangement suited to reserve use

Some products also distinguish fee funding or isolated funds. These are operating roles, not a promise that every product exposes every wallet type. A reserve label alone does not prove that devices are offline.

Reconcile uncertain results

Compare the business request, wallet record and chain transaction. Keep available balances, frozen balances, ledger entries and chain observations distinct.

If a request times out or remains under verification, query its existing record. Do not create another transfer simply because a success screen or notification is missing. Cancellation is conditional on the actual signing state; a submitted cancellation is not proof that funds cannot move. Developers should follow transactions and retries.