Overview#
Sending assets moves them out of a Team Wallet. Every transfer is validated against the Policy Engine before it reaches signing, and is then executed directly, routed to approval, or blocked according to the result.Before you begin#
You are in the correct Team and wallet;
You hold the Initiate transactions permission;
The wallet holds enough to cover the network fee, or Gas Service is enabled and funded;
You have verified the destination address and network through a trusted channel;
If your Team has enabled the Manual Transfer Restriction, the destination address is in the whitelist and Active.
Initiating a transfer#
Open Send in a wallet and complete the following.| Field | Notes |
|---|
| Token | Selected from wallet assets. The network follows from the token and is shown on screen |
| Destination address | Select from the whitelist or your Team Wallets, or enter manually or by QR code |
| Amount | The available balance for that token is shown, along with the US dollar equivalent |
| Network fee | Estimated and displayed by the system |
| Note | Up to 100 characters, visible within your Team only; not written on-chain |
Destination addresses carry a source label. Addresses chosen from the whitelist show a whitelist label and their group; Team Wallets show a Team Wallet label; manually entered addresses show as ordinary addresses. This label is your first check on whether an address can be trusted.When selecting a whitelist address, you can search by name, address, group, or tag. Only addresses that are Active and match the network of the current transfer can be selected.Reviewing and submitting#
The confirmation screen summarizes the transfer. Check each of the following before submitting:Token and network. Confirm the network matches the recipient's. Transfers on a mismatched network usually cannot be recovered.Destination address. Verify the full address character by character, not just the first and last few — malware exists that alters clipboard contents and substitutes a visually similar address. Also confirm the source label is what you expect: a transfer intended for a whitelisted counterparty that shows as an ordinary address suggests the address may have been swapped.Amount. Confirm the order of magnitude and decimal places.Network fee. The estimate changes with on-chain conditions, and the amount actually deducted may differ.Once verified, submit. Submitting requires identity verification — Face ID or fingerprint if Biometric Payment is enabled, or your Wallet Password if it is not.After submission the transaction enters the subsequent stages and can be tracked in Transaction Records. An on-chain transaction cannot be reversed once broadcast.Approval and signing#
A submitted transaction passes through policy validation, approval, and signing.Policy validation is performed automatically by the Policy Engine, which determines whether the transaction should be released, routed to approval, or blocked. The Matched policy field in the transaction details shows which policy applied.Approval is triggered when the transaction matches a policy whose action is to require approval. The Approval Node referenced by that policy determines who handles it. Approvers see the item in the Approval Workbench in the app, review the transaction details, and approve or reject. When several approvals are required, the transaction stays at this stage until enough are collected.Signing begins after approval, performed by members holding the Approve transactions permission. Before signing, each participating member independently verifies that the content to be signed matches the transaction information shown at approval; if they do not match, signing stops. This is the second line of defense after approval.Only once signing completes is the transaction broadcast on-chain.Approval and signing progress is visible in the transaction details: completed stages show who handled them and when, and pending stages list who is expected to act. If a transaction sits at one stage for a long time, this tells you where it is waiting.Why a transfer may be restricted#
No permission to initiate transactions. Initiating a transfer requires the Initiate transactions permission, which you can check in your member details.Insufficient balance or network fee. Beyond the amount being sent, the wallet must cover the network fee. Gas Service can cover it instead.Address format error or network mismatch. The address must match the format of the selected network.Destination not in the whitelist. If your Team has enabled the Manual Transfer Restriction, transfers can only go to whitelist addresses that are Active and match the network.Blocked by policy. The transaction matched a policy whose action is to block, or it matched no policy at all — the Policy Engine denies by default, so a transaction not covered by any policy cannot proceed.Daily limit exceeded. Daily limits are calculated across the Team's transactions for the day and reset at 00:00 Beijing time (UTC+8).Things to note#
Send a small test transfer before a large one. The first time you send to an address, transfer a small amount to verify the address and network, confirm it arrives, and only then send the full amount.Watch for changes to the address source label. If a destination address is removed from the whitelist or its group changes after a transaction is submitted, the approval detail flags the difference between the current state and the state at submission. Approvers should re-verify before proceeding.Do not leave approvals sitting. A pending transaction occupies the approval flow. If you have doubts, reject it and check with the initiator rather than leaving it unhandled.Modified at 2026-08-26 02:51:05
