Pocket Broker Withdrawal Problems and Solutions
The most common complaint
The most repeated complaint is "they won't let me withdraw." It almost always describes a withdrawal that's stuck, not a payment denied, and behind it there's a pending requirement the user hasn't identified yet.
Search for any trading platform's name next to the word withdrawal and you'll find the same thing: messages written in the heat of the moment, with no folio, no dates, and no mention of which method was used. That doesn't mean the complaints are false. It means they're poorly told, and poorly told complaints don't help anyone resolve their own case.
What users are actually reporting
When those reports are sorted by what they describe, not by tone, four fairly stable groups come out:
- The request was sent and is still under review longer than the person expected.
- The request was cancelled and returned to the balance, almost always because the payout details didn't match.
- The withdraw button doesn't enable, because of committed balance or a pending condition.
- The withdrawal went through, but the money hasn't shown up in the user's bank yet.
All four get described the same way — "they won't pay me" — and all four are solved differently. Identifying which one you're in is half the work.
A delay is not a denial
This distinction seems obvious and almost nobody makes it in the moment. A delayed withdrawal exists, has a folio, shows up in your history, and moves through stages. A cancelled withdrawal also leaves a trail: the balance returns to your account and there's usually a reason written down. A withdrawal that has really been denied would be something else: money that never comes back to your balance, with no explanation and no response. That last scenario is by far the least frequent of the three, and claiming it requires evidence, not impatience.
Why it causes so much alarm
Because it's your money and because the clock is running in your head, not in the system. On top of that, fixed-time options are a high-risk market and a lot of people arrive with a fresh loss: once you've already lost trades, any friction with the remaining balance reads as confirmation of the worst. It's human. But it's worth separating the two things, because a market loss and a stuck withdrawal have nothing to do with each other.
This page's honest framing
We're not going to tell you here that the platform keeps the money, because the patterns don't point that way; and we're not going to tell you everything is always perfect either. The useful read is in between, and fairly boring: the vast majority of these cases are process problems with a specific, fixable cause. The uncomfortable part, said once, is that this is an international platform: there's no Mexican authority arbitrating for you, so your real leverage is documentation and patience, not threats. The following sections are, basically, how to use that leverage.
Before concluding anything, place your case: request under review, request cancelled, button not enabling, or money on its way to the bank. Each one has its own fix.
Why a withdrawal is held
A withdrawal gets stuck for a short list of causes: incomplete verification, a name that doesn't match, a method different from the deposit one, a pending bonus condition, wrong bank details, or an expired payout instrument.
This is the section that solves most cases. Find your symptom in the table, read it honestly, and apply the fix before writing to anyone.
| Symptom | Likely cause | What to do |
|---|---|---|
| The withdrawal stays in review and doesn't move | Incomplete verification or a flagged document | Check each document's status on your profile, fix exactly what was flagged, and resubmit only that file |
| The request cancels itself and the balance comes back | The payout account's holder doesn't match the platform's | Cash out to your own account; if your surname changed or there's a typo, fix the profile first |
| The method you want doesn't show up | Money has to come back through the route it went in | Use the method you deposited with; if it was cash, prepare a bank account or e-wallet of your own |
| The withdraw button doesn't enable | Balance tied up in open trades or an unmet bonus condition | Check how much of the balance is actually withdrawable and which condition is still active before pushing further |
| The transfer bounces back before reaching the bank | Incorrect CLABE, a transposed digit, or a closed account | Copy the CLABE again from the banking app, confirm the account accepts transfers, and request again |
| The refund to the card isn't reflected | Card expired, cancelled, or replaced since the deposit | Notify support before requesting and ask for payment through another enabled route |
| You cancelled the withdrawal by mistake | You tapped cancel to "fix" something and the balance came back | Request again just once and don't cancel again: every cancellation resets the queue |
| It went through, but the money doesn't show up | It's in the bank stage, or it landed in another of your accounts | Check all your accounts and the non-business days before filing a complaint |
| It's already taken longer than you expected | Volume, a first withdrawal, or recent changes to your details | Compare against the timeframe the platform publishes, not your own expectation, and open a single ticket |
Verification is cause number one
If you had to bet on a single explanation, bet on this one. An incomplete file doesn't stop you from trading or depositing, which is why a lot of people discover the requirement right on the day of their first payout. The fix is boring and it works: complete your account verification and upload everything calmly before you need it.
The name has to be the same everywhere
Your profile, your ID, your proof of address and the payout account all have to say the same person, written the same way. A nickname, a single surname, or a typo is enough for the request to get cancelled. It's not suspicion: paying a different holder is exactly what anti-money-laundering rules prohibit.
The accepted bonus
This is the one that bothers people most because it tends to catch them off guard. Accepting a promotion means accepting its condition too, almost always a traded-volume requirement. Until that condition is met, the part of the balance tied to the bonus isn't withdrawable, and sometimes neither is the whole request. It's not a hidden trick: it's in the promotion's terms, which almost nobody reads when clicking accept. If the bonus is getting in your way more than helping, check whether you can decline it from your account or ask support to, and in the future consider simply not accepting it.
Go through the table before writing to support: in most cases the cause is on your own account and gets fixed in minutes.
How payment times factor in
The wait has two legs: the platform's internal review and the trip through your bank or e-wallet. Only the first depends on the operator; the second depends on hours, calendars and payment networks.
It's worth explaining why there are no figures on this page: timing changes with the method, the volume and the receiving bank, and publishing a number that goes stale would only make you plan badly and get alarmed for no reason. The current figure is on the withdrawal screen and in the platform's help centre; check it there. What is stable, and what lets you judge your own case, is how the wait is put together.
Leg one: internal review
Before the money moves, someone confirms your file is complete, that the destination's holder is you, that there are no pending conditions, and that the balance is enough. It's the only leg you have real control over, and also the one that stretches out most when something's missing. A clean file turns it into a formality; a half-finished one turns it into a queue.
Leg two: the road to your money
After that, the platform is no longer in charge. What happens depends on the channel:
- Bank transfer. The credit travels through the interbank system and depends on your bank's operating windows. Weekends and public holidays don't count, and some banks review credits arriving from abroad more closely.
- E-wallets. Usually the fastest link because confirmation is electronic end to end, but the e-wallet also has its own limits and verification tiers.
- Refund to a card. Goes through the issuer's network, which has its own cycles. Rarely instant, and if the card changed since the deposit, it doesn't arrive.
What extends the wait without anything being wrong
- Requesting on Friday afternoon, on a weekend, or over a long weekend: the bank clock starts once the system reopens.
- Being your first withdrawal: the file gets a closer look than the following ones.
- Having recently changed your email, phone or payout account, which triggers extra security checks.
- Volume spikes, typical after long weekends.
- Having requested several withdrawals in a row: they process in a queue, not in parallel.
How to tell if your case is on track
Open your account's withdrawal history and look at the status. If the request shows as sent or in process, your details are correct, and you haven't exceeded the timeframe the platform publishes, then what's running is a normal procedure even if it feels endless. The signal that does deserve attention is different: a status that doesn't change well past the published timeframe, or a cancellation with no visible reason.
Compare your wait against the timeframe the platform publishes and the bank calendar, not against your own expectation: that explains almost every delay.
How to unblock the withdrawal
The order that works is: complete verification, match the method to the deposit, close out any bonus condition, fix the payout details, and only then open a single, well-documented ticket.
Do it in this order. Skipping the first steps and writing in right away is the surest way to lose days waiting for a reply that's just going to tell you what you could have fixed yourself.
The four fixes that depend on you
- Finish verification. Valid ID on both sides, recent proof of address in your name, photos in daylight with no flash, original files.
- Match the method. Request the payout through the route you deposited with. If you funded in cash, prepare a bank account or e-wallet in your name, because there's no cash payout.
- Resolve the bonus. Check whether you have an active promotion and which condition it's still missing. If you're not going to meet it, find out how to decline it before requesting the withdrawal again.
- Fix the payout details. Copy the CLABE from your bank's app instead of typing it, confirm you're the holder, and that the account is active.
After each fix, request again just once. Duplicate requests don't speed anything up: they multiply the transactions someone has to reconcile, and that reconciliation does take time.
How to write a ticket that actually gets resolved
A good message is short, specific, and comes with the evidence attached. Include:
- The email you signed up with, never the password.
- The request's folio or identifier and its date and time.
- The amount and the method chosen.
- The payout details as you entered them, so they can be compared.
- A clear sentence about what you expected and what happened.
- Screenshots of the request's status and, if the money didn't arrive, the period's bank statement showing the credit is absent.
What not to do
- Don't open duplicate tickets. Each one creates a different thread, splits your case between agents who can't see each other, and ends up slower, not faster.
- Don't threaten or insult. It doesn't speed anything up and turns a simple case into an uncomfortable one.
- Don't request a chargeback from your bank as a first move. It's the instinctive reaction and it usually backfires: a chargeback opened while the withdrawal is in progress can freeze your account on the platform and stop the very payment you wanted to collect. It's a last-resort tool, not a first attempt.
- Don't share passwords or codes with anyone who messages you offering to unblock your withdrawal. That offer, on Telegram or anywhere else, is the classic scam that circles around these cases.
- Don't cancel and re-request in a loop. Every cancellation sends you to the back of the queue.
The order for escalating
- Chat or ticket inside your account, with all the evidence, in a single thread.
- Reply in that same thread if you're asked for something, without opening a new one.
- An explicit request to escalate to a higher level if the thread stalls, citing the folio and summarising what's already been sent.
- A formal email to the support or compliance channel the platform publishes, attaching the full history.
- If your case involves your bank — a refund that doesn't show up, for example — ask your bank to trace the credit using the relevant reference.
Move up one step at a time and leave a reasonable gap between each. Escalating all five in the same day only resets the reading of your file.
Fix what's in your hands first, then open a single ticket with a folio and screenshots, and escalate one step at a time: that's what separates a resolved case from one going in circles.
When it's a real problem
There's a real problem when the published timeframe is clearly exceeded, your details are correct, there are no pending conditions, and the thread with support has stopped moving despite the evidence sent.
Almost everything described as a block is delay or a pending requirement. But not everything, and it's worth being clear on the threshold, so as not to treat every wait as an emergency or ignore a signal that actually matters.
How to tell delay from a block
| Signal | Looks like delay | Looks like a block |
|---|---|---|
| Request status | Sent or in process, with a visible folio | No trace in the history despite having been sent |
| Your details | Complete and matching | Something pending that nobody explained |
| Timing | Within the published window, or with non-business days in between | Clearly exceeded with no explanation |
| Support | Replies and asks for something specific | Stops replying or repeats generic answers to specific evidence |
| The balance | Deducted or returned consistently | Neither paid nor returned, with no reason |
When to actually escalate
When the right-hand column describes your case across several rows at once, you're no longer waiting: you're facing something that needs pushing. That's when the formal escalation described above applies, with the full history and a professional tone. It also means pausing your trading while it gets resolved, so you don't mix new transactions with an open case.
What's worth watching more closely
- That whoever writes to you is really the platform's support, not a third party who contacted you separately.
- That you're logging in through the official domain and app, not a clone that copied the interface.
- That nobody asks you for an upfront payment to release a withdrawal. That doesn't exist: it's the clearest fraud signal there is, and it almost always comes from scammers posing as support.
A realistic expectation
Two ideas to close, with no dressing up. First: losing money trading is not the same as a blocked withdrawal. The product is high risk and most retail traders lose; that loss isn't fraud and doesn't get recovered through a complaint. Second: since this is an international platform, your protection doesn't come from a local regulator, it comes from how you keep your own file. That's why what actually helps most isn't a better-written complaint, it's prevention: verify when you open the account, always cash out through the route you deposited with, understand the bonus before accepting it, and keep screenshots of every transaction. With that, most readers of this page will never need it.
It's worth worrying when the published timeframe is clearly exceeded, your details are correct, and support has stopped moving forward; up to that point, what's running is process.
Frequently asked questions
Why is my withdrawal still in review?
Internal review confirms your file is complete, the destination is in your name, there's no pending bonus condition, and the balance is enough. If something's missing, the request sits there. Check the status of your documents and your promotions before assuming a block, and count the non-business days: a request over a weekend starts once the banking system reopens.
Why was my withdrawal request cancelled and the money returned to my balance?
The most frequent cause is that the payout details didn't match: an account in someone else's name, a CLABE with a changed digit, a closed account, or a card that already expired. It also happens when the method chosen isn't the same one you deposited with. Fix exactly that cause and request again just once, without opening parallel requests.
Can I withdraw if I accepted a bonus?
Depends on the condition the promotion carried, usually a traded-volume requirement. Until it's met, the part of the balance tied to the bonus isn't withdrawable, and sometimes the whole request gets stuck. Check the promotion's terms on your account; if you're not going to meet the condition, find out how to decline the bonus before requesting the payout again.
Should I request a chargeback from my bank if the withdrawal doesn't arrive?
Not as a first move. A chargeback opened while the withdrawal is in process can freeze your account on the platform and stop the very payment you wanted to collect. First fix what's on you, open a ticket with a folio and screenshots, and ask for escalation if the thread stalls. A chargeback is a last-resort tool, not a first attempt.
What should I include in a ticket to get it resolved faster?
The email you signed up with, the request's folio, the date and time, the amount, the method, the payout details as you entered them, and a clear sentence about what you expected and what happened. Attach screenshots of the status and, if the money didn't arrive, the period's bank statement. Write in a single thread: duplicate tickets split your case and slow it down.
Does a held withdrawal mean the platform has no intention of paying?
Almost never. The patterns point to process problems with a specific cause: incomplete verification, a mismatched name, a method different from the deposit one, or an open bonus condition. A case that really deserves formal escalation is recognised by several signals together: the published timeframe clearly exceeded, your details correct, and support that has stopped moving forward despite the evidence.