The moment a withdrawal request stops being a balance
A withdrawal policy exists because the moment a player presses the cash-out button, the money changes legal character. Before that click it is an account balance, an entry the operator controls. After it, the same amount is a liability: a promise to move real funds to an outside instrument. The policy is the document that governs the space between those two states. A reader who treats it as a schedule of promises usually misreads it. A reader who treats it as a sequence of gates reads it correctly.
Runebanks publishes its withdrawal and refund terms as a single policy page. That page is the only place the operator's own conditions are binding. Everything else a player hears about how fast money moves, or what it costs, or how much must remain in the account, is noise until it matches the text on that page. The reader's first job is therefore not to remember figures. It is to identify which stage of the process each figure attaches to.
The four stages every withdrawal passes through
Across operators, a withdrawal moves through four distinct stages, and each stage has its own owner. A delay in one stage is not evidence about another. The stages are:
| Stage | What happens | Who controls the clock |
|---|---|---|
| Request and account check | The operator confirms the request is genuine, the account is in good standing, and any verification documents already on file still match the withdrawal method. | The operator |
| Pending and reversal window | The amount is frozen in the account and shown as pending. During this window the player can usually cancel the request and return the funds to their playable balance. | The operator, and the player's own decision to reverse |
| Release and transmission | The operator marks the withdrawal as processed and hands the funds to the payment provider named on the request. | The operator, then the payment provider |
| Provider settlement | The payment provider clears the funds into the player's external instrument. This stage is outside the operator's system entirely. | The payment provider, the receiving bank or wallet |
The distinction that matters most is between the third and fourth rows. A player who sees a withdrawal marked as processed and then waits several days is not waiting on Runebanks. The operator's own policy page typically states that once funds are released, the operator's part is complete. The remaining delay belongs to the payment provider's settlement cycle, which the operator cannot shorten. Reading the policy with this table in mind prevents the most common misattribution of blame.
What the pending window is
The pending window is the most misunderstood part of any withdrawal policy. It is not a processing delay. It is a deliberate holding period during which the request can still be undone. The policy page describes it because it changes what the player can do with the money. While a withdrawal is pending, the amount is neither fully in the account nor fully gone. It is frozen, visible, and reversible.
The reversal option is the key mechanic. A player who reverses a pending withdrawal puts the entire amount back into their playable balance. Nothing is lost except the time spent waiting. But the policy usually states that once the pending window closes and the withdrawal moves to the released stage, reversal is no longer possible. The funds are committed to the payment provider. The reader should look on the Runebanks policy page for the exact point at which the reversal option disappears, because that is the point of no return.
Why does the window exist at all? Because operators use it as a cooling-off mechanism. It reduces the number of chargebacks and payment disputes, and it gives the player a chance to reconsider. It is not a trick, but it is also not neutral: a player who reverses a withdrawal has, in effect, decided to keep playing with money they had already chosen to remove. The policy states the window because the player's control over the request ends when the window ends.
Why the operator stage and the provider stage are different
An operator cannot move money instantly, and a payment provider cannot move money before the operator releases it. The two stages are governed by different clocks, different rules, and different documents. The withdrawal policy governs only the operator's stage. The payment provider's terms govern the rest.
This matters in three practical ways. First, a delay before the status changes from pending to processed is an operator-side matter. The policy page is the place to look for what the operator promises at that stage, and for what it does not promise. Second, a delay after the status changes to processed is a provider-side matter. The operator's policy typically disclaims control over that stage, and the reader should not expect the policy to fix it. Third, a withdrawal that fails at the provider stage is usually returned to the operator, not to the player's external account. The policy page states what happens to returned funds: whether they go back to the playable balance, whether a new request must be submitted, and whether any fee applies.
The reader who keeps these two stages separate will stop asking the operator for answers the operator cannot give, and will start asking the payment provider for answers the operator is not responsible for.
Fees, minimums and the items that change most often
Withdrawal policies are among the most frequently edited documents an operator publishes. The reason is that the figures on them are tied to external contracts: payment provider fees, currency conversion spreads, and minimum transaction thresholds all move when the operator renegotiates with a provider or when a provider changes its own schedule. A fee or minimum read today may not be the fee or minimum in force next month.
The reader should therefore treat every figure on the policy page as perishable. The page itself is the only current source. The items that commonly change, and that the reader should re-check before each withdrawal, are:
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Withdrawal fee per request | Provider fees are renegotiated; the operator may absorb or pass them through differently over time. | On the withdrawal policy page, usually in a fees section or a table of charges |
| Minimum withdrawal amount | Payment providers set their own minimum transaction sizes, and those change. | On the policy page, often near the top of the withdrawal terms |
| Maximum withdrawal per period | Operators adjust caps based on risk and liquidity; a monthly cap may not match a weekly cap. | On the policy page, in a limits section |
| Currency conversion rate | Exchange rates move continuously; the policy states which rate applies and when. | On the policy page, in a currency or conversion clause |
| Verification documents required | Regulatory pressure and fraud patterns change what the operator asks for before a first withdrawal. | On the policy page, in a verification or KYC section |
| Reversal window length | The operator may shorten or lengthen the pending period; the current window is stated on the page. | On the policy page, in the pending or cancellation section |
If the policy page does not state one of these items, that absence is itself an answer. A reader who cannot find a fee schedule should not assume the withdrawal is free. A reader who cannot find a minimum should not assume any amount can be withdrawn. The correct move is to ask support before submitting the request, or to treat the absence as a reason to withdraw a smaller test amount first.
Why unused bonus balance is normally not a refundable asset
The refund section of a withdrawal policy exists to answer one question: under what circumstances does the operator return money to a player? The answer almost always excludes one category: unused bonus balance. The reason is mechanical, not punitive.
A bonus balance is not money the player deposited. It is a conditional credit the operator issued. It exists only while the conditions attached to it are unmet. Those conditions are typically a wagering requirement: the bonus amount must be turned over a stated number of times before it converts into withdrawable cash. Until that happens, the bonus is a bookkeeping entry, not an asset. If a player asks for a refund of unused bonus balance, they are asking the operator to convert a conditional credit into unconditional cash without the condition being met. No withdrawal policy grants that, because doing so would make the wagering requirement meaningless.
The policy page states this in one of two ways. Either it says explicitly that bonus balances are non-refundable, or it says that only the withdrawable balance is eligible for withdrawal, which amounts to the same thing. The reader should look for the distinction between withdrawable balance and bonus balance on the Runebanks policy page. The two are presented separately in the account, and the policy governs only the first.
There is one partial exception worth understanding. If a player deposits real money and receives a bonus, then loses the deposit while the bonus remains, the bonus is still not refundable. But if the player has not yet wagered the deposit at all, some policies allow the deposit itself to be withdrawn, with the bonus forfeited. That is a refund of the player's own money, not of the bonus. The policy page states whether this is possible and what happens to the bonus when it is forfeited.
What the refund section covers
The refund section of a withdrawal policy is narrower than most players expect. It does not promise refunds on demand. It describes the limited circumstances in which the operator will return funds that were already committed. The typical categories are:
| Refund trigger | What it means in practice | Where the policy states it |
|---|---|---|
| Failed provider settlement | The payment provider returns the funds to the operator; the operator credits them back to the player's account. | In the refund or failed transaction section |
| Duplicate charge | The player was charged twice for one deposit; the operator returns the duplicate. | In the refund or deposit error section |
| Account closure with withdrawable balance | If the operator closes an account, any withdrawable balance is returned after verification. | In the account closure or refund section |
| Technical error on the operator's side | A game or cashier error credited or debited the wrong amount; the operator corrects it. | In the errors or disputes section |
Anything outside these categories is generally not a refund. A player who loses money on a game is not owed a refund. A player who changes their mind about a deposit is not owed a refund. A player who fails to meet a wagering requirement is not owed the bonus. The policy page exists partly to make these exclusions explicit, so the reader should read the exclusions as carefully as the inclusions.
Reading the policy before the first withdrawal
The worst time to read a withdrawal policy is after a withdrawal has gone wrong. By then the reader is already inside the process, and every clause reads as an obstacle. The right time is before the first request, when the reader can still choose the withdrawal method, the amount, and the timing.
The practical reading order is: first, the verification requirements, because those block everything else. Second, the fee and minimum sections, because those decide whether the withdrawal is worth making at all. Third, the pending and reversal window, because that decides when the money is truly committed. Fourth, the refund section, because that decides what happens if the provider fails. A reader who works through the page in that order will know, before pressing the button, exactly which stage will take how long, which stage is outside the operator's control, and what the policy does and does not promise.
If the Runebanks policy page does not state a verification requirement, a fee, a minimum, or a reversal window, the reader should not fill in the gap from memory or from another operator's page. The absence is the answer: that item is not governed by the policy, and the reader should ask support before committing funds.
FAQ
Does the withdrawal policy guarantee a payout time?
No. The policy governs the operator's own stage: the pending window, the release decision, and the conditions that must be met before release. Once funds are handed to the payment provider, the provider's settlement cycle takes over, and that is outside the operator's control. The reader should look for what the policy promises at the operator stage and treat everything after release as provider-dependent.
Can I cancel a withdrawal after it is processed?
Usually not. The reversal option exists during the pending window, before the status changes to processed. Once the operator releases the funds to the payment provider, the request is committed. The policy page states the exact point at which cancellation stops being available.
Why is my bonus balance not included in my withdrawable amount?
Because a bonus is a conditional credit, not deposited money. It converts to withdrawable cash only after the wagering requirement attached to it is met. Until then, the policy treats it as non-refundable. The withdrawable balance and the bonus balance are shown separately in the account, and only the first is eligible for withdrawal.
What happens if the payment provider fails to settle my withdrawal?
The funds are typically returned to the operator, which then credits them back to the player's account. The policy's refund section states the exact procedure: whether the player must submit a new request, whether any fee applies, and how long the return takes. The reader should look for the failed transaction clause.
This page is an independent summary of what a withdrawal and refund policy covers. It is not published by Runebanks, and it states no figures or statuses for the operator; the operator's own policy page is the only binding source for the terms that apply to any withdrawal.
Play responsibly
Gambling should be treated as paid entertainment, never as a way to earn income or recover losses. 1-800-MY-RESET (1-800-697-3738)
18+ or 21+ depending on where you are; follow the minimum age that applies to you.
This article is general information about how these mechanics work. It is not legal advice and not a recommendation to gamble or to use any particular operator. Availability and legality differ by jurisdiction — check the rules that apply where you are.
