A player opens an operator's FAQ because a specific process has stalled: a deposit has not appeared, a withdrawal is marked pending, a document was rejected, or a bonus did not trigger. The FAQ is the first place to look, but it is not the place where the binding answer lives. It explains how things normally work. It cannot know what is true for a particular account at a particular moment, and it cannot override the terms page. Reading it well means knowing which of its answers are reliable and which are only a starting point.
What a FAQ can answer bindingly
A FAQ is strongest when it describes the operator's standard routes and document lists. These are the parts of the site that change least often and apply to most players in the same way. A question like "which documents are accepted for verification" has a stable answer: the operator accepts a passport, a national ID, or a driving licence, and the FAQ can list those categories without knowing anything about the reader. A question like "which deposit methods are available" is also stable in its general form, because the cashier routes are built into the platform. The reader can take those answers as the operator's stated position and act on them.
The binding force of a FAQ answer comes from the fact that the operator published it on its own site. If the FAQ says a document must be in colour, or that a bank statement must be less than three months old, that is a requirement the reader can rely on when preparing a submission. If the FAQ says a withdrawal route must match the deposit method, that is a process rule the reader can expect to be applied. These are not account-specific facts; they are general conditions, and the FAQ is a legitimate place for them.
Where a FAQ stops being binding
The moment a question depends on the reader's own account, the FAQ can only describe the usual outcome. It cannot say whether a specific withdrawal will be approved, how long it will take, or why a particular document was rejected. Those facts are generated by the operator's systems and by the reader's history, and no static page can contain them. A FAQ that says "withdrawals are usually processed within two business days" is stating a norm, not a promise. The reader's own withdrawal may sit longer because of verification, a weekend, a payment-provider delay, or a review triggered by the amount.
Similarly, anything that depends on current terms is outside the FAQ's authority. A bonus percentage, a wagering multiple, a minimum deposit, a maximum withdrawal cap — all of these are set by the promotions terms or the general terms, and those pages are updated independently of the FAQ. If the FAQ mentions a figure and the terms page states another, the terms page wins. The reader should treat any number in a FAQ as a pointer to the page that governs it, not as the final word.
The three kinds of FAQ questions
Most FAQ questions fall into one of three groups, and each group has a different relationship to the operator's other pages. Understanding the group tells the reader where to look next.
| Question type | What the FAQ can do | Where the binding answer lives |
|---|---|---|
| Process and routes | State the standard steps, document lists, and available methods | The FAQ itself is usually sufficient; the cashier or verification page confirms |
| Terms and figures | Mention a figure or condition as a general indication | The promotions terms, general terms, or payment policy page |
| Account-specific status | Describe what usually happens and what may cause delay | The player's own account area; support is the only channel that can state the actual status |
| Compliance and limits | Explain why a document or check is required | The AML policy, KYC page, or responsible-gaming page |
The first group is the only one where the FAQ is close to final. For the other three, the FAQ is a map, not the destination. A reader who stops at the FAQ and acts on a figure found there has read the wrong page.
What changes and what stays fixed
FAQ pages are maintained by the operator, and the operator changes them when its processes or its commercial terms change. A payment method may be added or removed. A document requirement may be tightened. A bonus structure may be replaced. The reader who read the FAQ six months ago and returns today cannot assume the answer is the same. The only way to know is to read the FAQ again, and then to check the page that governs the specific item.
What stays fixed is the structure of the operator's obligations: the operator must verify identity before releasing funds, must apply its stated terms to bonuses, and must provide a route for complaints. Those obligations are not created by the FAQ; they are created by the operator's terms and by the regulatory framework it operates under. The FAQ can explain them, but it cannot alter them. A reader who finds a contradiction between the FAQ and the terms page should treat the terms page as authoritative and, if the contradiction matters, ask support to reconcile the two.
Reading the FAQ against the terms page
The most common error is to read the FAQ as a summary of the terms. It is not. The terms page is drafted to be binding; the FAQ is drafted to be helpful. The terms page uses defined words, cross-references, and conditions. The FAQ uses plain language and often omits the exceptions. A FAQ that says "withdrawals are paid to the method used for deposit" may not mention that this rule has exceptions for closed methods, or that the operator may offer an alternative route. The terms page will state the rule and its exceptions. The reader who needs certainty should read both, and where they differ, follow the terms.
This does not make the FAQ useless. It makes it a starting point. The FAQ tells the reader which page to open, which document to prepare, and which question to ask support. That is a real function. It is not a substitute for the binding source.
When the FAQ does not state an item
An FAQ is a selection. The operator chooses which questions to answer, and the absence of a question is itself information. If the FAQ does not explain how a withdrawal is reviewed, the reader cannot conclude that no review exists. If the FAQ does not state a processing time, the reader cannot conclude that processing is instant. If the FAQ does not list a document, the reader cannot conclude that the document is not required. The absence means only that the operator has not chosen to answer that question on that page.
In those cases, the reader has two moves. The first is to open the page that governs the item: the payment policy for withdrawal times, the AML policy for verification triggers, the promotions terms for bonus conditions. The second is to ask support, in writing, and to keep the answer. A written answer from support is the operator's statement about the reader's account, and it is more specific than anything a FAQ can say.
What the FAQ cannot tell you about your own account
No FAQ can tell a reader whether their deposit has arrived, whether their documents have been approved, or whether their withdrawal has been released. Those facts exist only in the operator's systems, and they change minute to minute. The FAQ can describe the stages: a deposit must be confirmed by the payment provider, a document must pass review, a withdrawal must clear verification. But it cannot say which stage the reader's own transaction is in. The reader who wants that answer must look at the account area, where the operator displays status, or contact support.
This is the line that separates a FAQ from a support channel. The FAQ is general; support is specific. The FAQ is static; support is live. The FAQ is free to read; support requires the operator to act. A reader who treats the FAQ as a support channel will be frustrated, because the FAQ cannot see their account. A reader who treats support as a FAQ will also be frustrated, because support will answer the general question but cannot change the general rule. Each has its place.
Questions to ask before acting on a FAQ answer
Before a reader relies on a FAQ answer, three checks are worth making. First, is the answer about a process or a figure? A process answer is more stable. A figure answer must be checked against the page that governs it. Second, does the answer apply to the reader's own situation? A FAQ that says "most withdrawals are processed within two business days" is not a statement about the reader's withdrawal. Third, has the answer changed since the reader last looked? The FAQ is a living page, and the operator can revise it without notice.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Operators revise document lists as compliance requirements change | FAQ or the verification page in the account area |
| Available deposit methods | Payment providers are added and removed; availability varies by region | Cashier page, not the FAQ alone |
| Withdrawal processing time | Depends on verification status, amount, method, and provider delays | Payment policy page; the FAQ states only a norm |
| Bonus percentage and wagering | Promotions are replaced and terms are revised independently of the FAQ | Promotions terms page |
| Withdrawal route rule | Exceptions exist for closed methods and alternative routes | General terms or payment policy |
| Verification triggers | Thresholds and triggers are set by the AML policy and can be revised | AML policy page |
Using the FAQ without being misled
The FAQ is most useful when the reader knows what it is: a curated set of general answers, maintained by the operator, accurate at the level of process but not at the level of account status or current figures. A reader who uses it to find the right page, prepare the right document, and ask the right question gets real value from it. A reader who uses it as the final authority on a bonus or a withdrawal has read the wrong page and may act on a figure that no longer applies.
The operator's own site is the only binding source for its terms. The FAQ is part of that site, but it is the least binding part of it. Where a FAQ answer and a terms page answer conflict, the terms page governs. Where a FAQ answer and a support answer conflict, the support answer is more specific and should be kept in writing. The reader who understands this hierarchy can use the FAQ without being misled by it.
FAQ
Can I rely on the figures in a FAQ?
Only as a general indication. Any figure in a FAQ — a bonus percentage, a processing time, a minimum deposit — is set by the terms page or the payment policy, and those pages are revised independently. The reader should check the governing page before acting on a figure found in a FAQ.
What should I do if the FAQ and the terms page disagree?
Treat the terms page as authoritative. The FAQ is a plain-language summary and may omit exceptions. If the contradiction affects a decision, ask support in writing to reconcile the two, and keep the answer.
Can a FAQ tell me why my withdrawal is delayed?
No. A FAQ can describe the usual stages and the common causes of delay, but it cannot see a specific account or a specific transaction. The account area shows the current status, and support is the only channel that can state the actual reason for a delay.
Is a FAQ a substitute for reading the terms and conditions?
No. The terms page is drafted to be binding and contains the exceptions and conditions that a FAQ omits. The FAQ is a starting point that points to the right page; it is not a summary that can be relied on in place of the terms.
This page is an independent summary of what an operator FAQ covers and where its authority stops. It is not published by lootcasino.com, and it states no figure or status for that operator. The operator's own FAQ, terms pages, and support channel are the only binding sources for its processes and conditions.
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.
