Deposits and Withdrawals | Market Structure & Exchanges

MARKET STRUCTURE & EXCHANGES · CENTRALISED EXCHANGES (CEX)

Deposits and withdrawals connect a centralised exchange's internal account ledger with public blockchain settlement. The asset, network, address and any memo/tag must all match the venue's supported route.

Risk first. Wrong-network transfers, missing tags, unsupported token contracts and copied addresses can cause long delays or permanent loss of access. Exchange recovery should never be assumed.

Last reviewed: 21 August 2026 · Educational content only

Deposits
Withdrawals
Network safety
Worked example
Mistakes
Checkpoint
FAQ

How a deposit works

The exchange presents a supported asset/network combination and a receiving address, sometimes plus a memo/tag/payment ID.
The user broadcasts a blockchain transaction from the sending wallet or venue.
The exchange monitors the destination address and waits for its required confirmations/finality threshold.
After checks, the exchange credits the customer's internal balance.

The blockchain transaction and the exchange credit are separate events. A transaction can be confirmed on-chain while the internal account is still waiting for processing or identity/compliance review.

Confirmations: venues choose thresholds according to chain finality, reorganisation risk, asset value and operating policy. More confirmations usually increase settlement confidence but also increase credit time.

How a withdrawal works

The user submits asset, network, address and amount to the exchange.
The exchange debits or reserves the internal balance.
Security, compliance, allowlist and risk controls are applied.
The custody system creates or batches a blockchain transaction.
The transaction is broadcast; the destination then waits for its own confirmation policy.

Stage	Primary system	Possible delay
Trade fill	Exchange ledger	Milliseconds/seconds
Withdrawal review	Exchange custody/risk	Policy dependent
Broadcast	Blockchain	Network/fee dependent
Destination credit	Receiving wallet/venue	Confirmations + processing

Network and address safety

Choose the receiving network from the destination's current deposit/receive screen first.
Confirm the sender supports that exact network and asset/token contract.
Do not rely on address format alone. Several EVM networks use identical-looking 0x addresses.
Include memo/tag/payment ID where required for shared-address systems.
Check minimum deposit/withdrawal and fee rules before sending.
For material or unfamiliar transfers, use a small test when fees/minimums make it practical.

Withdrawal fee

A venue charge; it may differ from the actual blockchain network fee.

Network fee

The cost of blockchain inclusion/settlement; the venue may batch or subsidise it.

Worked example

An exchange supports USDC on Ethereum and Arbitrum. Your destination's receive screen explicitly says USDC — Ethereum and shows an address beginning 0x....

Your sending exchange also offers Arbitrum withdrawals with the same-looking destination address format. Choosing Arbitrum because it is cheaper does not validate the transfer. The receiving venue must support the exact asset/network route you selected.

Suppose you correctly send a £20 test deposit over Ethereum and it credits. Before sending £20,000, re-open the current deposit screen and compare network and address again. A successful earlier test does not protect against later clipboard replacement, changed deposit instructions or selecting a different network.

Decision discipline: destination first → asset → network → address → memo/tag → sender network match → test when justified → verify credit → re-check before main transfer.

Common mistakes and misunderstandings

Choosing the cheapest network without confirming destination support.
Copying a previous transaction-history address instead of the live receive screen.
Ignoring memo/tag requirements.
Assuming the same token ticker on two chains represents an interchangeable route.
Sending the full amount before testing a new or high-value workflow.

Recovery uncertainty: a wrong-network deposit can sometimes be recoverable if the destination controls the corresponding keys and supports a recovery process—but technical possibility is not a promise of service.

Knowledge checkpoint

Why can two EVM networks use the same-looking address while still requiring explicit network matching?
What does a deposit confirmation threshold protect against?
Why can a withdrawal fee differ from the underlying network fee?
Which four fields should you verify before sending to a centralised exchange?

FAQ

❓ Why is my deposit pending?

It may be waiting for confirmations, exchange processing or compliance review.

❓ Can a wrong-network deposit be recovered?

Sometimes, but recovery is venue-specific and should never be assumed.

❓ Why are withdrawals slower than trades?

Trades are internal ledger events; withdrawals add custody and blockchain steps.

❓ Can deposit addresses change?

Yes. Always use the current destination instructions.

Summary

Deposits move blockchain assets into an exchange's internal account system.
Withdrawals reverse that path through custody and blockchain controls.
Asset, network, address and memo/tag must align.
Test transfers and independent re-verification reduce operational error.

This building block is educational and not a trade recommendation.