Skip to main content
Version: Current guides

Troubleshoot a missing transfer

Keep the original transaction​

Do not repeatedly press Send, create another order, uninstall or clear app data. Record the paying account, recipient information, network, token quantity, initiation time, order/payment identifier, transaction hash and error. An app timeout, closed page or temporarily missing recipient balance does not prove that payment never occurred.

Step 1: Establish whether it was submitted​

Check Transaction records and the original payment flow.

EvidenceNext step
Explicitly cancelled/not submitted, with no broadcast evidenceCheck the original record and balance before deciding whether to send again
Hash exists or submitted/confirming is shownCheck the original hash on the correct network and wait instead of sending again
Timeout, failed query or unknown resultRestore connectivity and check the original record; no displayed hash does not automatically mean no broadcast
Included on-chain but execution failedReview the error and fees, establish that retry is appropriate, then use an allowed continuation

If an explorer cannot find the hash, check the network first. Temporary absence is not cancellation or a refund and is not enough reason to resend.

Step 2: Check where the recipient is looking​

  1. Compare the full address, token and network. Matching token names or identical 0x addresses do not replace network verification.
  2. For ordinary transfers, inspect the ordinary balance on that network. Clear filters and select the correct account before refreshing. An all-networks fiat estimate is not confirmation of receipt.
  3. For private receipts, check the associated private record first. If pending settlement, follow Private withdrawals. Do not ask the payer to pay again because the ordinary balance has not increased.
  4. For hidden-amount payments, compare actual payment and change. If the deposited amount exceeds what the recipient received, the difference may be your own pending change. See Notes and change.

Step 3: Separate blockchain success from service credit​

For card top-ups or OTC payments, check the blockchain step, then inspect card/bank processing in the original order. Funds received, card processing, review, unknown result and credited are different stages. If your current version offers continuation or retry for the original order, use only the explicitly available action. Do not create another order or send more funds to “unlock” it. See Cards and OTC.

If settlement was submitted, wait on that record; do not repeat it from another device. If balances are correct but an old screen is stale, restore connectivity and refresh the original screen without deleting data.

Contact official support​

Use in-app or verified official support and provide the non-secret identifiers above, current status, time and checks already performed. Redact full card numbers, security codes, identity documents and unrelated private information from screenshots. Never send seed phrases, private keys, unlock passwords, cloud-backup passwords, verification codes, full private credentials or credential recovery material.

For a wrong network or address, preserve evidence and establish whether you still control the destination. Do not trust guaranteed recovery in exchange for another fee. Support, closing a page or resetting the app cannot directly reverse a broadcast transaction. Any possible remedy depends on the actual network, destination and service; recovery or refunds are not guaranteed.