Skip to main content
Version: Current guides

Send an ordinary or private payment

Before sending​

Ask the recipient for the exact network, asset and full receiving information. The 0x prefix does not distinguish EVM networks, and a short payment link is not an ordinary address. Check that the current account can sign and holds both the payment asset and the network fee asset.

Steps​

  1. Open Send from Home or the asset details and choose a token and specific network. All networks is an aggregate view; payment must use an actual network.
  2. Paste, scan or choose a recipient from the available address book. Expand and verify the full address rather than relying on a label, avatar or a few final characters.
  3. For a private code or link, check the resolved network, token, receiving information and fixed amount. If resolution fails, do not rewrite the link as an ordinary address to proceed.
  4. Enter the amount and check the available ordinary/private options. The newer sending flow may put token, recipient and amount steps in one sheet rather than starting with a mode-selection page.
  5. If a private payment offers Hide amount, verify that this request supports it. An unavailable option or unknown state does not mean entering the private screen has hidden the amount.
  6. Open the preview and check the paying account, recipient, amount, network fee and change. Preview again after an amount change. MAX does not remove the need to reserve fees.
  7. Complete the requested identity check, confirm once, wait for the result and retain the transaction identifier.

After switching modes or changing details​

Recheck recipient compatibility, any fixed amount, fees and change. Do not reuse earlier estimates or manual note selections. Ordinary transfer support does not establish private payment support for the same asset and network.

Failures and interruptions​

SituationNext step
Address/network mismatchConfirm with the recipient and correct it before previewing again
Insufficient funds or feesCheck which assets pay the amount and fees; see Fees
Cancellation during proof creation or before signingCheck the original record and establish that nothing was submitted before starting again
Hash exists, submitted message or timeoutCheck Transaction records and wait for the original result rather than sending again
Approval completed but payment failedApproval is not payment; inspect the current step and only use an explicitly offered continuation
Failure displayedDistinguish pre-signing failure from on-chain execution failure; the latter may still cost network fees

Closing a sheet or leaving the app does not cancel a broadcast transaction. A timeout is not evidence that no funds were spent. Follow Missing transfers when the result is unclear.