Skip to content
Financial Context Wiki

Centralized Exchange (CEX): Trading, Custody, and Withdrawal Risk

Learn how a centralized crypto exchange holds customer assets, records balances, matches orders, processes withdrawals, and concentrates custody and platform risk.

Updated

For educational purposes only; not investment, legal, tax, or custody advice. Crypto assets and claims on exchanges can lose value or become inaccessible.

Direct answer

A centralized exchange (CEX) is an operator-run service that maintains customer accounts, takes custody of deposited assets, and matches trades in an internal system. A typical CEX lets users deposit fiat money or crypto assets, place orders against an order book, and request withdrawals. The operator controls admission, listings, account authentication, matching rules, custody wallets, and whether a withdrawal request is accepted.

The balance shown after a deposit is normally an entry in the exchange’s internal ledger. It represents a claim under the account agreement, not a user-controlled on-chain balance. Trades between customers can therefore settle by changing database entries without broadcasting a blockchain transaction. On-chain activity is usually required when assets enter or leave the exchange, not for every matched trade.

This model can provide fast execution, familiar account recovery, fiat access, customer support, and advanced order types. It also concentrates control: account compromise, inaccurate records, asset commingling, cyberattack, operational failure, legal restraint, or insolvency can prevent a customer from trading or withdrawing even while the interface still displays a balance.

How it works

  1. Account and deposit: The user opens an account and completes the authentication or identity checks required by the operator. Before depositing, verify the exact asset, network, token contract, address, memo or tag, minimum amount, and confirmation policy. A deposit address may be unique to the account but still be swept into an omnibus wallet controlled by the exchange.

  2. Ledger credit: After the exchange observes enough confirmations or finality, it credits its internal ledger. The credited amount can differ from the sent amount because of network fees, deposit rules, or token behavior. Keep the transaction identifier and reconcile it to the account statement.

  3. Order entry and matching: Limit orders rest in an off-chain order book. A matching engine applies the venue’s price, time, and order-type rules. A market order consumes available orders at successive prices, so its volume-weighted average execution price can differ from the best quote. Internal matching is fast and normally charges no blockchain gas per fill, but trading fees, spreads, slippage, and funding or borrowing costs may still apply.

  4. Internal settlement: A fill changes the buyer’s and seller’s ledger balances. It does not prove that the exchange holds sufficient, correctly segregated, unencumbered assets for all customers. The public blockchain generally cannot reveal the completeness of the exchange’s customer liabilities or internal transactions.

  5. Withdrawal: The customer submits an instruction; the exchange checks permissions, available balance, limits, compliance and risk rules, then signs or batches an on-chain transfer. An “approved” status is not receipt. Verify the transaction identifier, network, asset contract, destination, amount, confirmations or finality, and spendable balance in the destination wallet.

Worked example

Suppose the sell side of an order book offers 20 ETH at 2,000 USDT, 30 ETH at 2,005 USDT, and 50 ETH at 2,015 USDT. A market order to buy 60 ETH fills all 20 at the first level, all 30 at the second, and 10 at the third:

(20 x 2,000 + 30 x 2,005 + 10 x 2,015) / 60 = 2,004.17 USDT per ETH

The best displayed ask was 2,000 USDT, but the average execution price is about 2,004.17 USDT. At a 0.10% trading fee, the fee is about 120.25 USDT, before any withdrawal fee. The trade changes internal balances; it does not send 60 ETH to the buyer’s personal wallet.

If the user later requests a 10 ETH withdrawal and the exchange charges 0.005 ETH, the internal balance decreases by 10.005 ETH. The user should verify that the external wallet receives 10 ETH on the intended network. A platform-generated identifier, email confirmation, or debited screen balance is not a substitute for checking the actual transaction and final receipt.

Risks and controls

  • Identify the responsible entity. Confirm the contracting company, jurisdiction, service permissions, account terms, custody arrangement, and rules for segregation, lending, staking, setoff, insurance, forks, insolvency, and withdrawals. A brand may use several legal entities with different protections.
  • Evaluate custody and financial evidence. Look for coverage of customer liabilities, wallet control, asset ownership, segregation, encumbrances, reconciliation, governance, and independent assurance. A proof-of-reserves snapshot or Merkle inclusion proof is not a financial-statement audit and does not by itself establish complete liabilities, unborrowed assets, effective controls, or continuing solvency.
  • Secure the account. Use a unique password and phishing-resistant authentication where available; protect recovery channels; enable withdrawal allowlists and change delays; restrict API keys to the minimum permissions and trusted IP addresses; and review login, order, and withdrawal alerts. A trading tool usually does not need withdrawal permission.
  • Control execution cost. Inspect order-book depth rather than only the last price. Compare the spread, expected slippage, maker or taker fee, deposit and withdrawal fees, network cost, and currency-conversion cost. Test unfamiliar order types with small amounts.
  • Limit custody exposure. Keep only the amount and duration needed for the service’s purpose, subject to the operational risks of self-custody. Periodically test a small withdrawal and preserve statements, transaction records, support messages, and tax records. Splitting assets among exchanges reduces one concentration but may leave common stablecoin, bank, cloud, custodian, or jurisdiction risks.
  • Prepare for disruption. If an unknown login, order, API action, or withdrawal appears, lock the account if possible, revoke keys and sessions, contact support through a verified channel, and preserve evidence. If withdrawals are delayed, stop adding exposure and distinguish an account review from an asset-wide or platform-wide suspension. Never give a password, seed phrase, or one-time code to purported support staff.

Delisting notices often specify separate deadlines for deposits, trading, and withdrawals. Record each deadline and confirm another supported venue or self-custody path before acting. A delisted market does not make the token invalid, but liquidity and wallet support may deteriorate quickly.

Common misconceptions

Myth 1: A displayed balance is the same as on-chain ownership

It is normally an internal claim against the exchange. Direct on-chain control begins only after a valid withdrawal reaches an address whose keys the user controls.

Myth 2: Proof of reserves proves solvency

A snapshot can support limited claims about selected assets at one time. It may omit liabilities, encumbrances, ownership, controls, and events before or after the snapshot.

Myth 3: A large or regulated exchange cannot freeze withdrawals

Size and authorization may improve some controls, but technical incidents, compliance reviews, legal orders, liquidity stress, and insolvency can still delay or block access. Verify the exact entity and regulatory scope.

Myth 4: A CEX is always cheaper than a DEX

Off-chain matching may avoid gas for each fill, but the total comparison must include spreads, slippage, trading and withdrawal fees, network costs, and the risks of custody or smart contracts.

Sources

Navigation

Search the wiki...