Withdrawal Rejections and Declined Requests

What a rejection means

Declined is a status, not a verdict. It means the request as submitted cannot be released, and it is almost always accompanied by a reason that tells you exactly what to change.

The word does more emotional damage than the situation warrants. In payments, a declined transaction is routine — cards decline for insufficient balance a million times a day and nobody reads it as an accusation. The same is true here, and the productive response is the same: read the reason, fix the thing, try again.

Declined versus delayed

These behave completely differently and get conflated constantly. A delayed request is in a queue and will resolve on its own, given the published window of three business days extendable to fourteen. A declined request will not resolve on its own, ever, because something about it is blocking release. Waiting on a decline is the single most common wasted week in this whole process.

A fixable status

Almost every decline names a condition that is within your control: complete a document, use a different method, satisfy a bonus condition, close an open position, adjust the amount. The exceptions are rare enough that assuming your case is one of them is usually wrong. Treat it as fixable first and escalate only when the reason given makes no sense against your account.

Why it is not a ban

• A declined request does not restrict the account.
• The funds stay in the balance and remain yours.
• You can submit a new request as soon as the cause is addressed.
• A decline for one method does not block the others.

What a decline does cost you is time, and the time is spent twice if you resubmit the identical request without changing anything. That happens more often than it should, usually because the reason was skimmed rather than read.

The rest of this page walks through the causes in the order they occur in practice, with the fix for each. Working through them in that order finds the answer for the overwhelming majority of declined requests within a few minutes.

One framing helps more than any individual fix. A withdrawal request is a set of assertions: that you are the verified account holder, that this destination belongs to you, that this money is free to move, and that the amount fits the method. A decline is the system telling you which assertion it could not confirm. Approached that way, the message stops reading as a judgement and starts reading as a checklist with one item ticked in the wrong box.

It is also worth saying plainly what a decline is not. It is not a sign that the platform has run out of money, it is not a preliminary to an account closure, and it is not something support has decided about you personally. The overwhelming majority are produced by automated checks against published rules, and the person who eventually reads your ticket will be looking at the same rule you can read yourself.

A decline is a named condition rather than a refusal, and resubmitting without addressing the condition simply repeats it.

Verification-related declines

The largest single group. Either documents were never submitted, or they were submitted and something about them did not line up with the account.

The AML policy states that verification is carried out when the company requests it, and that full name and address verification is required for bank-transfer flows. The public offer adds that the client is obliged to provide identification and address documents and to comply with any other verification steps the company determines. A payout that meets one of those requirements for the first time is not being obstructed; it is being asked.

Incomplete KYC

The simplest case and the easiest to fix. Documents have been requested and not supplied, or supplied partially. The request will not move until the set is complete. Sending everything at once, at good image quality, is faster than sending items one at a time and waiting for each to be assessed.

Document mismatch

Subtler and more frustrating. The documents are genuine but something disagrees with the account: a middle name present in one place and absent in the other, a surname transliterated two ways, an address that has changed since registration, a date of birth entered with the day and month reversed. The fix is documentary — make the two sides agree — rather than explanatory.

Pending review

Sometimes the decline is really a hold: documents are in review and the withdrawal cannot be released until they clear. This looks identical to a rejection from the outside, and the distinguishing feature is whether the message asks for something new or simply reports a status.

• Read whether the message asks for a document or reports a state.
• Correct account profile details before resubmitting documents.
• Send one complete, high-quality set rather than several partial ones.
• Keep a copy of everything you sent and the date you sent it.
• Never pay anyone to accelerate a verification — no legitimate fee exists.

Once verification is complete it serves every future withdrawal, which is why this category of decline is overwhelmingly a first-payout phenomenon and rarely appears again.

The timing of the request matters as much as its content. Submitting a withdrawal while documents are still in review does not put you further forward in the queue; it creates a request that is waiting on a process that is itself waiting. Letting verification finish first, then requesting, is faster in practice even though it feels slower, because the second step does not have to be assessed twice.

Where documents have been rejected more than once, resist the temptation to send progressively more material. Sending five documents when two were asked for makes the review longer rather than shorter, and it increases the chance that something in the extra material raises a new question. Send exactly what was named, at the best quality you can manage, and add a short note only where a genuine complication needs explaining.

Verification declines are a first-payout problem, and completing documents once removes the whole category permanently.

Method and bonus declines

The second group covers two rules that are set long before the withdrawal: where money is allowed to go, and what conditions were attached when it arrived.

Both are decided at deposit time, which is why both feel like ambushes when they surface at withdrawal time. Neither is negotiable after the fact.

Wrong payout method

The payment policy states that withdrawals, refunds and compensation can only be made using the same account or card used for the deposit, and only in the deposit currency. Requesting a payout to a method that did not fund the balance is therefore refused as a matter of course. Where the original method is really closed, an alternative has to be approved by the operator, which involves evidence that the original is unusable and that the new one belongs to you.

Active bonus lock

Where a bonus was accepted at deposit, the conditions written into that offer's own terms apply to the balance it attaches to. Until those conditions are satisfied, the affected portion is not free to leave, and a request covering it will be declined. This is a condition rather than a confiscation, and it was agreed to at the moment the bonus was accepted.

Unmet turnover

The most common shape a bonus condition takes is a trading-volume requirement: a certain amount of trading has to happen before the bonus-linked funds unlock. The operator does not publish a general multiplier, because the figure belongs to whichever offer you accepted, so the only accurate source is the terms of that specific promotion.

• Deposit using the method you want to be paid on, and the first rule never bites.
• Read bonus terms before accepting, or decline the bonus entirely.
• Ask support whether an active bonus can be removed if you no longer want it.
• Check whether the decline covers the whole balance or only the bonus-linked part.

Traders who never accept a bonus and never deposit on a method they cannot receive on eliminate this entire section from their experience of the platform. It is the cheapest insurance available here.

The bonus case deserves a fair hearing rather than a warning label. A deposit bonus is not a trap and it is not free money; it is a commercial offer with conditions, in the same way a bank's introductory rate has conditions. Accepting it is a reasonable decision for a trader who has read the terms and expects to meet them, and an unreasonable one for a trader who has not read them and simply wanted the larger balance. The problem is almost never the bonus itself. It is accepting one without knowing what was attached.

If a bonus is already active and you would rather it were not, ask support before trading further, since the answer depends on that offer's own terms rather than on a general policy. Trading through a condition you did not want, or trying to withdraw around it, both take longer than a single question asked early.

Method and bonus declines were both decided at the deposit screen, so the fix belongs there rather than at the payout.

Account-state declines

The third group is about the balance itself: whether the money you are trying to move is actually free, and whether anything about the account has attracted a manual look.

These are usually the quickest to resolve because they are visible in your own account without waiting for anyone to answer a ticket.

Open trades pending

Funds committed to open positions are not available to withdraw. A trader looking at a total balance and requesting all of it will be declined for a shortfall they cannot see, because the figure they are reading includes money that is currently in the market. Close positions, or request only the free portion.

Insufficient free balance

The same problem in a slightly different shape. Between the amount committed to trades, any bonus-linked portion and the method's own minimum and maximum, the actually withdrawable figure can be well below the headline number. The cashier applies all of these at once, which is why a request can be declined for an amount the account appears to hold.

Flagged activity

Payments businesses screen outgoing transactions, and unusual patterns attract a manual review. A first payout to a brand-new destination, a sudden change of method, a login from an unfamiliar location shortly before a large request — none are accusations and all can add a step. The way through is to be ordinary: same account, same method, same person, over time.

• Check the free balance rather than the total before requesting.
• Close or account for open positions first.
• Keep the amount inside the method's displayed floor and ceiling.
• Avoid changing destination and amount dramatically in the same request.
• Respond promptly to any question raised, since a flagged review waits on you.

A pattern worth avoiding entirely: cancelling and resubmitting a request repeatedly in quick succession. It does not speed anything up, and a burst of identical requests looks precisely like the behaviour anti-fraud screening exists to notice.

Where an account has actually been flagged for review, the useful response is patience plus responsiveness rather than volume. Answer whatever is asked promptly and completely, do not open several parallel tickets about the same request, and avoid making further changes to the account while the review is running. A review that has all the information it needs finishes; a review that is chasing a moving target does not.

Withdraw the free balance, not the headline balance, and let a flagged review finish rather than resubmitting into it.

Turning a decline around

The route back is short when it is taken in the right order: identify the stated cause, fix only that, resubmit once, and escalate only if the reason does not match your account.

Most of the time lost to declined withdrawals is lost to doing these steps out of order — resubmitting before fixing, or escalating before reading.

Fixing the root cause

1. Read the decline message word for word and write down what it actually names.
2. Check the obvious account-state items: free balance, open positions, bonus status.
3. Check the method: is it the one that funded the deposit, and is it still valid?
4. Check verification: is anything outstanding, and does the profile match the documents?
5. Fix the single thing identified, then confirm the fix has registered before resubmitting.

Resubmitting correctly

Submit one corrected request rather than several attempts in quick succession. If the decline was about verification, wait for the documents to be accepted before requesting again, since a payout submitted into a pending document review simply queues behind it. Keep the reference for the new request separately from the old one.

Escalating to support

Escalate when the stated reason does not match anything true about your account, when no reason was given at all, or when a corrected resubmission is declined for the same cause. Make the first message complete: request reference, method, amount, submission date, the exact decline text, and what you changed. Support cannot act on "my withdrawal was declined", and a complete first message frequently resolves in one reply what an incomplete one takes four exchanges to resolve.

• Quote the decline message exactly rather than paraphrasing it.
• Attach evidence of the fix you made.
• Ask a specific question rather than expressing general frustration.
• Keep the exchange in one thread so the history stays readable.

Almost none of this is needed by an account that verified early, deposited on the method it wants to be paid on, and declined bonuses it had not read. Registration is free and verification can be completed before any deposit, which is where this whole page is best solved.

One habit is worth adopting whatever your history with the platform: run a small withdrawal early, through the whole cycle, while the amount is too small to matter. It surfaces every one of the conditions on this page at a moment when none of them are stressful, and it converts the first real payout from an experiment into a repeat of something that already worked. Traders who do this rarely appear in complaint threads, not because they were lucky, but because they met every condition on a day when meeting it cost them nothing at all.

Fix one named cause, resubmit once, and escalate with a complete message only when the reason does not fit your account.