Seven stages, seven different owners

1. 01

   Request submitted owner: you

   A withdrawal request is a live instruction with rules attached: a minimum amount, an allowed destination, sometimes a requirement that the destination match the account name or the payment method you used. A request that breaks one of those rules can be rejected rather than queued, so it is worth reading the operator's withdrawal rules once, before you need them.

   Your action: save the reference you are shown, right then, along with the amount and the time.

2. 02

   Account verification owner: operator

   Identity checks are attached to money leaving an account more often than to money arriving. If your documents are missing, expired, or the name on them does not match the account, the request typically stops here rather than being quietly processed. Details are on the verification page.

   Your action: submit the requested documents once, in full, at the quality asked for, and keep unexpired copies somewhere you can reach them.

3. 03

   Operator review owner: operator

   An internal check of the account and the request — commonly described as anti-fraud or AML review. It is the stage least visible from outside, because nothing is being sent and nothing is being asked of you. It is also the stage where support can see something you cannot.

   Your action: ask one specific question with your reference — which stage the request is in — rather than asking for an estimate.

4. 04

   Queued for the payment rail owner: operator

   The request has been approved but is waiting for the chosen method: a crypto destination, a card, an e-wallet or a bank transfer. Queues, cut-off times, weekends and public holidays live here, and a bank rail can add a handling step downstream that the operator never sees.

   Your action: confirm the destination details are exactly right. A correctly-formed request at this stage will not speed up, but a malformed one will come back.

5. 05

   Sent or broadcast owner: operator

   The operator's part is finished: for an on-chain transfer this is the broadcast of a transaction, and it is the moment the transfer becomes irreversible. Dashboards usually relabel the request as "completed", "sent" or "paid" here, which is the label most often misread as "the money is in my bank".

   Your action: for an on-chain transfer, capture the transaction hash; for a bank rail, capture the evidence the operator gives you that it submitted the payment.

6. 06

   Network or banking confirmation owner: third party

   Now it is out of the operator's hands entirely. A blockchain transfer needs its confirmations, and the number of them is a property of the chain and of the receiving service. A bank transfer depends on sender and receiver banks, cut-off times and, for cross-border payments, intermediary banks.

   Your action: verify independently rather than asking the operator to hurry a network: a block explorer for a chain, your own bank statement or app for a fiat rail.

7. 07

   Credited and settled owner: your bank / wallet

   The funds appear, and if a fee or a conversion applied you can now see exactly what was taken and by whom. Compare the amount received against the amount requested and against the operator's stated fee — this is the only point where you can see all three costs at once.

   Your action: if the amount is short of the operator's own stated fee, that is a concrete question with numbers attached. That is a far stronger support ticket than a delay.

Disclosure: this page carries an affiliate link to gamdom.com/r/csgo2026. If you open an account through it we may earn a commission. It costs you nothing extra and it does not change what we write. 18+. Gambling can cause serious financial harm — never stake money you cannot afford to lose. Nothing here is advice about where to play, and no processing time is promised by anyone.