What to Do If Your SUI Deposit to Binance Hasn't Arrived?
If your SUI deposit to Binance hasn't arrived, first check the transaction status on a Sui blockchain explorer using the TxID. If the chain shows "Success" but Binance doesn't, it usually means the required number of network confirmations hasn't been reached or Binance has temporarily suspended the deposit service for that network. If it stays missing for more than 2 hours, submit a request through Binance's self-service recovery channel.
1. Find the TxID of This Transfer from the Sending Platform
What to do: Go back to the platform (wallet or exchange) from which you sent the SUI, and copy the TxID (transaction hash) of this transfer.
How to do it:
Case A: Withdrawn from another exchange. Log in to the withdrawal platform, go to withdrawal history, find the SUI transaction, and copy the TxID. If that exchange supports Sui network withdrawals, the record will show the hash.
Case B: Sent from an on-chain wallet. Open your Sui wallet (such as Sui Wallet, OKX Web3 wallet, etc.), locate the transaction record for this transfer, and copy the TxID.
When you're done: You have the TxID of this transaction.
Prerequisite: You can log in normally to the sending platform.
Common failure reason: The sending platform shows "Processing" rather than "Completed". This means the transaction hasn't been packaged yet; it's not a Binance problem – just wait.
2. Check the Transaction Status on a Sui Blockchain Explorer
What to do: Use the TxID to check the real on-chain status of this transfer on a Sui blockchain explorer. Sui is an independent L1; you cannot use Etherscan or BSCScan to look up Sui transactions.
How to do it:
Open a Sui blockchain explorer (we recommend suiscan.xyz or the official explorer) and paste the TxID.
Look at the key information:
Status: Must be Success for the on-chain confirmation to be considered complete.
Confirmations: Binance usually requires that the Sui network reaches a certain number of confirmations before crediting the deposit. If the confirmation count is very low or shows "Pending", transactions are still in the queue – just keep waiting.
Receiving address: Verify that it matches your Binance SUI deposit address.
When you're done: You have confirmed on the Sui explorer that the status is "Success" and the confirmation count is sufficient.
Prerequisite: You have the TxID from Step 1.
Common failure reason: Using Etherscan or BSCScan to look up a SUI transaction. SUI is the native token of the Sui network – a completely different chain from Ethereum and BSC.
3. Check Binance Deposit History and Network Status
What to do: If the explorer shows Success but your Binance account hasn't received the deposit, check your Binance deposit history and the network status.
How to do it:
Go to [Funds] - [Deposit History] in the Binance app and see if the deposit record appears.
If it shows "Pending" or "Processing", Binance's node is waiting for network synchronization – just wait.
If there is no record at all, the deposit may have encountered a problem.
Visit Binance's "Deposit & Withdrawal Status" page and check whether the Sui network is currently operational. Binance has completed the integration of USDC and FDUSD on the Sui network, and SUI itself also supports Sui network deposits. If the network shows "Suspended" or "Congested", wait for it to resume.
When you're done: You have confirmed that Binance hasn't manually suspended SUI deposits and that the deposit history contains the record.
Prerequisite: You have confirmed in Step 2 that the on-chain transaction was successful.
Common failure reason: During network congestion or brief Sui mainnet instability, Binance may temporarily suspend deposit services and credit the deposit after things return to normal.
4. Use Binance's Self-Service Recovery Channel (if the Deposit Still Hasn't Arrived)
What to do: If all the steps above check out but the deposit hasn't arrived after 1–2 hours, submit a request through Binance's self-service recovery function.
How to do it:
Binance self-service recovery applies when:
The on-chain transaction status must be "Confirmed/Success".
If the transaction doesn't involve Tag/Memo issues (SUI does not require a Memo), you can submit directly.
Steps:
Go to the Binance Help Center and search for "Deposit not credited" or "Self-Service Recovery" to find the application portal.
Paste the TxID; the system will automatically fill in the coin, network, deposit address, etc. (if the information is in the system).
Confirm that the information is correct and submit the application.
Check the processing status in "Application Records".
If the self-service recovery channel cannot process the request, contact Binance live support and provide:
Binance account email
Coin name (SUI)
Deposit amount
TxID
When you're done: The application is successfully submitted and you have a ticket number or application record.
Prerequisite: Step 3 confirms that the on-chain status is Success.
Common failure reason: Entering the TxID incorrectly when submitting. Copy-paste is the safest; do not type it manually.
What to do next:
Now follow the steps in order: Obtain the TxID → Check the status on a Sui block explorer (suiscan.xyz) and confirm Success → Look for the record in your Binance deposit history. If the explorer shows Success but Binance hasn't credited the funds, wait 30 minutes first for the confirmations to accumulate. If it still hasn't arrived after 2 hours, submit a request through the self-service recovery channel. After submission, pay attention to Binance's in-app notification; processing time depends on the manual review queue.
