Separate the app display from the actual order state. This guide walks through orderbook state, collateral checks, settlement display, and the first evidence to inspect before opening a support ticket.
Flow layers
4
V2 symptoms
4
Check steps
5
FAQ items
6
The key takeaway from this page
A changed button, frozen quote, or odd balance label is not automatically a completed trade.
Separate the app display from the actual order state. A changed button, frozen quote, or confusing balance label is not the same thing as a completed trade.
Do not assume funds are missing, and do not use third-party recovery tools. Check open orders, trade history, balance/collateral display, and market depth first.
Most panic screens come from collapsing these layers into one event.
The app can show a submitted or changing state before the final order state is clear.
The order still has to meet available liquidity, price limits, and matching-engine rules.
A balance, collateral migration, or available-cash display can differ from the quote screen.
The final market, claim, or cash-available display can lag the user interface during busy or migration windows.
Reserved collateral is an order-state concept, not proof that money vanished.
No. A resting buy order ties up available collateral until it fills, partially fills, expires, or is cancelled. Your visible balance is not always the same as immediately available collateral for a new order.
Keep these four concepts separate:
Polymarket documents orders as limit orders, with GTC/GTD orders resting until they fill, expire, or are cancelled. Orders are monitored for balances and allowances, and the maximum order size is the underlying balance minus the still-open remainder of existing orders.
Reserved collateral is not margin or leverage, and it is not proof that funds vanished, are missing, or were stolen.
Match the screen copy first, then inspect the first layer before escalating.
A displayed price can move when the available size at that price is thin. Separate the quote you saw from the final matched order state.
Treat this as an app-display/account-state symptom unless official docs say it is a V2 product change.
Separate collateral migration/balance display from filled order state and settlement state.
This may belong to the troubleshooting hub settlement-balance section rather than the order-flow page.
Follow a repeatable sequence before treating the symptom as a failed trade.
Open orders
A failed-looking click may have left a resting order rather than a completed trade.
Trade history
A completed fill should appear in history; a button flash alone is not enough.
Wallet / balance / collateral
Available balance, collateral labels, and cash display can be separate from order state.
Market depth
Thin size at the displayed price can make the final matched price differ from the quote.
Refresh web vs app
A stale app surface can make the same account look different from desktop web.
Avoid mixing order-state confusion with other troubleshooting categories.
Resolved-market payout or cash-available backlog after the outcome is known.
Mobile display lag when desktop web shows a clearer state.
Backtest/live slippage, queue, and depth problems for automated strategies.
How thin books, visible size, and exits affect actual trade prices.
Treat community panic as a symptom until official product surfaces confirm the state.
This page treats community panic as a symptom, not proof. Specific product behavior should come from official Polymarket docs, help pages, or account surfaces the user can check directly.
If an official page does not support a specific claim, the copy stays generic: app-display state, orderbook state, collateral/balance state, or settlement/display state.
6 common questions answered
Continue exploring
