Polymarket Troubleshooting Hub
Every common Polymarket panic — from a first order that won't fill to a withdrawal that's pending for days — traced back to the actual mechanic causing it, with the fix in plain English and what to send support if the fix doesn't work.
Pick the version of the problem you actually have
Most Polymarket panic starts when users collapse different failure modes into one story. Start with the symptom that matches your screen — not the one that feels scariest. Every card jumps to the full section below.
Status check first: before assuming a position or fund issue is permanent, check Polymarket's official status page for active incidents or maintenance windows. If the status page is clear, keep troubleshooting the account, wallet, and market state separately.
My first order failed
Deposited, but the first trade shows an execution error or 'no executions found.' Usually a market-state or order-price issue, not lost funds.
Jump to fixApp & website show different balances
Different numbers on each surface, or every order is rejected for 'insufficient balance' even though the deposit confirmed. Seven-step fix below.
Jump to fixThe order book wall vanished
You saw a wall of resting size, tapped to take it, and it's gone. Maker cancelled, UI snapshot was stale, or a faster taker hit it first.
Jump to fixCan't cash out a winning position
Position moved your way but the sell won't fill at the screen price. Thin book, partial fills, and exit-liquidity mechanics.
Jump to fixClaim keeps failing + kicks me out
'Automatic message failed' on a resolved market, and the app logs you out mid-claim. Two separate problems happening at once.
Jump to fixWithdrawal pending / delayed
A small test withdrawal arrived fast but the real one is still pending. Different rail, extra review, or third-party processor delay.
Jump to fixWithdrawal 'declined' + balance reads zero
Different from a delayed withdrawal: status flipped to 'declined' or 'failed' and the in-app balance dropped to zero before any payout arrived. Almost always a display-vs-on-chain state mismatch — the funds are usually still on-chain. Action map below.
Jump to fixPosition disappeared before resolution
A position was visible before final resolution, then changed or disappeared on one surface. Separate app display, position inventory, wallet state, and official market status before assuming funds are missing.
Jump to fixDeposit stuck / recovery tool broken
Funds sent to Polymarket never arrived, or recovery.polymarket.com itself is broken. Documented recovery paths and escalation ladder.
Jump to fixWhy did my first Polymarket order fail?
Deposited, but the first trade shows an execution error? A first-order failure usually points to something observable: the market was thinner than it looked, your order could not match available liquidity, the market state changed, or the same order needs a calmer second look before you assume anything is broken.
Quick answer: a first-order failure usually means the market was thinner than it looked, your order could not match liquidity, or the same order needs a calmer second look. It is rarely a sign your funds are gone.
Did the order look filled, then freeze or fail?
Use the V2 order-flow explainer to separate app display from open orders, trade history, collateral state, and market depth.
Why a Polymarket order looked filled but failedQuick amount buttons are not practice mode
Polymarket quick amount buttons — including Polymarket $5 / $10 tabs or other preset amounts inside a trade flow — should be treated as preparing a real order, not browsing. Fast crypto markets can move or resolve while you are still learning the screen.
Read the market question and resolution rule
Check whether you are buying YES or NO
Check whether the order is marketable now
Check the clock — 5-minute markets are not tutorials
After a surprise fill, slow down
- Do not chase with a second market order.
- Do not assume a quick loss means funds vanished.
- Do not use screenshots as proof of the executable price.
Match your symptom to what's likely happening
No executions found
Likely explanation
Your order likely did not find a match, the market state changed, or the screen looked more tradable than it actually was at that moment.
Order pending
Likely explanation
The order exists, but it may still be waiting for a counterparty rather than being broken.
Rejected or failed
Likely explanation
The platform may have blocked the order because of account readiness, market conditions, or order details that do not fit the current market state.
Balance looks fine, but trade will not go through
Likely explanation
A visible balance does not always mean every trading prerequisite is fully ready yet, especially right after funding.
Four common causes
The market looks open, but it is not truly executable
A market can look alive on screen while being paused, thin, or temporarily not matchable in the way you expect. Open-looking is not the same thing as immediately fillable.
Your price or order type cannot find a match
If your order is priced away from available liquidity, it may sit there or fail to execute. That usually means no counterparty met your terms, not that your money vanished.
Liquidity is thinner than the interface made you expect
The book may not have enough size at your desired price. A market can show activity without having enough real depth to fill a new order cleanly.
There is a temporary platform or routing issue
Sometimes the problem is broader than your order. Repeated failures across markets or visible status problems are the clue that this may be a platform issue instead of user error.
Four-step retry playbook
Confirm the market is active
Check whether the market has visible quotes, recent activity, or any obvious sign that trading is actually live right now.
Confirm the order type and price
Look at whether your order could realistically match what is available. If your price is too passive or too far away, it may never execute.
Confirm account and funding state
Make sure the account screen, wallet connection, and order details all look normal before retrying the same trade.
Retry once, then stop guessing
After one clean retry, look for a pattern. If the same issue repeats across markets or you see visible status problems, gather evidence instead of hammering the button.
Polymarket balance not matching between app and website
If your Polymarket balance reads different numbers on the app vs the website, or every order is rejected for insufficient balance even though a deposit shows as confirmed — the cause is almost always one of seven things. Work through them in order before filing a support ticket.
The 30-second answer
If your Polymarket balance looks different on the app than it does on the website — or if every order is rejected for insufficient balance even though a deposit shows as confirmed — the mismatch is almost always one of seven things: a different login email on each surface, a deposit that has not yet confirmed on-chain, funds sitting in the trading vs funding wallet, USDC.e that has not been bridged to the collateral token Polymarket uses for orders, a pending limit order that is tying up the balance, a stale app cache, or a support ticket that needs to be filed with the right evidence. None of these require you to share a seed phrase or use a third-party "balance fix" tool.
The seven checks, in order
Work through each step before moving to the next. Most mismatches are resolved by Step 5 without any support contact.
Are you signed into the same email on both surfaces?
Polymarket accounts are keyed to the email you signed up with. If the app and the website are signed into different email addresses, each surface shows that account's balance — not the one you funded. Sign out of both, then sign back in using the exact same email on each surface.
Has the deposit confirmed on Polygon?
A deposit shows in Polymarket only after it's confirmed on the Polygon block explorer. If it's still pending in your wallet's activity tab, it won't appear as available collateral yet. Paste your tx hash into polygonscan.com and confirm at least one block confirmation.
Is it in the trading wallet or the funding wallet?
Polymarket separates the funding wallet (where deposits land) from the trading wallet (what the order book reads). If funds sit in the funding wallet only, every order will reject for 'insufficient balance' even though the total looks right. Move the balance to the trading side from inside the Polymarket app, not by sending another transaction.
Do you have USDC.e waiting to be bridged?
Polymarket uses a specific collateral token. If you sent bridged USDC.e or a non-canonical USDC variant to the address, it may show in your wallet but be invisible to the order book until it's converted. The in-app bridge or swap is the safe path — never hand a seed phrase to a 'balance fix' tool.
Is an open limit order tying up the collateral?
Resting buy orders reserve their full notional collateral until they fill or cancel. If you see balance "missing" but have open orders, the collateral is locked against those orders, not lost. Cancel any orders you don't actually want before ticketing support. Reserved-collateral explainer.
Hard-refresh the app and the web client
After making any of the above changes, force a hard refresh on both surfaces. The web client can cache a stale balance snapshot for minutes after the on-chain state has updated. Close and reopen the app on mobile, hard-reload on desktop.
File support with a clean evidence pack
If steps 1–6 don't resolve it, file with polymarket.com/support — include tx hash, public wallet address, screenshots of both surfaces showing the mismatch, your registered email, and timestamps. Never include a seed phrase, recovery phrase, or private key.
What NOT to do
Scammers impersonate Polymarket support and target balance-issue posts on social platforms. These rules are not optional.
- Never share a seed phrase, recovery phrase, or private key with anyone — including anyone who claims to be Polymarket support.
- Never use a third-party 'balance fix' tool, browser extension, or Telegram/Discord bot that asks for wallet access.
- Never accept a DM from an account claiming to be Polymarket support. Real support responds inside the ticket thread on polymarket.com/support — never via DM first.
- Don't deposit again to 'test' before the first deposit has finished confirming. Duplicate deposits make support tickets slower to resolve, not faster.
- Don't create a second wallet to 'rescue' funds from the first. Polymarket's account-recovery paths are documented and do not require creating new wallets.
The order book wall vanished when I tapped. What happened?
You saw a wall of resting size on the book. You tapped to take it. It is gone. Here is the thirty-second answer, the actual mechanics of a central limit order book, and the decision tree for what to do before you fire your next order.
The thirty-second answer
Three things to accept before you tap again.
What a book wall actually is
A Polymarket market runs on a central limit order book (CLOB). The book is a stack of resting buy and sell orders at different prices. A "wall" is just a single resting order whose size is noticeably larger than the orders around it. It shows on the book until it fills, is cancelled, or the owner changes its price.
ASK 74¢ 200 ASK 73¢ 800 ASK 72¢ 10,000 ← the "wall" ───────────────── BID 71¢ 1,200 BID 70¢ 500
In the snapshot above, someone has posted a resting sell order for 10,000 contracts at 72¢. Until another trader takes it or the maker cancels, it shows on the book. That is the whole mechanic. The order is resting. It is not a promise. It is not a commitment.
The three real reasons a wall disappears the moment you click
The maker cancelled before your order routed
Resting orders on an order book can be cancelled any time by the trader who posted them, including a fraction of a second before your own order arrives to cross them. The wall was real. Then the owner pulled it. Your order arrived at an empty level. This is the single most common explanation, and it is baked into how every central limit order book works.
Latency meant your UI snapshot was stale
The book you see in the app is a snapshot that updates on a short delay. Between the last refresh and your click, the wall may have already been filled, cancelled, or edited. The tap felt instant to you. On the book it landed seconds late. What looks like a vanishing wall is sometimes just a stale render.
A faster taker hit the wall before you did
Another trader, often a market-making bot with a tighter connection, saw the same wall and took it first. Your order routed into the space that wall used to occupy, not the wall itself. On a busy book, this can happen in sub-second bursts that feel invisible to a retail app.
Five-step playbook when a wall vanishes
Do not chase with a market order
If the wall you wanted is already gone, a market order behind it will sweep whatever prints are sitting on the next levels, which are usually worse. Cancel the instinct to retry immediately.
Inspect the top five levels, not just the visible wall
Open the depth view. The wall you remember was one level. The real question is how much size rests across the top five bids or asks. That is your actual fillable liquidity.
Place a limit at the level you would actually pay to exit
Write down the worst price you are willing to trade at before you look at the book again. Put a limit there. If the book does not come to you, you did not miss anything — you avoided paying for something that was never really yours.
Size down to fit the levels immediately inside your limit
If the next three levels hold only 200 contracts combined, do not fire an order for 500. Split the clip, start with the smaller size, and let the book tell you whether there is anything real behind the displayed prints.
If the wall was your only reason to trade, cancel and step away
A vanished wall is not a trading signal. If the only thesis was that someone big was resting offers you could take, and that person just left, the opportunity left with them. Walk away from the screen for ten minutes before you decide anything else.
Why can't I cash out my Polymarket win?
Being right on direction is not the same thing as getting a clean exit. On an order book, you still need real buyers at a real price for your real size.
Quick answer
- • Polymarket is an order book, not a guaranteed cash-out button.
- • The displayed price is not the same thing as executable size.
- • If there are not enough buyers at your price, you may need to lower price, sell smaller, wait, or hold to resolution.
What's actually happening
You were right on direction
Your position moved your way. That part can be true even if the exit still feels terrible.
The screen price is not a promise
A last trade or midpoint can look great, but it does not mean your full size can sell there right now.
Your size may be the real problem
A small order might exit cleanly while a larger order chews through the bid stack and gets worse fills.
You still have choices
You can lower price, split the order, wait for more liquidity, or hold to resolution if the thesis still stands.
Your four exit options
Lower your limit price
Fastest path to liquidity, but you are explicitly accepting a worse exit.
Sell in smaller chunks
Helps you test real depth and reduce the chance of smashing through the whole bid stack at once.
Wait for more liquidity
Reasonable if the market still has life and you are not forced to exit immediately. Still, no one owes you better bids later.
Hold to resolution
Sometimes the cleanest answer if the market moved your way but the order book is too thin to reward you for leaving early.
Before you force the exit, ask yourself:
- • Is the best bid actually near the displayed price?
- • Is there enough depth for my whole position?
- • Am I trying to dump too much at once?
- • Would waiting for new buyers help? (It might, but no one owes you better bids later.)
- • Would holding to resolution make more sense if my thesis is intact?
Why is my Polymarket claim failing? (And why the app kicks you out)
You tapped "Claim" or "Withdraw Winnings," got an automatic message saying "failed," and now the app keeps kicking you out of login. Here's what's actually breaking — and what order to fix it in.
The "failed" message and the login loop are usually two separate problems happening at the same time. They look like one bug because they land in the same 30 seconds, but they sit in different layers of the stack.
Problem A is on-chain: the claim transaction itself reverts or never gets signed. Problem B is off-chain: your browser's Polymarket session drops mid-transaction, so when the wallet app hands you back, the site has already forgotten you.
We walk them one at a time, then give you a single fix order that handles both.
Problem A — The claim transaction is failing
Five mechanical reasons the on-chain claim can't complete. Most of the "automatic message failed" popups trace back to one of these.
Not enough MATIC/POL in your wallet for gas
Polymarket claims require an on-chain transaction on Polygon. If your wallet has zero native Polygon gas (MATIC, or POL after the rename), the signature fails with an error that can look exactly like an anonymous 'automatic message failed' notice.
Fix: Send a very small amount (roughly a dime's worth) of MATIC/POL to your wallet address on Polygon, then retry.
A previous transaction is still pending
Tapping 'Claim' twice before the first attempt confirms creates a nonce collision. The second transaction often fails while the first one is still stuck in the mempool.
Fix: Open your wallet's activity/history tab, wait for any pending transaction to confirm or speed it up, and only retry once the slot is clear.
Your wallet disconnected mid-signature
Browser-wallet sessions drop, especially on mobile when the app switches contexts. The claim is initiated, but the signature request never reaches a connected wallet.
Fix: Fully disconnect the wallet from Polymarket settings, close the tab, reconnect from a fresh tab, and only then retry the claim.
The signature window closed before you approved it
On mobile, the wallet app sometimes pops up and closes again before you can tap approve. The transaction never gets signed, so Polymarket records a failed attempt.
Fix: Tap claim, immediately switch to your wallet app, and look for the pending signature request in its notifications or activity tab — approve it there.
A browser extension is blocking the request
Ad blockers, strict privacy extensions, and third-party cookie blockers can silently break the signature flow for a wallet connector.
Fix: Try a clean browser profile, or disable extensions for app.polymarket.com only, then reload and retry.
Problem B — The app is kicking you out
Two common reasons Polymarket's web session drops in the middle of a claim.
Session token expired during the wallet signature delay
Polymarket's web session has a short life. If the signature step takes long enough (wallet app open for several minutes, mobile context switching, slow approval), the session can lapse the instant the transaction resolves — and the app logs you out.
Fix: Log back in, let the previous claim attempt fully settle in your wallet's history, then retry from a clean session.
Your browser is blocking the auth cookies
If your browser blocks third-party cookies, or if your mobile wallet opens Polymarket in a different webview than your main tab, the session can exist in one context and not the other. Result: 'logged in here, logged out there.'
Fix: Use the same browser for both the wallet and the Polymarket tab. Desktop Chrome, Chrome mobile, or Brave with third-party cookies allowed for app.polymarket.com are the safest paths.
Six-step fix order that handles both
Check your wallet's MATIC/POL balance
If it's zero or effectively zero, top up a small amount before doing anything else. Nothing else works if the gas token is missing.
Clear any pending transactions
Open your wallet's activity tab. Wait for every pending transaction to confirm — or cancel/replace them — before you touch the claim button again.
Fully log out and disconnect
Log out of Polymarket, disconnect the wallet from the site, and close the browser tab entirely. Do not keep a stale session alive across retries.
Open a fresh tab and reconnect
Open Polymarket in a new tab (or a second browser to compare), log back in, reconnect the wallet, and verify the same address is showing.
Verify the position still exists before retrying
Go to 'My Positions' and confirm the position is present and claimable. If it's missing entirely, stop — that's a data issue for support, not a transaction issue.
Claim once, approve quickly
Tap claim, immediately switch to your wallet app, and approve the signature within about a minute. If it fails again after a clean attempt, stop retrying and move to support.
When to stop and escalate
Some failures aren't user-fixable. Stop retrying when any of these apply.
- The claim has failed 3 or more times after you've worked through the six fix steps.
- The position shows as resolved on-chain (you can see it on Polygonscan) but the Polymarket UI shows nothing to claim.
- The claim button is missing or greyed out on a position the UI admits is yours.
- You can't log back in at all after clearing cache and trying a fresh browser.
Why is my Polymarket withdrawal delayed?
If a tiny withdrawal arrived instantly but a larger one is still pending, that does not automatically mean your money disappeared. It usually means the second transfer took a different route, hit extra review, or is waiting on an outside processor.
Quick answer: if one withdrawal cleared fast and another did not, the slower one is usually taking a different path or got queued for extra review.
Which version of the problem do you actually have?
Status says completed, but I never received it
The app looks done, but your wallet or payout destination does not.
Still pending after days
The request exists, but it never seems to leave the queue.
A tiny withdrawal worked, but the real one didn't
A later micro-withdrawal landed first and made the larger one look lost.
Confused about wallet vs cash withdrawal path
You need to know which leg actually owns the delay.
Support escalated it, but nothing changed
The ticket moved internally, but your evidence still matters.
The five most common causes
Different rail than your test withdrawal
Meaning
A small transfer clearing quickly does not prove a larger transfer will use the same path or clear on the same timeline.
What to check
Confirm the destination, payout method, and any on-screen status text for both withdrawals before assuming they were identical.
Extra review on a larger amount
Meaning
Larger withdrawals can trigger extra checks even when the same account had a smaller transfer go through without friction.
What to check
Compare the exact amounts, request timestamps, and whether the later withdrawal shows a different status or review note.
Third-party payout processor delay
Meaning
A withdrawal can leave the first internal stage and still be waiting on another service before you actually receive funds.
What to check
Look for status changes, transaction references, or any indication that the withdrawal moved beyond the request-creation stage.
Wallet / network mismatch or bridge confusion
Meaning
Address, network, or wallet-path confusion can make a normal transfer look missing when it is really pointed at the wrong place or wrong leg.
What to check
Verify the destination wallet or payout method, the expected network, and whether you are checking the correct receiving location.
Status lag: internal completion does not equal final receipt
Meaning
A platform can mark its own step complete before the destination shows the funds as fully received.
What to check
Match the in-app label against whatever proof of receipt you actually have at the destination side.
The actual withdrawal path
Most withdrawal panic comes from collapsing five distinct stages into one. Here's the flow — identify which stage is actually slow before you label it missing.
Polymarket balance
Your funds start inside the platform balance view.
Withdrawal request created
This only proves the request exists, not that the destination has funds yet.
Payment rail / wallet path selected
This is where user expectations often break: the path matters.
Processor / network confirmation
Middle-leg delays often live here rather than at the first or final screen you check.
Destination receives funds
This is the moment that actually matters to the user.
Polymarket withdrawal shows "declined" and my balance now reads zero — what happened?
Different operational shape from a delayed withdrawal. The status flipped to "declined" or "failed" and the in-app balance dropped to zero before any payout arrived. This is almost always a display-vs-on-chain state mismatch, not a missing-funds event. The on-chain Polygon ledger is the source of truth.
What this section IS: a neutral, primary-source-anchored map of the operational shape "withdrawal status declined + balance display zero." We describe what the app display means vs. what the on-chain ledger means.
What this section is NOT: an accusation that Polymarket is withholding funds, an endorsement of any third-party recovery tool, a recommendation to DM anyone, or a guarantee of resolution. Every withdrawal flows through Polygon on-chain; the on-chain ledger is the source of truth. If your on-chain balance is intact, no funds were lost regardless of what the app display reads in the short term.
What "declined + balance zero" actually means
Polymarket's app surfaces a display layer on top of the on-chain Polygon ledger. The two can briefly disagree: the display can read "declined" and zero while the ledger still shows funds at your address, or the display can lag a partial cash-out so the residual leg looks like it vanished. The on-chain record is authoritative — the app display is a view of it, not a substitute for it.
Three causes that look identical from your screen
Rail rejected before commit
Display refresh lag after a partial cash-out
Heavy-load transient internal-state error
Action map — in order
Resolve which on-chain reality you're in before you do anything else. Most of these states clear on a clean refresh once you know which one you have.
Open polygonscan.com and paste your wallet address
Check whether the funds are still on-chain at your address. If they are, no funds were lost — the app display has not re-fetched the ledger yet. (Type the URL yourself; do not click a link from a DM.)
Hard-refresh the Polymarket app or website
Clear the cached state and re-check the balance. The majority of display-vs-on-chain mismatches resolve at this step alone, with no support contact needed.
If on-chain shows funds but the app still reads zero after refresh, file a support ticket via the in-app help flow only
Do NOT click DM links from accounts claiming to escalate or recover funds. Polymarket support does not initiate DMs. See the cross-link to the support-DM section below.
If on-chain shows zero AND the withdrawal status reads 'declined,' the rail was rejected before commit
No funds moved — nothing was sent. Re-attempt the withdrawal to a destination you control on Polygon, and confirm the destination network matches what Polymarket supports.
What this is NOT
A "declined + balance zero" display state is not a "lost funds" event in the on-chain sense. The phrase "money disappeared" describes what the app display reads in the moment; the on-chain ledger is what controls the actual position. We do not characterize this shape as theft, fraud, scam, or platform malfeasance — it is a state mismatch with multiple resolvable causes.
Order failed before the win?
If the symptom happened during the buy click, start with the order-flow page before treating it as a settlement backlog.
Order looked filled, then failedWorried this is a scam-DM situation?
If anyone DMs offering to recover funds or escalate your ticket, stop and read the dedicated walkthrough first.
Polymarket support will never DM you firstCutover-week operational variance (Apr 28)?
If your declined withdrawal lands inside the V2 cutover window, the migration page covers what changes and what to expect.
What changes with the Polymarket V2 cutoverMy Polymarket iOS app shows a settled position I can't exit, or a cash balance that disagrees with the web — what's going on?
A distinct shape from a balance-mismatch (§2) or a withdrawal stuck after sale (§6): the iOS app surface renders a settled or already-resolved position as still open, or surfaces a cash balance that disagrees with what the web client shows. Reports cluster around the platform's acknowledged early-morning maintenance windows and resolve once the app re-fetches.
What this section IS: a neutral, mechanism-class description of an app-vs-web rendering divergence on iOS — not an on-chain state event. The on-chain Polygon ledger is authoritative; the iOS app surface is a view of it.
What this section is NOT: a recommendation or anti-recommendation of the iOS app vs. the web client, a guarantee of any specific maintenance-window timing, or a claim that funds are missing. We do not link out to the App Store and we do not characterize this shape as theft, fraud, or platform malfeasance.
What "settled but stuck" actually means on iOS
The iOS client caches a session view of your portfolio. When a position resolves (expires worthless, settles to 100¢, or is closed via the order book), the resolution is recorded on-chain on Polygon, but the iOS surface can lag the ledger — sometimes for hours, sometimes across a maintenance window. During the lag, the position can appear open, the "exit" or "sell" control can return an error, and the cash balance can read a stale value that disagrees with what the web client at polymarket.com shows for the same wallet. None of this is an on-chain event; the underlying ledger has already settled.
Three causes that look identical from the iOS screen
Cached session view of a settled position
Within an acknowledged maintenance window
App-vs-web cash-balance drift
Action map — in order
Resolve which surface you're looking at before doing anything else. Most app-vs-web divergences clear once the iOS session re-fetches.
Open polymarket.com on a desktop or mobile browser and check the same wallet
If the web client shows the position as settled and the cash balance as expected, you are looking at an iOS rendering lag — not an on-chain problem. The web view is closer to the Polygon ledger.
Force-close and reopen the iOS app
This drops the cached session view and forces a re-fetch. The majority of settled-but-stuck displays clear at this step.
If the divergence persists, paste your wallet address into polygonscan.com
Confirm the on-chain state directly. The ledger is authoritative; the iOS surface is a view of it. (Type the URL yourself; do not click a link from a DM.)
If on-chain shows the position settled but the iOS app still renders it as open after refresh, file an in-app support ticket
Include the wallet address, the market slug, and screenshots of both the iOS view and the web view. Do NOT respond to DMs offering to escalate or recover a stuck position.
Check status.polymarket.com for an acknowledged maintenance or incident window
If the divergence lines up with a published incident, the right action is usually to wait for the window to close and the next session refresh to re-sync.
Worried this is a scam-DM situation?
If anyone DMs offering to recover funds or unstick your position, stop and read the dedicated walkthrough first.
Polymarket support will never DM you firstCutover-week operational variance (Apr 28)?
If the divergence lands inside the V2 cutover window, the migration page covers what changes and what to expect.
What changes with the Polymarket V2 cutoverMy Polymarket sports bet settled but I haven't been paid for days, and the app shows an "available soon" balance — what's going on?
A distinct shape from a withdrawal stuck after sale (§6), a "withdrawal declined" status (§6.5), or an iOS-vs-web rendering divergence (§6.6): the bet has resolved on the market but the payout has not landed in the cash balance, and the app surface displays an "available soon" or pending-reconciliation badge — sometimes for multiple days. Users have reported an in-app banner stating that a balance fix is in progress during platform-wide reconciliation work.
What this section IS: a neutral, mechanism-class description of a settlement-to-balance reconciliation backlog. The on-chain Polygon ledger is authoritative; the cash-available view in the app surface is a derived display that can lag.
What this section is NOT: a claim that funds are missing, a characterization of the delay as theft / fraud / scam / platform malfeasance, a guarantee of any specific resolution timeline, or a recommendation to use any third-party "recovery" tool, signature-requesting bot, or external script. We do not echo specific user dollar amounts as factual claims; we use illustrative numbers only. We never name individual users.
What "available soon" actually means
Three structural causes that all surface as the same in-app symptom — a pending-payout banner, an "available soon" cash-balance row, or a settled position that did not credit the wallet within the user's expected window:
Settlement-to-balance reconciliation lag
Platform-wide reconciliation work, in-app-banner-acknowledged
Post-cutover collateral migration carry-over
Action map — in order
Open polymarket.com on a desktop browser and check the same wallet
If the position is shown as resolved on web but the iOS surface still shows the bet as open, that's the §6.6 iOS rendering shape — a different mechanism. Otherwise continue to step 2.
Paste your wallet address into polygonscan.com
The on-chain ledger is authoritative. If the resolution is recorded on-chain, the payout is owed by the protocol and the in-app delay is a propagation / rendering issue — not a missing-funds event. (Type the URL yourself; do not click a link from a DM.)
Look at the top of the app surface for a platform-wide balance-fix banner
If a reconciliation banner is visible, the platform has acknowledged the work is in progress. Wait for the banner to clear before opening a support ticket. We never quote a specific wait time — the banner is the platform's own running statement.
If no banner is visible AND the on-chain resolution is recorded AND 24+ hours have passed, file an in-app support ticket
Use the in-app help flow only. Do not respond to DMs from accounts claiming to be support. Do not sign anything with your wallet to 'recover' funds.
We do NOT recommend any third-party 'claim bot,' 'payout recovery,' or wallet-signing script
The on-chain ledger is the source of truth; no off-platform tool can accelerate an on-platform reconciliation. Anyone offering one is a scam.
What we are NOT saying
We are not saying funds are missing. We are not saying the platform is engaged in fraud or theft. We are not naming individual users or echoing specific user dollar amounts as fact. We are not committing to a specific resolution timeline. We are describing a mechanism class — a reconciliation backlog between an on-chain settlement and the rendered cash-available view — that users have reported the platform itself acknowledges via an in-app banner during reconciliation windows.
Worried this is a scam-DM situation?
If anyone DMs offering to recover a stuck payout or accelerate a reconciliation, stop and read the dedicated walkthrough first.
Polymarket support will never DM you firstCutover-week operational variance (Apr 28)?
If your reconciliation lag straddles the V2 cutover window, the migration page covers what changes and what to expect.
What changes with the Polymarket V2 cutoverMarket loads but API/auth/order requests fail?
That is a different access-layer question: public market reads, authenticated CLOB calls, geoblock status, frontend-only restrictions, and IP/WAF friction can fail independently.
API / geoblock / 403 troubleshootingMy Polymarket position was visible before resolution, then disappeared or changed — what should I check?
If a position disappears from one Polymarket surface before final resolution, separate four states before assuming funds are missing: app display, open position inventory, wallet or ledger state, and official market resolution plus maintenance status.
30-second answer: one surface changing before final resolution is a state-triage problem first. Check the official status page, compare web and mobile, preserve evidence, confirm the market state, and use the official in-app help flow if the mismatch persists.
Separate four states before you panic
App display / cached surface
A phone app, mobile browser, or desktop tab can show a stale account view. Compare surfaces before treating one screen as the final state.
Open position inventory
Check whether the same account still shows the position in the open-position view, trade history, or another official account surface.
Wallet / ledger / address state
If a wallet or address view is available, preserve what it shows. Do not use a third-party wallet-fix tool or sign a recovery request from a stranger.
Official market resolution + maintenance status
Confirm whether the market is still trading, pending, resolved, or settled, then check the official status page for incidents or maintenance windows.
Five-step action map
Check status.polymarket.com for active incidents or maintenance windows.
Compare web, mobile web, and the app while signed into the same account.
Save screenshots plus timestamp and timezone for the market page, My Positions view, and wallet/address view if available.
Confirm whether the market is still trading, pending, resolved, or settled.
Use the official in-app help/support flow with an evidence pack; do not use third-party recovery tools.
What this is NOT
- Not proof that funds are missing.
- Not proof that Polymarket deleted, stole, hid, or removed a position.
- Not a reason to share seed phrases, use recovery bots, browser extensions, Telegram or Discord support, or third-party wallet-fix tools.
- Not the same as a final resolved market failing to credit proceeds.
Not the same as
Settled bet not credited
Resolved market, but proceeds have not reached the available balance.
Open related guideiOS settled-position stale view
One app surface still shows a settled position as stuck or non-exitable.
Open related guideWithdrawal declined + balance zero
A withdrawal failed or declined and the app balance temporarily looks wrong.
Open related guideRules changed after trading started
A rules/title/date conflict or official clarification question.
Open related guideOrder looked filled, then failed
A V2 app display, orderbook, collateral, or settlement-state mismatch.
Open related guidePolymarket recovery tool not working? What to do when your deposit is stuck
What to do when your deposit is stuck and the recovery tool itself is down — with the documented escape paths, what cannot be recovered, and when a stuck deposit becomes a regulator complaint.
This section is for: deposits that never arrived, funds trapped in a smart contract on the wrong network, and the case where recovery.polymarket.com or matic-recovery.polymarket.com itself returns an error or shows a $0 balance.
This section is NOT for: a claim failing with "automatic message failed" (see §5 above), a withdrawal stuck after the sale (see §6 above), or a pure balance-display bug where the UI shows zero but Polygonscan shows your funds at the correct address (that is a refresh / session cache problem — see §2).
Sent USDC to your Polymarket profile address?
First identify which address actually received the transaction before you file support, retry a deposit, or assume funds are gone.
Start by deciding which address you used:
- 1Deposit-widget address shown during the deposit flow
- 2Your Polymarket profile / wallet address
- 3A copied address from an old wallet, email, DM, or thread
Deposit-widget address
What it means: The address came from the Polymarket deposit flow for that session.
Next step: Confirm the transaction hash, network, token, and confirmation state before escalating.
Do not: Do not send a second deposit just to test whether the first one clears.
Polymarket profile / wallet address
What it means: The address belongs to your Polymarket account profile or embedded wallet, but may not be the current deposit-widget path.
Next step: Use the official recovery flow for the network/token you sent, then file support with an evidence pack if the tool fails.
Do not: Do not use any third-party recovery tool, wallet-repair site, or DM support link.
Unknown, old, or third-party address
What it means: The address was copied from somewhere outside the current Polymarket deposit/profile surface.
Next step: Preserve the transaction hash and destination address. Recovery may be impossible if the destination is not controlled by your account or the supported recovery flow.
Do not: Do not share seed phrases, private keys, screenshots with sensitive account details, or wallet signatures publicly.
Before filing support, collect:
- Transaction hash
- Network used
- Token used
- Destination address copied from the original transaction
- Screenshot of the Polymarket screen that showed the intended address, if available
- Whether recovery.polymarket.com or matic-recovery.polymarket.com loaded or errored
Three failure modes
Deposit sent, never arrived
It has been more than 10 minutes and the balance still shows $0.
Polymarket's deposit help article documents that a deposit sent through Deposit → Transfer Crypto should appear within about 10 minutes. Before you treat a deposit as missing, wait the full window.
What to check first
- Paste your transaction hash into polygonscan.com and confirm it has at least one block confirmation.
- Verify the destination address matches the deposit address Polymarket showed you — not an address copied from somewhere else.
- Confirm you sent the correct collateral token (native USDC on Polygon) and not a different variant or a different chain.
- Re-open Polymarket in a new tab and hard-refresh. The web client can cache a $0 state for several minutes after an on-chain update.
When to escalate
- If the 10-minute window has passed and the tx confirmed on Polygonscan but the Polymarket balance still reads $0, file with polymarket.com/support.
- Include the tx hash, your public wallet address, the email on your Polymarket account, and a Polygonscan screenshot.
- Do not send a seed phrase. Do not accept a DM from anyone claiming to be support.
Sent to the wrong network or wrong token
Ethereum mainnet, Base, Arbitrum, or a non-canonical token on Polygon.
Polymarket is on Polygon and uses a specific USDC variant as collateral. Funds sent to a different chain, a different token, or a smart-contract address that does not recognize the transfer can sometimes be recovered — but only through the documented flows.
Ethereum mainnet or a non-Polygon chain
If you sent USDC on Ethereum, Base, Arbitrum, or another EVM chain to a Polymarket address, recovery.polymarket.com is the documented tool. It detects balances at your address across supported networks and walks you through a bridge-back flow. Do not send a second deposit until the first has been recovered or written off.
Non-USDC.e token on Polygon
If you sent a non-canonical USDC on Polygon (USDC.e before bridging, or a different stablecoin entirely), the in-app swap/bridge may be able to convert it. If the token is too esoteric, matic-recovery.polymarket.com is the backup. If neither works, this is a support ticket — expected resolution time is days to weeks depending on the token.
Other networks (Solana, Tron, Bitcoin, etc.)
Funds sent to a Polymarket address on a non-EVM chain are generally NOT recoverable by Polymarket. This is a fundamental wallet-compatibility issue, not a policy one. Polymarket support cannot move funds on chains where they do not control the destination address. Treat this as lost funds and consider it a hard lesson.
Do NOT
- Do not use a third-party 'recovery tool' that asks for your seed phrase or private key. There is no legitimate recovery flow that requires those.
- Do not re-send funds to the same address hoping the first deposit will 'clear.' Two stuck deposits are not easier to recover than one.
The recovery tool itself is broken
recovery.polymarket.com errors out, shows $0, or never loads at all.
When the official recovery tool is the thing that's broken, you are in escalation-only territory. There is no self-serve path. What matters is building a clean evidence pack so support can process the ticket faster.
Before you give up and ticket
- Try a fresh browser profile with all extensions disabled. Ad blockers and strict privacy extensions can break the recovery tool's wallet connector.
- Try a different browser entirely (Chrome → Brave, or Brave → Firefox). Some Web3 connectors fail silently in one browser while working in another.
- Try connecting with a different wallet if possible (MetaMask vs Rabby, for example). The recovery tool's connector may be failing on the wallet's side, not Polymarket's.
- Check status.polymarket.com. If the recovery tool is in a known-broken state, there's no workaround except waiting and ticketing.
When to escalate
- File at polymarket.com/support. In the ticket, say explicitly that the recovery tool is not loading or is returning an error.
- Attach: screenshot of the recovery tool's error state, the tx hash of the stuck deposit, your public wallet address, your Polymarket email, a screenshot from the other browsers/wallets you tried, and timestamps.
- This is slower than Cases A or B. Expect days, not minutes. That is not a sign something is extra wrong — it is how the escalation-only lane works.
What Polymarket support will never do
Scammers monitor every social platform for posts about Polymarket balance issues, claim failures, and stuck deposits. They DM within minutes, pretending to be support, and their goal is your seed phrase. These rules are not optional.
- Real Polymarket support will never DM you first on Twitter/X, Discord, Telegram, or anywhere else. If someone DMs you claiming to be support, they are not.
- Real Polymarket support will never ask for your seed phrase, recovery phrase, or private key. There is no legitimate flow that requires those.
- Real Polymarket support will never ask you to install a 'balance fix' tool, browser extension, or Telegram/Discord bot with wallet access.
- Real Polymarket support will never ask you to connect your wallet to an unfamiliar domain. Bookmark polymarket.com and recovery.polymarket.com — type them, don't follow DM links.
- Real Polymarket support operates through polymarket.com/support tickets. Scammers prey on users posting balance issues on social platforms.
For the full impostor-pattern breakdown, see Polymarket support will never DM you first.
What to send when you file a ticket
Every support ticket resolves faster when you lead with a clean evidence pack. Missing details turn a one-reply resolution into a three-day back-and-forth.
- Your wallet address (public — this is safe to share).
- The market URL or position ID if relevant.
- A screenshot of the error or mismatch.
- Transaction hash if relevant — from Polygonscan or your wallet's activity tab.
- Exact amount and timestamp (with timezone) of the event.
- Browser and device info (e.g. 'Chrome 133 on iPhone 15 Pro').
- Whether the same issue repeats across a clean retry or different markets.
- What you have already tried — list the steps above you worked through.
- For position-visibility issues: market URL or slug, screenshots before and after if available, position ID if visible, timestamp plus timezone, surface used (iOS app, web, or mobile web), wallet/address view if available, and whether status.polymarket.com showed an active incident or maintenance window at the same time.
Use the official in-app help/support flow from the signed-in Polymarket app or website. Do not invent or trust support emails from social posts, DMs, or search ads. Never include a seed phrase, a recovery phrase, or a private key. Real Polymarket support will never ask for these.
Frequently asked
Related guides
API / geoblock / 403 troubleshooting
Separate public reads, authenticated CLOB calls, geoblock status, frontend-only restrictions, and access-layer friction.
Order looked filled, then failed
A V2 order-flow checklist for app display, orderbook state, collateral display, and settlement state.
Cash-out path and payout math
Why early exits can pay less than the headline probability and when holding to resolution changes the math.
What changed with Polymarket V2
Collateral, order-flow, and pUSD migration context for post-cutover troubleshooting.
Resolution and dispute evidence
Where to find source documents, dispute windows, and settlement evidence when a market resolves unexpectedly.
Can rules change after trading starts?
How to separate a real official clarification from headline confusion, app display panic, or a generic settlement dispute.
Polymarket 'View-Only Mode' mechanism
What view-only mode is, how location detection works, and why we do not recommend VPN bypass.
Polymarket resolution-clause fallback explained
Pre-trade literacy: how fallback clauses can flip a Polymarket question to 50-50 if the trigger event never happens.
Polymarket guide
The canonical Polymarket overview — product, fees, state availability.
Polymarket funding guide
Deposit paths, gas on Polygon, and the first-trade friction checklist.
Polymarket support scam warnings
How impostors target users posting balance issues on social platforms.
Cross-platform: why is my P&L wrong?
The same 'my money is lying' confusion, not specific to Polymarket.
When prediction market funds are stuck
Broader triage for balances, payouts, and missing-funds panic across platforms.
How to exit an illiquid prediction market
The broader playbook for getting out of a thin book without eating the full spread.