The question that decides what the FAQ is worth
A player lands on Runebanks' FAQ page because something about their money, their account, or a game rule is unclear. The first decision is not which answer to read. It is whether the answer on that page can bind the operator at all. An FAQ is a convenience layer. It restates, in plainer words, rules that live somewhere else and are enforceable only there. A sentence in an FAQ has no independent force. If the FAQ and the terms page conflict, the terms page wins, because it is the document the player accepted and the one the operator will cite in a dispute. The reader who treats the FAQ as the final word has read a summary and mistaken it for a contract.
That does not make the FAQ useless. It makes it a map. The useful question is never "what does the FAQ say" but "which document does this FAQ answer point to, and does that document state the figure or condition I need". Runebanks' FAQ, like every operator FAQ, is best read with one eye on the answer and one eye on the source the answer names.
What an FAQ can answer bindingly
An operator FAQ is strongest on process. Process questions have answers that do not change from one account to the next and do not depend on a current promotion. The FAQ can state which documents the verification team commonly asks for, because the list of acceptable document types is a fixed procedure, not a figure. It can state the order in which a withdrawal moves through review, approval and release, because that sequence is the same for every player even when the time each stage takes is not. It can state which payment routes are available for deposits and which for withdrawals, because a route either exists on the cashier screen or it does not.
Those answers are binding in a limited sense. They bind the reader's expectations, not the operator's obligations. When the FAQ says a utility bill is an accepted proof of address, the player can reasonably submit one. When the FAQ says withdrawals are reviewed before release, the player can reasonably expect a review step. What the FAQ cannot do is turn "commonly accepted" into "must be accepted for this account" or "reviewed before release" into "released within a stated number of hours". The binding version of every process answer is the account screen, the cashier, or the terms page that the FAQ paraphrases.
What an FAQ cannot answer at all
The line an FAQ cannot cross is the line between a rule and an account state. A rule applies to everyone: a wagering requirement is a condition on withdrawing bonus winnings, KYC documents are required before a first withdrawal, a self-exclusion cannot be lifted on request. Those are writable in an FAQ because they do not depend on who is reading.
An account state depends on who is reading, and no FAQ can know it. Whether this player's documents have passed, whether this withdrawal is inside the review queue or held for a missing document, whether this bonus is still active or has expired, whether this deposit method is available to this account in this country, whether this player has self-excluded and for how long: none of that is an FAQ question. The FAQ can say that a held withdrawal is usually held for one of a small list of reasons. It cannot say which reason applies to this reader. The answer that matters is on the account screen, in the cashier, in the verification email, or from support, and the FAQ's only honest job on those questions is to tell the reader where to look.
The same line separates the FAQ from the terms. A bonus percentage, a wagering multiple, a minimum deposit, a maximum withdrawal, a fee: those are figures, and figures live in the terms and promotions pages, not in a summary of them. An FAQ that repeats a figure is repeating something it does not control. The reader who copies a number from an FAQ and relies on it later has relied on a paraphrase. The reader who follows the FAQ's pointer to the terms page and reads the number there has read the binding source.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Document lists are revised as compliance requirements change | Verification or KYC page, and the document request email |
| Withdrawal review order | Process steps are stable, but the time each takes is not | Withdrawal policy page and the cashier status screen |
| Deposit and withdrawal routes | Methods are added and removed by region and by payment provider | Cashier screen at the moment of the transaction |
| Bonus percentage and wagering multiple | Promotions change frequently and apply per campaign | Promotions terms page for the specific bonus |
| Withdrawal minimum and maximum | Limits are revised and may differ by method and player level | Withdrawal policy page and the cashier |
| Self-exclusion and cooling-off rules | Responsible gambling tools are governed by policy, not FAQ | Responsible gambling page and account settings |
| Account status and held withdrawals | Specific to the reader's account and cannot be in an FAQ | Account screen, support ticket, or verification email |
Where the binding answer lives
For every FAQ topic, there is a document or screen that carries the enforceable version. The reader's job is to identify it and read it there. For anything about money movement, the binding source is the withdrawal policy page and the cashier screen at the moment of the transaction. The cashier is the only place that shows the methods available to this account right now, and the only place that states the limits and fees that apply to this transaction. An FAQ that lists methods is a snapshot; the cashier is the live system.
For anything about bonuses, the binding source is the promotions terms page for the specific campaign. A welcome bonus and a reload bonus have different terms, and the FAQ cannot carry all of them without becoming the terms page itself. The reader who wants to know what a bonus costs to withdraw reads the wagering requirement on that bonus's own terms page, not the FAQ's summary of how wagering works in general.
For anything about verification, the binding source is the document request itself. The email or account notification that asks for documents states which documents, in which format, by which deadline. The FAQ can prepare the reader for what is commonly asked; it cannot substitute for the actual request. For anything about account status, the binding source is the account screen and, where the screen is silent, support. No FAQ answer can tell a reader whether their own account is restricted, under review, or in good standing.
Reading the FAQ as a decision tool
The practical way to use Runebanks' FAQ is to treat each answer as having two parts: the explanation and the pointer. The explanation tells the reader what category their question falls into. The pointer tells them where the answer that binds lives. A good FAQ answer does both. A bad one does only the first, leaving the reader with a general explanation and no route to the specific answer.
When the FAQ does not state a figure, that absence is not a defect. It is the FAQ doing its job. Figures belong in documents that are versioned, dated, and accepted by the player. An FAQ that refuses to state a number is an FAQ that knows where numbers live. The reader who finds no minimum withdrawal in the FAQ should not conclude that no minimum exists. They should conclude that the minimum is stated on the withdrawal policy page, and that the FAQ has correctly declined to paraphrase it.
The same logic applies to anything the FAQ says about timing. A sentence like "withdrawals are processed after verification" is a process statement and is safe. A sentence like "withdrawals take two days" is a figure and is not safe, because the operator will not be held to a paraphrase in the FAQ. Across operators, withdrawal processing commonly ranges anywhere from a few hours to several business days depending on method, verification status and the operator's own queue, but the only number that matters to this reader is the one on their own withdrawal screen.
What changes and what stays fixed
FAQ pages change less often than promotions pages and more often than terms pages. Process answers are stable for long periods: the broad shape of verification, the order of withdrawal review, the existence of a responsible gambling page. What changes are the specifics that sit underneath those processes: which documents are currently accepted, which payment methods are currently offered, which limits currently apply, which bonus campaigns are currently live.
The reader who bookmarks an FAQ answer about payment methods is bookmarking a snapshot. The reader who bookmarks the cashier screen is bookmarking the live system. The distinction matters most when money is moving. A deposit method that worked last month may not appear this month, and the FAQ will not have been updated the moment it disappeared. The cashier will have. The same holds for withdrawal routes: the FAQ can say that not every deposit method has a matching withdrawal route, but only the cashier can show which routes exist for this account today.
Terms pages carry version dates and sometimes a "last updated" line. FAQ pages often do not. That is another reason the FAQ is a poor place to read a figure: the reader cannot tell whether the number they are reading is the current one or a leftover from a previous version. The terms page can usually be dated. The FAQ usually cannot. Where a figure matters, read it from the document that can be dated.
FAQ
Can I rely on the Runebanks FAQ if it conflicts with the terms page?
No. The terms page is the document the player accepted and the one the operator will cite in a dispute. The FAQ is a summary and has no independent force. Where the two conflict, read the terms page as binding and treat the FAQ as outdated or simplified.
Why does the FAQ not state the minimum withdrawal amount?
Because figures belong in versioned documents, not in summaries. The minimum withdrawal is stated on the withdrawal policy page and in the cashier, where it applies to the specific transaction. An FAQ that omits a figure is correctly pointing the reader to the binding source.
How do I know which documents to send for verification?
The document request itself is the binding source. It states which documents, in which format, and by which deadline. The FAQ can tell you what is commonly asked across operators, but only the request sent to your account tells you what is required of you.
Does the FAQ tell me why my withdrawal is held?
It can tell you the common reasons a withdrawal is held, but not which reason applies to your account. That answer is on the account screen, in the cashier status, or in a support reply. The FAQ's job on that question is to point you there.
This page is an independent summary of what an operator FAQ covers and where it stops, it is not published by Runebanks, and it states no figure or status for them; Runebanks' own FAQ and the documents it points to are the only binding sources.
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.
