The limit every FAQ shares: process, not outcome
A player opens an operator's FAQ with a specific question in mind: how long a withdrawal takes, which documents unlock a locked account, why a bonus did not appear. What they often do not notice is that the FAQ can answer only the first kind of question. An FAQ page describes the route a request follows and the documents or steps the operator asks for along that route. It cannot tell a specific reader what will happen to their specific request, because that depends on the reader's own account state, the payment method they chose, and the terms in force on the day of the request.
That is not a defect of any one FAQ. It is the structure of the document. A Fair Dice FAQ is a general reference for recurring questions. The moment a question becomes "what happens to my deposit right now", the answer moves out of the FAQ and into the reader's own account, the cashier, or a support conversation. Reading the FAQ with that boundary in mind saves a reader from treating a general description as a personal promise.
The practical consequence is simple. When the FAQ says a withdrawal is reviewed before release, that tells the reader a review step exists. It does not tell the reader that their withdrawal will clear today, tomorrow, or at all. The FAQ is the map of the process, not the outcome of the journey.
What an FAQ can answer bindingly
Three categories of question sit naturally inside an operator FAQ, because the answer is the same for every reader who asks them.
The first is process. Which steps does a deposit follow between the moment a player confirms it and the moment the balance updates? What happens after a withdrawal request is submitted? What does account verification require, and in what order? These answers describe a route, and the route does not change from one reader to the next. A deposit either appears in the cashier or it does not; the FAQ explains where to look and what the intermediate states mean.
The second is document lists. Verification, for example, is a list of documents: proof of identity, proof of address, sometimes proof of the payment method. The FAQ can state which categories of document the operator asks for. It cannot state whether a given reader's document will be accepted, because acceptance depends on the document's quality, expiry, and match with the account details.
The third is definitions. What does "wagering requirement" mean? What is a rollover? What counts as a bonus-eligible game? These are rule definitions, and a well-written FAQ defines them once for everyone. The definition is binding; the reader's position under that definition is not.
What these three categories share is that they are account-independent. The operator can print them once and they hold for every reader. That is exactly the material an FAQ is built to carry.
What an FAQ cannot answer, and why
The mirror image is the category of questions an FAQ cannot settle, however confidently the reader asks them.
Anything that depends on the reader's own account is out of scope. Whether a withdrawal has been approved, why a deposit is pending, whether a document was accepted, whether a bonus is active: all of these turn on data the FAQ does not hold. The FAQ can say that a withdrawal is reviewed, but it cannot say that this reader's withdrawal passed review. The reader's account page and any message from the operator carry that answer.
Anything that depends on current terms is also out of scope, for a different reason. Terms change. A bonus percentage, a wagering multiple, a minimum deposit, a list of accepted payment methods: these are figures, and figures are revised. An FAQ that printed them would go stale. The operator's own terms page, promotions page, and cashier are the live documents; the FAQ points toward them rather than repeating them.
Finally, anything that requires a decision about a specific reader is out of scope. Whether an account will be closed, whether a withdrawal will be refused, whether a document will be rejected: these are decisions made case by case, against the operator's policies and the reader's history. No FAQ can make them in advance.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Withdrawal review steps | The route is stable, but the reader's place in it is not | FAQ describes the route; the account page shows the current state |
| Verification document list | Categories are fixed; acceptance of a specific document is not | FAQ lists categories; the verification request names what is needed |
| Bonus wagering multiple | Figures are revised across promotions | Promotions terms page, not the FAQ |
| Deposit methods available | Method lists change by region and over time | Cashier, not the FAQ |
| Withdrawal minimum or maximum | Limits are adjusted by the operator | Withdrawal policy or cashier page |
| Account closure or restriction criteria | Decisions are case-by-case under policy | Terms and conditions; support for the specific case |
Reading the FAQ against the live documents
The useful habit is to treat the FAQ as an index, not as the final word. When a reader wants to know what a term means, the FAQ is a good place to learn the definition. When a reader wants to know what the term is for their situation, the FAQ is only a pointer.
Take a withdrawal question. The FAQ may explain that withdrawals pass through a review step, that verification may be requested, and that the cashier shows the available methods. Those are all true and useful. But the amount a reader may withdraw, the method they may use, and the time their specific request will take are all stated elsewhere: on the withdrawal policy page, in the cashier, and in the account's own transaction history. A reader who reads only the FAQ and expects it to contain those figures will leave with the wrong impression.
The same holds for bonuses. The FAQ can define a wagering requirement. It cannot state the multiple for the bonus the reader just claimed, because that multiple is printed on the promotion's own terms. If the FAQ and the promotion page disagree, the promotion page governs, because it is the document that created the offer.
Where the FAQ is silent, the reader should not assume the answer is "no". Silence in an FAQ means only that the question is not answered there. The answer may exist in the terms, in the cashier, or only in a support reply. The absence of a statement is not itself a policy.
The verification question: where the FAQ stops
Account verification is the clearest example of the boundary. The FAQ can list the document categories: identity, address, payment method. It can explain that documents must be valid and legible. It can describe the order in which the operator requests them.
What it cannot do is tell a reader whether their own document will pass. A passport that expired last month will fail; a utility bill in someone else's name will fail; a screenshot of a bank statement may fail. None of those outcomes is knowable from the FAQ, because none of them is a general rule. They are judgments about a specific document against a specific account.
The reader who needs that answer should look at the verification request itself. The operator's request names the document category and the deadline. The account page or the support channel carries the outcome. The FAQ is the map of what verification is; the request is the instruction for what this reader must do.
FAQ vs. terms: which document governs
A recurring confusion is which document wins when an FAQ and a terms page seem to conflict. The answer is structural, not a matter of preference. The terms and conditions are the contract the reader accepted. The FAQ is an explanatory summary. Where the two differ, the terms govern, because the terms are the document that creates the obligation.
That does not make the FAQ useless. A well-drawn FAQ saves a reader from reading fifty pages of terms to learn what a rollover is. But the FAQ is a convenience, not a source of rights. If the FAQ says "withdrawals are reviewed" and the terms say "withdrawals above a threshold require additional verification", the terms add a condition the FAQ did not mention. The reader's position is governed by the terms, and the FAQ's silence on the threshold does not remove it.
The practical rule is to read the FAQ for orientation and the terms for obligation. When a decision about the reader's money or account is at stake, the terms page, the promotion page, or the support reply is the binding source. The FAQ is where the reader starts, not where the reader finishes.
FAQ
Can the Fair Dice FAQ tell me how long my withdrawal will take?
No. The FAQ can describe the review steps a withdrawal passes through, but the time for a specific withdrawal depends on the reader's account state, the method chosen, and the operator's current processing load. The account's transaction page and any message from the operator carry the actual status.
If the FAQ does not mention a payment method, does that mean Fair Dice does not accept it?
Not necessarily. An FAQ may list only the most common methods or none at all. The cashier is the live list of what is available to a specific reader in a specific region. Silence in the FAQ is not a policy statement.
Does the FAQ's explanation of verification tell me my document will be accepted?
No. The FAQ explains what verification is and which categories of document are requested. Whether a specific document passes depends on its validity, legibility, and match with the account details. The verification request and the support channel carry that outcome.
If the FAQ and the terms page disagree, which one applies?
The terms page applies. The terms are the contract the reader accepted; the FAQ is an explanatory summary. Where the two differ, the terms govern, and the FAQ's silence on a condition does not remove the condition.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Fair Dice, and it states no figure or status for the 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.
