How to Transfer USDC or USDT from Stables to My Binance Australia Account?

2023-12-05 09:30

If you're looking to move your stablecoins between accounts, follow this step-by-step guide to transfer stablecoins from Stables to Binance Australia on the mobile device.

1. Start on Stables. Log in to your Stables account to bring up your dashboard. Tap [Withdraw].

2. Tap [Change] and select [Add new] - [Wallet address].

3. Log in to your Binance Australia account and tap [Wallet] - [Fiat & Spot].

4. Use the search bar to find either USDC or USDT. Tap [Deposit] next to it.

5. You’ll see the unique deposit address for the crypto. Copy the deposit address.

6. Go back to Stables and paste the copied Binance deposit address into the [Wallet Address] field. Tap [Add].

7. Tap on the stablecoin icon and select either USDC or USDT.

8. Tap on the blockchain you want to send your stablecoins with.

9. Enter the amount of USDC or USDT you want to send to Binance and tap [Continue].

10. Confirm the transfer: For security reasons, you’ll need to confirm the transaction with your biometrics or PIN. Tap [Confirm].

Please note that the transfer time will vary based on the cryptocurrency you're sending and the selected blockchain. Typically, your deposit should appear in your Binance Wallet shortly after the transfer has been confirmed by Stables. For any further assistance, please contact Binance Customer Support.

Disclaimer: This information is of a general nature only and should not be regarded as specific to any particular situation. This should not be taken as financial advice to buy, trade, or sell cryptocurrency or use any specific exchange. This is not intended for use as investment, financial or legal advice as each individual's need will vary.

Binance Australia does not endorse any individual or organisations mentioned in this FAQ and similarly is not affiliated or associated with or in any way officially connected with any individual or organisations mentioned in this FAQ unless otherwise stated. Binance Australia is not liable for any loss caused, whether due to negligence or otherwise arising from the use of, or reliance on, the information provided directly or indirectly by the use of this FAQ.