Withdrawal Processing Times by Method

Two stages of every payout

Every withdrawal is reviewed by the operator and then settled by a payment rail. The two are run by different parties, quoted in different documents, and fail in completely different ways.

Almost every argument about payout speed dissolves once these are separated. A trader saying "it took two weeks" and a platform saying "we processed it in three days" can both be telling the truth, because they are describing different clocks. Working out which clock your request is on decides whether you should wait or act.

Broker review window

This is the stage the operator controls and the only one it quotes figures for. The public offer states that withdrawal request processing is executed within three business days, and that in certain cases the company reserves the right to extend the period up to fourteen business days. The payment policy adds that funds will be withdrawn from the client account within five business days.

Payment-rail settlement

Once released, the money is in somebody else's system. A blockchain confirms it in minutes. A card scheme passes it through an acquirer and your issuer over business days. The banking system moves a wire in a window the payment policy puts at three to forty-five business days. None of these are the operator's to compress, and no support ticket makes them shorter.

Why both add up

• The review window is the same regardless of which method you picked.
• The settlement window varies by more than an order of magnitude between rails.
• They run in sequence, so the total is the sum rather than the larger of the two.
• Business days on both sides exclude weekends and public holidays.

The practical use of this is diagnostic. If your rail settles in minutes and the money has not appeared, the request is still in review, and the answer is patience or documents. If your rail settles in business days, the payout can be released and invisible at the same time, and the answer is to check with the receiving institution rather than the platform.

Everything else on this page is an elaboration of those two paragraphs. The stages are the model; the numbers are the detail.

One further nuance is worth carrying with you. The two documents quote slightly different things: the public offer describes processing the request, and the payment policy describes funds leaving the client account. Those are adjacent steps rather than the same step, which is why the figures do not match exactly and why quoting either one alone gives an incomplete answer. Read them as the outer edge of the operator's side of the process — a request that has been with the operator for under five business days is inside what it has published, whatever the shorter figure suggested.

People also underestimate how much of the total is decided before the request exists. An account that verified in its first week, deposited on one method and has traded without accepting a bonus arrives at the withdrawal screen with nothing left to check. An account doing all of those things for the first time on the day it wants its money is asking a review queue to complete several processes at once. Same platform, same rules, wildly different experience, and the difference was set weeks earlier.

Work out which of the two clocks your payout is on before deciding whether it is late.

Fastest to slowest methods

Ranked by the settlement leg alone, crypto is fastest, wallets sit in the middle, and cards and wires trail. The review stage in front of them is identical whichever you choose.

Worth stating clearly before the ranking: the operator publishes no per-method settlement table. What follows describes the mechanics of each rail rather than a promised timetable, and the only figures quoted as official are the ones from the payment policy and the public offer.

Crypto leading the pack

A crypto payout is complete when the network confirms it. That process does not consult a calendar, so it runs identically at 3am on a Sunday and at 10am on a Tuesday. On a low-cost, high-throughput network confirmation is a matter of minutes; on a congested one it is longer and more expensive. This is the only rail where the second clock is in fact short.

E-wallets in the middle

A wallet credit has fewer hops than a card refund — often a single transfer from the operator's payment provider to your wallet account. That makes it noticeably faster than a card in practice. The complication is that wallet providers run their own compliance checks and can hold a credit after the broker has released it, particularly the first time and particularly for larger amounts.

Cards and wires trailing

Card refunds pass through an acquiring bank, a card scheme and your issuer, each on its own batch cycle, and the posting date you eventually see is set by your bank rather than by anyone else in the chain. Wires are slower still and carry the widest published band of any method. Neither is unreliable; both are simply built out of business days.

• Crypto: settlement in minutes to hours, no calendar dependency.
• Wallets: usually within a working day, subject to provider review.
• Cards: business days, entirely at your issuer's pace.
• Bank transfers: three to forty-five business days per the payment policy.

If speed is what you care about, the decision is made at deposit time rather than at withdrawal time, because the payment policy allows a payout only to the account that funded the balance.

That constraint is worth restating in speed terms, because it is where most disappointment starts. Depositing by card and then wanting a crypto-speed payout is not a choice the cashier will offer you; the refund goes back to the card, and only the part that is not a refund can take another approved route. Traders who care about timing therefore make their timing decision at the deposit screen. Everyone else makes it too, without noticing, and finds out later which one they picked.

There is also a difference between a rail being fast and a rail being predictable. Crypto is fast but its cost and confirmation time move with network conditions. Cards are slow but boringly consistent, which for some people is worth more than speed. Wallets are the compromise most ordinary traders settle on. None of these is the right answer for everyone, and the question worth asking is which failure mode you would rather live with rather than which number is smallest.

The rail you deposit on sets your settlement speed, so choose it for the payout rather than for the deposit.

What the review stage checks

Three things are examined before a payout is released: whether the account is verified, whether the request looks ordinary, and whether any bonus conditions are still attached to the balance.

These are the levers that actually move the first clock, and two of the three are entirely within your control before you ever submit a request.

Verification status

This is the big one. The AML policy describes verification as something the company requests, and states that full verification of name and address is required for bank-transfer deposits and withdrawals. An account whose documents were accepted weeks ago passes this check as a formality. An account being asked for a passport scan for the first time, in response to a withdrawal, is starting a document cycle in the middle of a payout.

Anti-fraud screening

Every payments business screens outgoing transactions, and unusual patterns attract attention. 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 of these are accusations, and all of them can add a manual look. The way to look ordinary is to be ordinary: same account, same method, same person, over time.

Bonus-condition checks

Where a bonus was accepted at deposit, the conditions in that offer's own terms apply to the balance it is attached to. Until they are satisfied, the affected portion is not free to leave. This is the most common cause of a payout that is refused rather than delayed, and it is entirely avoidable by declining bonuses you have not read.

• Verify before depositing, not in response to a withdrawal.
• Use the deposit method as the payout method.
• Read any bonus terms before accepting, or decline the bonus.
• Close open positions so the balance you are withdrawing is plainly free.
• Keep the account details consistent with your identity documents.

An account that satisfies all five is the simplest possible case in the queue, and it behaves that way. Most published complaints about slow payouts describe accounts that failed at least one.

It is worth being fair about why the review stage exists at all. A payments business that released every request without checks would be a laundering channel within a week, and the operators that skip these steps are not the trustworthy ones. The check that delays your first payout by two days is the same check that stops somebody funding an account with a stolen card and cashing out through it. Reading it as an obstacle rather than as a cost of doing business misreads what is happening.

What you can reasonably expect is proportionality. A routine payout on a verified account to a familiar destination should not require a fresh document round every time, and in practice it does not — the friction is concentrated in the first payout and thins out afterwards. If your third or fourth withdrawal to the same destination is still attracting new document requests, that is worth raising in a ticket, with the earlier request references attached so the pattern is visible to whoever reads it.

Verification, method matching and bonus status decide the review clock, and all three are settled before you click withdraw.

External delay factors

Some of the wait belongs to nobody in particular: calendars, volumes and banks. These are worth understanding precisely because there is nothing to be done about them except plan.

Anyone measuring a payout in calendar days will consistently reach a worse answer than the same payout measured in business days, and much of the frustration in this area comes from that arithmetic rather than from the process.

Weekends and holidays

Every documented figure is quoted in business days. Those exclude weekends and public holidays across the whole processing chain, and the calendars that apply are the ones observed by the operator and the banks rather than the one on your wall. A request submitted on a Friday evening before a public holiday can look completely static for four or five days while nothing at all has gone wrong.

Peak-volume periods

Review queues are staffed, and staffing is finite. Periods of unusual market activity produce more requests, more document submissions and more anti-fraud flags at the same time. The published extension to fourteen business days exists precisely so that the operator is not promising a three-day turnaround during a week when three days is not achievable.

Bank-side processing

On the settlement side, your own bank contributes delays nobody else can see. Inbound foreign credits attract checks. Some issuers hold refunds from merchant categories they view cautiously. Correspondent banks in a wire chain queue transfers on their own schedules. None of this is visible from the platform, and the platform cannot influence it.

• Count business days, not calendar days, from the moment of submission.
• Check whether the payout has been released before assuming it is stuck.
• Ask the receiving institution once the operator shows the money as sent.
• Expect the first credit from a new source to be checked more carefully.

None of these factors indicates a problem with the operator, and reading them as evidence of one is how ordinary processing gets reported online as misconduct.

A short worked example shows how quickly the arithmetic runs away. A request submitted at 8pm on a Friday has not started. Saturday and Sunday do not count. Monday is a public holiday somewhere in the chain. By the time three business days have elapsed, the calendar shows a week, and a trader counting calendar days has already concluded that something is wrong. Nothing is. The same request submitted on a Tuesday morning would have looked entirely unremarkable, and the process behaved identically in both cases.

The one external factor that does deserve attention rather than patience is a receiving institution that has silently held a credit and not told you. Banks and wallet providers do this, usually pending a routine question about the source of funds, and they do not always send a prominent notification. Where the operator shows the payout as sent and days have passed, a single call or message to the receiving side resolves more of these than any number of tickets to the platform.

Most unexplained waiting is calendars and banks, neither of which any support ticket can move.

Setting realistic expectations

The published bands describe a range, not a promise, and the shortest number in a range is the worst possible anchor for your expectations.

People plan against the figure they saw first, which is almost always the fastest one. Anchoring on the outer edge instead produces a calmer week and a much lower rate of unnecessary support tickets.

Quoted versus actual times

Planning around delays

The corollary is straightforward: do not withdraw money you need on a specific date at short notice. If a payment is due, start the payout well before it matters, or hold the funds somewhere they are already liquid. A payout is not a same-day instrument on any rail except crypto, and even crypto has the review stage in front of it.

When to follow up

• Under three business days: nothing has gone wrong; wait.
• Between three and fourteen business days: still inside the published extension.
• Past fourteen business days with no message: open a ticket with the reference.
• Marked as sent but not received: ask the receiving institution first.
• Status shows a condition: fix the condition rather than escalating.

When you do open a ticket, include the request reference, the method, the amount, the date and time of submission and the current status in the first message. Support cannot act on "my withdrawal is late", and a complete first message frequently resolves in one reply what an incomplete one takes four to resolve.

The best time to learn how long your particular setup takes is when the amount is small enough not to matter. Registration is free and verification can be finished before any deposit, so a small test payout early in the account's life costs almost nothing and calibrates everything that follows.

Anchor on the outer edge of the published bands and start any payout you actually need well before you need it.