The situation a FAQ page resolves
A player lands on an operator's FAQ because something has already gone sideways or is about to. A deposit has not appeared, a withdrawal is stuck at a status screen, a document was rejected, a bonus did not credit, or a game rule is unclear in the middle of a session. The reader is not shopping; the reader is mid-transaction and wants the shortest path from confusion back to a working account. That starting point changes what a FAQ can and cannot do, and it is the reason a careful reader treats the page as a map rather than as a contract.
The FAQ is the operator's self-service layer. It exists to absorb the questions that would otherwise fill a support queue: which documents are needed for verification, how a deposit route appears in the cashier, what a wagering requirement means in general, where a transaction history is displayed, how to close an account. Those are process questions. They have answers that hold for every reader, because they describe the machinery of the site rather than the state of one account.
What the FAQ cannot do is answer a question whose answer is a number that changes, or a decision that depends on the reader's own account. A FAQ written today cannot tell a reader tomorrow what the current withdrawal minimum is, because the operator can change that figure without rewriting the FAQ. It cannot tell a reader whether their specific withdrawal will be approved, because that depends on verification state, payment method, bonus history and risk review. The FAQ can say which factors are checked; it cannot say what the check will conclude.
What a FAQ binds, and what it merely points at
The useful distinction is between a rule and a route. A rule is a condition that governs money or account status: a wagering multiple, a maximum withdrawal, a verification threshold, a restricted-country list. A route is the path a reader follows to see the rule as it applies to them: the promotions page, the cashier, the account verification screen, the terms and conditions document. A well-built FAQ answers route questions in full and refuses to answer rule questions except by pointing at the document that owns them.
That division is not a defect. It is the only structure that keeps the FAQ honest. If the FAQ restated the wagering multiple, the reader would have two sources that could drift apart, and the FAQ would be the one that loses. If the FAQ restated a withdrawal maximum, a reader who relied on it would be relying on a page the operator does not treat as the binding record. The FAQ's authority is procedural, not contractual. The reader who understands that reads the FAQ for the how and the terms for the how much.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit methods and any per-method minimum | Payment routes are added and removed; minimums are adjusted by method and currency | The cashier or deposit page, at the moment of the deposit |
| Withdrawal minimum, maximum and any fee | Figures are revised without notice and may differ by method or account class | The withdrawal page or the withdrawal policy document |
| Verification documents required | The list is stable, but the trigger for requesting them depends on account activity | The account verification screen and any KYC or AML policy page |
| Wagering requirement for a bonus | Each promotion carries its own multiple, and promotions change frequently | The specific promotion's terms, not the FAQ |
| Processing time for a withdrawal | Depends on method, verification state and review; figures are indicative only | The withdrawal status screen for the specific request |
| Game rules and payout structures | Rules are fixed per game, but variants differ across tables and titles | The game's own rules panel or help screen |
Which questions the FAQ can answer bindingly
The binding part of a FAQ is the part that describes what the reader must do, in what order, and what the screen will show at each step. That content is binding because it is a description of the operator's own interface, and the interface is the same for every reader. If the FAQ says verification requires a government-issued photo ID, a proof of address and a proof of the payment method, that list is the list the upload screen will ask for. If the FAQ says a deposit made by a given method appears in the transaction history under a specific label, that label is what the reader will see.
Process answers are also the ones a reader can verify immediately. A reader who wants to know whether the FAQ is accurate does not need to trust it: they open the cashier and look. A reader who wants to know whether a withdrawal route exists opens the withdrawal screen and checks whether the method is listed. The FAQ's process claims are testable against the site itself, and that testability is what makes them safe to rely on.
The FAQ is also the right place for definitions that do not carry a figure. What a wagering requirement is, what KYC stands for, what a pending withdrawal status means, what self-exclusion does and does not do, what a session timeout is. These are stable concepts. The FAQ can define them without risk, because the definition does not change when the operator changes a number. The moment the definition would need a figure, the FAQ should stop and point.
Where the binding answer lives instead
For anything that carries a number, the binding source is the document or screen that owns that number. The promotions terms own the wagering multiple and the bonus expiry. The withdrawal policy owns the minimum, maximum and any fee. The cashier owns the available methods and their per-method limits. The AML or KYC policy owns the verification thresholds and the document list. The game rules panel owns the paytable and the rule variants. The FAQ is a signpost to all of these, not a substitute for any of them.
A reader who finds a figure in a FAQ should treat it as a snapshot that may already be stale. The operator's own terms pages typically carry a version date or a last-updated line, and the FAQ usually does not. Even when it does, the FAQ is not the document the operator's own disputes process will cite. When a withdrawal is declined or a bonus is voided, the support reply will quote the terms, not the FAQ. The reader who wants to know what will happen should read the same document support will quote.
There is one more source that outranks the FAQ for any question about a specific account: the account itself. The transaction history shows what happened to a deposit or withdrawal, with timestamps and statuses. The verification screen shows what has been submitted, what was accepted, and what is still outstanding. The bonus wallet shows what is locked, what is withdrawable, and what wagering remains. None of that is in the FAQ, because none of it is the same for two readers. The FAQ can tell a reader where to look; it cannot tell them what they will find.
What it means when the FAQ does not state an item
An absence in a FAQ is information, not a gap. If the FAQ does not state a withdrawal maximum, the reader cannot assume there is no maximum; the maximum, if one exists, lives in the withdrawal policy. If the FAQ does not name the payment methods, the reader cannot assume a method is available; the cashier is the only place the current list is shown. If the FAQ does not state a verification threshold, the reader cannot assume verification is never triggered; the AML policy is where the trigger is defined.
The same logic runs in reverse. If the FAQ does state a figure, the reader should still confirm it against the owning document before acting on it. A bonus decision made on a FAQ figure is a decision made on a page the operator will not treat as authoritative in a dispute. A withdrawal planned around a FAQ processing time is a plan built on an estimate that the operator's own withdrawal screen will refine the moment the request is submitted.
The reader's rule of thumb is simple: the FAQ tells you what to do and where to look; the owning document tells you what the number is; the account screen tells you what is true for you. Any question that can be answered by a stable process belongs in the FAQ. Any question whose answer is a figure, a status or a decision belongs somewhere else, and the FAQ's job is to say where.
How to read a FAQ without being misled
Read the FAQ as a directory first and as an explanation second. The first pass should identify, for each question the reader has, which owning document or screen the FAQ points to. The second pass should read the FAQ's process descriptions for the steps the reader will take. The third pass should open the owning document and read the figure there. Skipping the third pass is how a reader ends up with a number in their head that the operator never bound itself to.
When the FAQ and the terms disagree, the terms win. That is not a matter of which page is more recent; it is a matter of which page the operator's own disputes process treats as the record. A reader who quotes the FAQ in a support ticket will be redirected to the terms. A reader who quotes the terms will be answered on the terms. The FAQ is the operator's convenience layer; the terms are the operator's position.
For questions the FAQ does not cover at all, the reader's next step is the support channel, not a guess. The FAQ is not exhaustive, and its silence on a topic does not mean the topic does not exist. A missing question about a payment method, a bonus restriction or an account status means the answer is account-specific or policy-specific, and the reader should ask through the channel the operator provides for that category of question.
FAQ
Does the rune365.com FAQ state the current withdrawal minimum?
A FAQ may describe the withdrawal process and where the minimum is shown, but the figure itself belongs to the withdrawal policy and the withdrawal screen. Any number in a FAQ should be confirmed against those sources before a withdrawal is planned, because minimums change and the FAQ is not the binding record.
Can I rely on the FAQ's list of accepted payment methods?
The cashier is the only place the current list of deposit and withdrawal methods is shown for a given account and currency. A FAQ may describe how methods are displayed, but a method listed in a FAQ may have been removed, and a method not listed may have been added. Check the cashier at the moment of the transaction.
Where does the FAQ say which documents are needed for verification?
The FAQ typically describes the categories of documents — identity, address, payment method — but the specific list and the trigger for requesting them are set by the KYC or AML policy and shown on the account verification screen. The reader's own verification screen is the authoritative list for their account.
What should I do if the FAQ contradicts the terms and conditions?
Treat the terms and conditions as the binding document. When a FAQ figure or rule differs from the terms, the terms are what the operator's disputes process will cite. Confirm the current figure in the owning document, and if the contradiction affects a transaction, raise it through the support channel with the terms as the reference.
This page is an independent summary of what an operator FAQ covers and where its limits lie; it is not published by rune365.com, and it states no figure or status for that operator, whose own FAQ and terms pages 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.
