Skip to main content
Version: Current guides

Receive funds and generate a payment code

Receive at an ordinary address​

  1. Select the receiving wallet account and open Receive.
  2. Choose the asset and network and verify the full address. Even when addresses match, the sender must use the same network.
  3. Copy the address or share its QR code from the app, together with the asset and network. An abbreviated address display is not a complete receiving address.
  4. Ask for a small test transfer. Use its transaction hash to check confirmation on the correct network, then inspect that account's ordinary balance.

Do not assume an asset/network combination is supported merely because a product introduction mentions it. Ordinary transfer support also does not establish private payment support.

Private payment codes​

If your current version provides this entry, choose private receiving and select a currently supported network, token and receiving account.

  1. Wait for generation to finish before copying or sharing the displayed code/link. Do not use an old screenshot from a loading or failed state.
  2. For a fixed amount, open Set amount, enter the token quantity and confirm. Check the generated amount again and ask the payer to verify the same quantity in their preview.
  3. If an expiry option is available, configure and check it. Amount, usage count and expiry are separate restrictions; a fixed amount alone does not establish single use.
  4. Share the full receiving content and ask the payer to scan or open it through a compatible payment entry. Do not paste a private code into an ordinary address field.
  5. After payment, check the receipt record, amount and settlement state. A private receipt does not necessarily mean your ordinary balance has increased.

Changes and expiry​

After changing the token, network, account, amount or expiry, verify and share the currently generated content. Do not assume an old screenshot remains valid. Regenerate an invalid or used request. If a payment is already processing, check the original record before asking the payer to pay again.

Codes without an expiry may allow repeat payments; time-limited codes may be treated as single-use requests. Follow the current request instructions and payment result. A countdown is not an absolute guarantee of receipt.

Common problems​

  • Code missing or generation fails: Check connectivity and retry. Do not accept payment until generation succeeds.
  • Payer's wallet cannot read it: Check support for that request type. Do not edit its prefix or URL. If changing to ordinary receiving, explicitly tell the payer that the payment method has changed.
  • Unexpected amount: Distinguish token quantity from fiat estimate and compare the fixed amount shown to the payer. Stop if they disagree.
  • Private receipt exists but no ordinary credit: Read Private withdrawals and settlement. For ordinary receipts, follow Missing transfers.