Withdrawal statuses and queues
A payout is the one part of the cashier where waiting is unavoidable and the one part where the reason for waiting is invisible. This page decodes the statuses a request passes through and separates the time spent inside the operator from the time spent outside it. Channel-by-channel timings sit on the payments overview.
Open an account on the operator's siteWhat each status means
| Status | Where the money sits | Who can act |
|---|---|---|
| Pending | Deducted from the balance, still inside the operator | The player can usually cancel |
| Under review | In the finance queue | The operator; a document may be requested |
| Approved | Handed to the payment provider | Cancellation is no longer possible |
| Sent | Moving through a bank or a blockchain | The bank, traced by reference or hash |
The misunderstanding almost always lives between the last two rows. Once a request is marked sent, the operator's part is finished and the remaining wait belongs to somebody else entirely.
Approval time and travel time
Total duration is approval plus movement. Approval is human or automated review running on the operator's working rhythm; movement is the rail's own speed and starts only when approval lands. An approval granted at five on a Friday afternoon leaves a bank transfer motionless until Monday, even though the review itself took three minutes. The same approval pointed at a wallet arrives that evening. The rail cannot shorten the review, and the review cannot shorten the rail.
Cut-offs and the Estonian calendar
Banks clear in rounds and every round opens at a fixed time. An instruction arriving after the last cut-off joins the following day's batch. Weekends are not banking days, and national holidays — Midsummer, Christmas, New Year, Independence Day — remove further days from the calendar, which is why a long holiday weekend can double an expected wait. Instant SEPA is the exception that runs continuously, provided both banks support it and the amount fits inside the instant ceiling. A blockchain has no calendar at all; only its confirmation count matters.
The first request
A first payout is slower because three things happen once and never again. Identity is confirmed through ID-kaart, Mobiil-ID or Smart-ID. The channel used is bound to the account holder so funds cannot travel to a stranger. And the request is reviewed manually. A larger sum adds a fourth step: proof of the source of funds, typically a payslip or a bank statement. Those files go to the operator's own account area, never to this portal.
Why a large sum arrives in parts
When an amount exceeds the per-transaction ceiling, it is paid across consecutive cycles. That is ordinary cashier configuration rather than obstruction, and knowing it in advance turns an unpleasant surprise into a plan. The opposite habit costs time too: ten small requests each pass their own review, so they take collectively longer than one consolidated payout.
The same-channel rule and its one exception
Money returns the way it came. A deposit made through a bank link pays out to the bank account; a wallet deposit pays back to the wallet. The exception is the prepaid voucher — Paysafecard only works inbound, so a second channel has to be attached to the account before there is anything to withdraw. Attaching it at signup rather than on the day of a win is the whole trick.
When the wait stretches
One complete message beats five short ones. Include the date and time of the request, the amount, the channel, the current status and the payment reference or transaction hash. If the status is pending or under review, the question belongs to the operator; if it is approved or sent, ask the bank in parallel. The full message template is on the support page, and the formal route if answers go nowhere is described under complaints.