Bitget deposit network and memo/tag checklist: four checks before you send

Start here: match coin, network, address and memo before you send

When you deposit digital assets to Bitget, the same coin name does not mean the same network, and a correct address does not mean the deposit information is complete. Some assets also require a memo, tag or note. Before you send, confirm that these four items match exactly:

Deposit coin
+ Blockchain network
+ Deposit address
+ Memo / tag / note

Also check the minimum deposit amount, the required network confirmations, whether the deposit address is still valid, whether the sending platform supports the destination network, whether this is an ordinary on-chain transfer, and whether the asset requires a memo, tag or other identifier.

If any one of those is wrong, the asset may fail to credit automatically, stay pending, enter an unassigned wallet, go to the wrong network, need manual handling, or be unrecoverable.

Bitget’s Help Center lists insufficient network confirmations, a wrong or missing memo/tag, an amount below the minimum, an unsupported coin or network, and some unsupported transfer methods as common reasons a deposit does not arrive.

Step 1: Confirm the deposit coin

Before you transfer, confirm that the sending side and Bitget’s deposit page show the same asset.

Sending USDT
→ Bitget deposit coin must also be USDT

Sending XRP
→ Bitget deposit coin must also be XRP

Do not judge the coin from address format alone. Different assets can share a similar address format, run on the same chain, use the same ticker, exist in wrapped or multiple versions, or have different token contracts.

Bitget’s official wrong-deposit notes say that if you send one asset to another coin’s deposit address, the platform may not recognise or credit it automatically.

What should you check before sending?

• Full coin name
• Token ticker
• Blockchain network
• Token contract address
• Asset type shown on the sending platform
• Asset type shown on Bitget’s deposit page

If you cannot confirm that the tokens are the same asset, do not send first and try to fix it later.

Step 2: Confirm the blockchain network matches exactly

The same asset can support more than one deposit network. USDT, for example, may run on Ethereum, Tron, BNB Smart Chain, Arbitrum, Solana or other supported networks. The live list is whatever Bitget’s current deposit page shows.

The network chosen on the sending side must match the network chosen on Bitget’s deposit page exactly.

Bitget deposit page: TRC20
→ Sending platform must also be TRC20

Do not send ERC20 while Bitget’s deposit page is set to TRC20. Even if both sides show USDT, a network mismatch can still stop an automatic credit.

Bitget’s official notes list sending via an unsupported or wrong network as a wrong-deposit case, and remind users that not every wrong-network deposit can be refunded or recovered.

What if network names look similar?

Do not rely on the abbreviation. Check the full network name, the sending-side description, Bitget’s deposit-page description, address format, the fee coin for that network, the token contract, and the minimum deposit. If a network is selectable on the sender but not shown on Bitget’s deposit page, that does not mean Bitget supports it.

Step 3: Copy and check the deposit address

Copy the deposit address directly from Bitget’s current deposit page. Do not use an old screenshot, a chat message, another user’s address, browser autofill, an unverified QR code, a search-engine page, or an address saved long ago without rechecking it.

How to check the address

Before you send, check at least:

First 6 characters
+ Last 6 characters

For a large deposit, check the full address. Also confirm there are no extra spaces, missing characters or clipboard-malware swaps, that the QR code matches the text address, and that the address belongs to the current coin and network.

Why is checking only the ends not enough?

Some attacks generate addresses whose first and last characters look similar. A safer path is: copy from Bitget’s current deposit page, paste into the send page, check the full address again, send a small test, and only then send the rest after the credit arrives.

Step 4: Check whether a memo, tag or note is required

Some assets share a deposit address across users and need a memo, tag or other identifier to allocate funds to a specific account. The live requirement is whatever Bitget’s current deposit page shows.

Bitget’s official notes say a memo or tag is the unique identifier used to distinguish accounts on some deposits. If it is missing or wrong, the asset may not credit automatically and you may need to file a manual recovery request.

How should you fill in a memo or tag?

If Bitget’s deposit page shows both a deposit address and a memo/tag, the sending side must fill in both. Do not send the address alone, invent a memo, use another account’s memo, put the memo in the wrong note field, skip it because the amount is small, or replace it with an exchange UID unless the page explicitly asks for that.

What if the sending platform does not support memo/tag?

Do not send. Use a wallet or platform that supports memo/tag, check whether another supported network exists, read Bitget’s latest deposit notes, and contact both the sending platform and Bitget official support.

Step 5: Check the minimum deposit amount

Different coins and networks can have different minimums. If the amount is below the figure on the page, the asset may not credit automatically. Bitget’s official “deposit not arrived” notes say transfers below the minimum may not be processed, and the minimum should be checked on the current deposit page.

Before you transfer, confirm:

Amount you actually send
- Sending-platform withdrawal fee
- Any network deduction
>= Bitget minimum deposit

Do not look only at the amount typed on the send page. If you type 10 USDT, the sending platform deducts 1 USDT, and 9 USDT goes on-chain, a Bitget minimum above that on-chain amount can still block the credit.

Step 6: Check the network confirmation requirement

An on-chain broadcast does not always appear in Bitget available balance at once. The usual path is broadcast, block inclusion, network confirmations, then a credit after the platform confirmation count is reached.

Bitget’s official notes say the required confirmation count can differ by asset and network. You can check the minimum on the deposit page and use a block explorer with the TxID to see the current confirmation state.

What should you check first if a deposit has not arrived?

1. Whether the sending platform shows the transfer as complete
2. Whether a TxID exists
3. Whether a block explorer can find the transaction
4. Whether the transaction succeeded
5. Whether the current confirmation count meets Bitget’s requirement
6. Whether coin, network, address and memo match
7. Whether the actual amount meets the minimum

If the transaction is still waiting for confirmations on-chain, wait for the network. Do not send the same amount again.

Step 7: Send a small test first

Send a small test first when you are using a new coin, network, wallet, exchange or address, using a memo/tag for the first time, sending a large amount, moving assets after a bridge, or using an unfamiliar sending platform.

Send a small amount
→ Wait for confirmations
→ Check whether Bitget credited it
→ Recheck coin and network
→ Then decide whether to send the rest

The test amount must still be above Bitget’s minimum deposit.

Final checklist before you send

Coin

• Sending coin matches Bitget’s deposit coin exactly
• Token contract confirmed
• Not a same-name asset with a different contract

Network

• Sending network matches Bitget’s deposit network exactly
• Bitget’s current page clearly supports that network
• The network-fee coin is ready
• You are not sending via an unknown or unsupported network

Address

• Address copied from Bitget’s current deposit page
• First and last characters checked
• Full address checked for a large transfer
• QR code matches the text address

Memo / tag

• Confirmed whether the deposit page requires a memo/tag
• If required, the sending side filled it in correctly
• Memo/tag came from the current Bitget deposit page
• You did not use another account’s memo/tag

Amount and confirmations

• On-chain amount is above the minimum
• You know the sending-platform withdrawal fee
• You know the expected confirmation time
• You saved the TxID

How to troubleshoot a deposit that has not arrived

Case 1: The blockchain has not finished confirming

Use the TxID on a block explorer, wait until Bitget’s required confirmation count is reached, and do not send the same amount again.

Case 2: Memo/tag missing or wrong

Prepare your Bitget UID, coin, amount, TxID, deposit address, the correct memo/tag, sending-platform records and screenshots, then file a deposit ticket with Bitget official support.

Bitget’s official notes say memo/tag recovery usually needs manual review, may incur a processing fee, often takes around 10 working days, can take longer in complex cases, and success is not guaranteed.

Case 3: You used the wrong network

Do not keep sending to the same address. Prepare the coin, sending network, intended network, TxID, token contract, deposit address and sending-platform records. Bitget has a process for wrong-coin or wrong-network deposits, but recovery depends on the asset, network, who controls the address, and the on-chain transaction. Not every case can be restored.

Case 4: The amount is below the minimum

Check the current deposit page and official support notes first. Do not assume extra small sends will be merged automatically unless an official page says so.

Case 5: You used an unsupported transfer method

Some deposits come from smart-contract batch transfers, internal contract distributions, bridge contracts, special token transfers or unsupported network methods. Bitget’s official “deposit not arrived” notes say some smart-contract deposits or unsupported methods may not be processed automatically and need support to confirm.

Common misconceptions

Misconception 1: Same coin means any network is fine

The same coin can exist on more than one chain. The network must match.

Misconception 2: If the address looks the same, it will credit

A similar address format does not prove the coin and network match.

Misconception 3: Memo/tag is optional

If the deposit page requires a memo/tag, missing it can stop an automatic credit.

Misconception 4: The minimum is the amount you type on the send page

Check the on-chain amount after the withdrawal fee.

Misconception 5: If the sending platform shows complete, Bitget should credit at once

You still need on-chain confirmations and the platform credit threshold.

Misconception 6: A wrong-network deposit can always be recovered

Recovery depends on the network and the transaction. It is not guaranteed.

Summary

Before a Bitget deposit, the most important match is:

Same coin
Same network
Correct address
Complete memo/tag
Amount above the minimum
Confirmations meet the credit threshold

On a first use of a new coin, network or address, send a small test that is still above the minimum. Once an asset is sent on-chain, the platform usually cannot reverse the transaction. Completing the checks before you send is more effective than relying on manual recovery.

Notes

This article is based on Bitget’s publicly available official materials. Deposit networks, minimums, confirmation counts, memo/tag requirements, recovery processes and processing fees can change with coin, network, account and platform rules. Rely on Bitget’s current deposit page and latest official notes.