The situation a reader is in when they open an FAQ
A player does not open an operator's FAQ page out of curiosity. They open it because something has already gone wrong, or because they are about to do something and want to know the rule before money moves. The deposit did not arrive. The withdrawal has been pending longer than expected. The verification upload failed. The bonus did not credit. The FAQ is the first place they look, and the first place they learn what the operator will and will not put in writing.
That starting point matters because it sets the limit on what any FAQ can do. An FAQ is a collection of short answers to questions the operator expects to be asked repeatedly. It is written once and read many times. It is therefore good at answering questions whose answer is the same for every reader: which documents are accepted, which deposit routes exist, what the general withdrawal flow is, how to find a game's rules. It is structurally incapable of answering questions whose answer depends on the reader's own account: why this deposit is missing, where this withdrawal is in the queue, whether this document is enough for this verification. The reader who understands that distinction reads the FAQ for what it can give and goes elsewhere for what it cannot.
What a casino FAQ can answer bindingly
An FAQ page is a published document. Whatever it states about general process is a statement the operator has chosen to make publicly, and a reader can hold the operator to it in a dispute. That is what makes it different from a live-chat answer: the chat answer is ephemeral, the FAQ answer is on the page and can be screenshotted, dated and quoted. The binding quality attaches to the statement, not to the page type, but the page type is what makes the statement stable enough to rely on.
The questions an FAQ can answer bindingly fall into a few predictable groups. The first is document lists: what counts as proof of identity, proof of address, proof of payment method. The second is route availability: which deposit methods the cashier offers, which withdrawal methods exist, whether a withdrawal route requires a prior deposit on the same method. The third is mechanical process: what happens after a withdrawal is requested, what order verification steps occur in, what a wagering requirement is and how it is measured. The fourth is account controls: how to set a deposit limit, how to self-exclude, how to close an account. On all of these, the FAQ can state a rule that applies to every reader, and the reader can rely on it.
What the FAQ cannot do is state a number that belongs to the reader's own account. It cannot say whether this deposit will arrive, because that depends on the payment provider, the amount, the method and the account's verification state. It cannot say when this withdrawal will clear, because that depends on the queue, the method and the checks applied to this account. It cannot say whether this document is sufficient, because that is a decision made by a reviewer looking at the file. The FAQ can state the general rule and the general range; it cannot apply the rule to a specific case.
Where the FAQ stops and the binding answer moves elsewhere
The most important sentence on any FAQ page is the one that tells the reader where to go next. Every operator's FAQ has a boundary, and the boundary is usually marked by a sentence like "if your question is not answered here, contact support" or "for account-specific questions, use live chat." That sentence is not a formality. It is the operator's own admission that the FAQ is not the final authority on anything that depends on the reader's account.
For a deposit that has not arrived, the binding answer is not in the FAQ. It is in the transaction history in the cashier, in the payment provider's own records, and in the support ticket the reader opens. The FAQ can tell the reader what the normal flow is and what to check first; it cannot tell the reader where their money is. For a withdrawal that is pending, the binding answer is in the withdrawal status shown in the account, and in the email or notification the operator sends when the status changes. The FAQ can explain what "pending" means in general; it cannot shorten the queue.
For verification, the binding answer is in the document request itself. The operator's verification team states which documents it wants, in which format, and what will cause a rejection. The FAQ can list the documents that are commonly accepted; it cannot pre-approve a specific file. A reader who uploads a document because the FAQ said it was accepted, and then has it rejected, has not been lied to: the FAQ stated the general rule, and the reviewer applied a specific judgment. The reader's remedy is to read the rejection reason and resubmit, not to quote the FAQ back at the operator.
For bonuses and wagering, the binding answer is in the promotion's own terms, not in the FAQ. The FAQ may summarise how wagering works in general, but the multiple that applies to a specific bonus is stated on the promotion page or in the bonus's terms. If the FAQ and the promotion terms conflict, the promotion terms win, because they are the document that was attached to the offer. A reader who relies on the FAQ summary and is surprised by the actual multiple has read the wrong document.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Document lists are revised as compliance requirements change; a document accepted last year may not be accepted now | The verification request in the account, or the FAQ's document list read against the request |
| Deposit methods available | Payment routes are added and removed by the operator and by payment providers; a method shown today may be gone tomorrow | The cashier's deposit screen, which shows only the methods live for the reader's account and region |
| Withdrawal methods and conditions | Withdrawal routes depend on deposit history, verification state and the operator's current rules; the route for one reader is not the route for another | The cashier's withdrawal screen, read together with the withdrawal policy page |
| Wagering requirement for a bonus | Each promotion carries its own multiple; the FAQ can only describe the general mechanism, never the specific number | The promotion's own terms, linked from the offer the reader accepted |
| Withdrawal processing time | Processing time depends on the method, the queue, the verification state and the amount; no FAQ can state a single number that holds for every reader | The withdrawal status in the account, and the operator's withdrawal policy page for the general range |
| Self-exclusion and limit tools | These are account-level controls; the FAQ can describe them but the reader must apply them from the account settings, where the current options are shown | The responsible-gaming or account-limits section of the reader's own account |
What it means when the FAQ does not state an item
Absence from an FAQ is itself information. If the FAQ does not state a processing time for withdrawals, that is not an oversight: it is the operator declining to put a number in writing that it may not be able to meet for every reader. If the FAQ does not list accepted documents, the operator is telling the reader that the document request will be made case by case. If the FAQ does not state a wagering multiple, the operator is telling the reader that the multiple lives in the promotion terms, not in the FAQ. In each case, the absence is the answer: the reader should not assume a number exists just because the FAQ is silent.
The same logic applies to the FAQ's own scope. If the FAQ does not mention a topic at all, the reader should not conclude that the operator has no rule on it. It may mean the topic is covered by a different page: the terms and conditions, the privacy policy, the AML policy, the withdrawal policy. An FAQ is a summary layer, not a complete rulebook. The reader who needs the full rule should read the full document, and the FAQ's job is partly to point there.
How to read an FAQ against the operator's other pages
An FAQ is best read as an index. It tells the reader which questions exist, which answers are general, and which other page carries the specific rule. When the FAQ says "see our withdrawal policy," that is not a brush-off; it is the operator telling the reader that the binding answer is on a page that is updated more carefully than the FAQ. The withdrawal policy page is a legal document; the FAQ is a convenience. The reader who wants the rule reads the policy; the reader who wants a quick orientation reads the FAQ.
The same applies to the terms and conditions. An FAQ may summarise a rule about account closure, bonus abuse or dormant accounts, but the summary is not the rule. The terms and conditions are the rule, and they are the document a dispute will be decided against. A reader who quotes the FAQ in a dispute is quoting a summary; a reader who quotes the terms is quoting the contract. The difference matters when money is at stake.
For anything that depends on the reader's own account, no published page is the final answer. The final answer is in the account itself: the transaction history, the withdrawal status, the verification request, the bonus balance. The FAQ can tell the reader where to look; it cannot look for them. A reader who reads the FAQ and then checks the account is using the FAQ correctly. A reader who reads the FAQ and stops there has stopped one step short of the answer.
FAQ
Can I rely on the Thor FAQ for a withdrawal time?
No. The FAQ can state the general flow and the factors that affect timing, but the time for a specific withdrawal is shown in the account's withdrawal status and depends on the method, the verification state and the queue. The FAQ's general statement is not a promise about any particular withdrawal.
What should I do if the Thor FAQ does not answer my question?
Check the operator's other published pages first: the terms and conditions, the withdrawal policy, the privacy policy and the promotion terms each carry rules the FAQ only summarises. If the question is about your own account, open a support ticket or use the live chat, because no published page can apply a general rule to your specific case.
Does the Thor FAQ state which documents are accepted for verification?
It may list the document types commonly accepted, but the binding list is the one in the verification request sent to your account. A document the FAQ lists can still be rejected if the reviewer judges it insufficient for your case, so read the request and the rejection reason rather than the FAQ summary.
If the Thor FAQ and the promotion terms conflict, which one wins?
The promotion terms win. They are the document attached to the offer you accepted, and they state the wagering multiple and eligibility conditions that apply to that bonus. The FAQ is a general summary and is not the contract for any specific promotion.
This page is an independent summary of what an operator FAQ page covers and where its answers stop; it is not published by Thor, and it states no figure or status for that operator, whose own FAQ and linked policy pages are the only binding sources for the rules that apply to a reader's account.
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.
