Scoutinternal

Withdrawing Crypto (USDT, USDC, BTC, ETH, etc.) from BitGo to Binance or Other Exchanges

Withdrawing Crypto (USDT, USDC, BTC, ETH, etc.) from BitGo to Binance or Other Exchanges

Problem

FTX creditors and other BitGo users frequently attempt to withdraw cryptocurrency—most commonly USDT, USDC, BTC, ETH, SOL, and DOGE—from their BitGo Go Account wallet to an external exchange such as Binance. Common failures include: incorrect wallet password errors, spendable balance showing as 0 after trading, the "keychain does not have property encryptedPrv" error, inability to select a blockchain network, address format incompatibility (especially BCH), and confusion around the whitelist and video ID verification process. These issues predominantly affect FTX settlement recipients who are unfamiliar with the BitGo platform.

Diagnostics

  • Confirm the customer's account type: Check whether this is an FTX creditor Go Account via the admin tool. Most tickets in this cluster are FTX settlement recipients on BitGo Trust.
  • Check spendable balance vs. total balance: In the admin panel, verify whether the customer's traded funds have settled. Funds are not available for withdrawal until after daily settlement (begins at noon ET every weekday, excluding US public holidays, and can last up to 4 hours).
  • Check withdrawal/transfer history: Look in the admin tool under the account's transfers tab to see if any withdrawals have already completed successfully or are pending verification.
  • Identify the error message or error ID: Ask the customer for the exact error text or error ID. Key distinguishing errors:
    • "wallet password is incorrect" or similar decryption failure → incorrect wallet password
    • "keychain does not have property encryptedPrv" → wallet password needs to be set/reset
    • "insufficient balance" or "Enter an amount that doesn't exceed the maximum spendable balance" with a non-zero total balance → funds not yet settled, or gas/fee issue
    • Spendable balance shows 0 → settlement not yet complete
    • "invalid address" from Binance (BCH) → address format mismatch (legacy vs. CashAddr)
  • Check whitelist status: Verify whether the customer has whitelisted the destination address in the Whitelist tab of their Go Account.
  • Check if video ID verification is pending: First-time withdrawals to a new whitelisted address may require a liveness check or scheduled video ID call. Look for pending verification status on the withdrawal.
  • Confirm the customer is using the correct UI: Some withdrawal and settings features require switching to "classic view" in the BitGo web app.
  • Confirm the coin and network: For FTX creditor accounts, stablecoins (USDT, USDC) are supported only on the ERC-20 network. The customer must use a matching ERC-20 deposit address on Binance.

Resolution

Scenario: binance-usdt-withdraw-transfer#incorrect-wallet-password

Trigger: The customer receives an error indicating the wallet password used during the withdrawal request is incorrect.

Signals: wallet password incorrect, decryption error, wrong password, unable to withdraw, ErrorID

Steps:

  1. Inform the customer that the wallet password is different from their login password.
  2. Instruct the customer to switch to the classic UI:
    • Click on the profile icon in the top right corner.
    • Click on "Switch to classic view".
  3. Navigate to the wallet password reset:
    • Go to Trade > Wallet Details > Settings > Forgot Wallet Password.
  4. The customer enters their current login password, then sets and confirms a new wallet password.
  5. Advise the customer to manually type the new password rather than relying on a password manager, as password managers may save it incorrectly or associate it with a different account.
  6. Recommend using Google Chrome on a desktop/laptop for the best experience.
  7. Once the wallet password is reset, the customer should retry the withdrawal using the new wallet password.

Notes: This is the most common root cause across tickets. The wallet password is set separately from the account login password. If the customer changed their login password, the wallet password does not change automatically. The creator of the wallet must use the wallet passphrase they originally set; any other user uses their BitGo platform password.

"The error message indicates that the wallet password used during the withdrawal request is incorrect. Please try again and make sure to use the correct wallet password. If you happened to forgot the wallet password you may goto Trade > Wallet Details > Settings > Forgot Wallet Password" (ticket #204158)

"Be sure you are manually typing the new password. It is possible that password managers may not save the new password, may save it incorrectly, or may incorrectly associate it with a different account." (ticket #211295)

"Please also note that your login password can be different from your wallet password and if you had changed your login password, your wallet passwords will not change." (ticket #244201)

Scenario: binance-usdt-withdraw-transfer#keychain-encryptedprv-error

Trigger: The customer sees the error "keychain does not have property encryptedPrv" when attempting to withdraw.

Signals: keychain does not have property encryptedPrv, encryptedPrv, wallet password reset, trading wallet

Steps:

  1. Explain that this error means the trading wallet password needs to be set or reset.
  2. Instruct the customer to switch to Classic View if needed (profile icon > "Switch to classic view").
  3. Guide them to reset the trading wallet password:
    • Log in to the account.
    • Navigate to the Trading Wallet.
    • Go to Settings.
    • Select Update Wallet Password.
    • Enter the current login password.
    • Enter and confirm a new wallet password.
    • Complete the upgrade.
  4. After resetting, the customer should retry the withdrawal using the new wallet password.
  5. If issues persist, suggest trying in an incognito or private browser window and manually entering the new wallet password.

Notes: This error is distinct from a simple incorrect password. It indicates the wallet keychain was never encrypted with a user-supplied passphrase, commonly seen with FTX creditor Go Accounts that were migrated.

"if you're encountering the error 'keychain does not have property encryptedPrv', it may be necessary to reset your trading wallet password." (ticket #206982)

"If you are running into 'Keychain does not have property encryptedPrv' error, you may need to reset the trading wallet password." (ticket #242847)

Scenario: binance-usdt-withdraw-transfer#spendable-balance-zero

Trigger: The customer's spendable balance shows 0 even though total balance reflects funds, typically right after trading USD for crypto.

Signals: spendable balance 0, zero balance, can't withdraw after trading, settlement, funds not available

Steps:

  1. Explain that funds are not immediately available for withdrawal after trading due to settlement processing time.
  2. Daily settlement begins at noon ET every weekday (excluding US public holidays) and can last up to 4 hours.
  3. Ask the customer to wait at least 24–48 hours after their trade, then try again.
  4. If the issue persists after settlement, ask the customer to provide the wallet ID and error details in plaintext for further investigation.

Notes: This is very common among FTX creditors who convert USD to crypto and immediately attempt withdrawal. The spendable balance will update once settlement completes.

"Please note that funds are not immediately available for withdrawal after trading due to settlement processing time. This ensures that all transactions are properly recorded and processed. As a result, your spendable balance may show as 0 until the funds are fully settled." (ticket #215731)

"Please note that traded funds will only be available for withdrawal after daily settlement which begins at noon ET every weekday (excluding US public holiday) and can last for up to 4 hours." (ticket #231768)

Scenario: binance-usdt-withdraw-transfer#whitelist-and-withdrawal-steps

Trigger: The customer does not know how to withdraw crypto from BitGo to Binance and needs step-by-step guidance.

Signals: how to withdraw, transfer to Binance, withdrawal steps, whitelist address, send USDT, send BTC, procedure

Steps:

  1. From the Go Account wallet, select Withdraw next to the asset the customer wishes to withdraw.
  2. Before withdrawing, the destination address must be whitelisted:
    • Navigate to the Go Account Wallet.
    • Click on the Whitelist tab.
    • Click to add the destination address from Binance (or other exchange).
  3. If the destination address requires a destination tag (e.g., XRP), include it when adding to the whitelist in the format: address?dt=tag.
  4. For the first withdrawal to a new address, the customer will be prompted to complete a liveness check (self-serve video verification) or schedule a video ID call with BitGo.
  5. Once the address is verified, complete the withdrawal by entering the amount and wallet password.
  6. For stablecoins (USDT, USDC), FTX creditor accounts support only the ERC-20 network. The customer must use a matching ERC-20 deposit address on Binance.
  7. Supported withdrawal assets include BTC, ETH, XRP, SOL, and stablecoins.
  8. Fiat USD can only be withdrawn to a bank account, not to Binance.

Notes: Customers often confuse whitelisting with verification. Whitelisting adds the address; verification (liveness check or video call) happens after the first withdrawal is initiated to that address. Fiat USD cannot be sent to an exchange—it must go to a bank account.

"Please follow the steps below to whitelist an address:- —> Navigate to your Go Account Wallet —> Click on whitelist tab —> Click on whitelist and add the address" (ticket #211881)

"The transactions of the stablecoins USDT, USDC works only on ERC-20 Blockchain Network." (ticket #249169)

"FYI, fiat USD can only be withdrawn to bank account." (ticket #211881)

Scenario: binance-usdt-withdraw-transfer#bch-address-format

Trigger: Binance rejects a BCH address generated by BitGo as invalid.

Signals: BCH, invalid address, Binance, Bitcoin Cash, base58, CashAddr, legacy address

Steps:

  1. Explain that BitGo generates BCH addresses in legacy (base58) format, which Binance may not accept.
  2. Direct the customer to convert the address to CashAddr format using the tool at: https://cashaddr.bitcoincash.org/
  3. Advise the customer to send a small test amount to the converted address first to confirm it works before sending the full amount.

Notes: This applies specifically to BCH. Other coins (BTC, ETH, etc.) do not typically have this address format issue with Binance.

"This is likely due to Binance not accepting BCH legacy address which BitGo is using. You can use this tool to convert the address to its CashAddr format - https://cashaddr.bitcoincash.org/" (ticket #217610)

Scenario: binance-usdt-withdraw-transfer#classic-view-required

Trigger: The customer cannot find withdrawal settings, wallet password reset options, or encounters UI limitations in the new interface.

Signals: classic view, old UI, switch to classic view, can't find settings, Forgot Wallet Password not visible

Steps:

  1. Instruct the customer to switch to the classic (old) UI:
    • Click on the profile icon in the top right corner.
    • Click on "Switch to classic view".
  2. Once in classic view, the customer can access wallet settings, password reset, and withdrawal options that may not be fully available in the new UI.
  3. The path for wallet password reset in classic view is: Trade > Wallet Details > Settings > Forgot Wallet Password.

Notes: Multiple tickets confirm that certain wallet management functions—particularly the Forgot Wallet Password option—require switching to classic view. This is a known UI limitation.

"Please be informed that access to the specified options requires the switch to the old UI. We've attached screenshots to guide you through the process. Step 1 :- Click on the profile icon in the top right corner Step 2:- Click on Switch to classic view" (ticket #204158)

Scenario: binance-usdt-withdraw-transfer#video-id-verification

Trigger: The customer's withdrawal is pending and requires video identity verification before it can be processed.

Signals: video verification, liveness check, video ID, first withdrawal, pending verification, schedule video call

Steps:

  1. Explain that the first withdrawal to a new whitelisted address requires identity verification.
  2. After initiating a withdrawal, the customer will see options to:
    • Perform a self-liveness check (self-serve), or
    • Schedule a video ID call with BitGo.
  3. If the customer needs to schedule a video call, they can use the Calendly link: https://calendly.com/bitgo-client-delivery/videoid
  4. The customer should have a government-issued photo ID ready for the call.
  5. Once verification is complete, the withdrawal will be processed.

Notes: The verification options only appear when there is a pending withdrawal. If no withdrawal is pending, the customer will not see the liveness check or scheduling options. Ensure the customer initiates the withdrawal first before attempting verification.

"You should be prompted to do a liveness check for sending to an address the first time. If the liveness check failed for you, you can then choose to Schedule a video ID instead." (ticket #221675)

Related