A player opens an operator's FAQ because one specific thing is stuck: a deposit has not appeared, a withdrawal is pending, a document was rejected, or a bonus did not credit. The FAQ is the first place they look, and it is useful for exactly one kind of answer. It can tell them how a process is supposed to run. It cannot tell them what is happening to their own account right now, and it cannot bind the operator to a number that lives in the terms. The rest of this page is about reading that distinction correctly.
The one thing an FAQ can answer bindingly
An operator FAQ is a process document. Its strongest answers are about routes and sequences: which payment page to open, which document types the verification team asks for, which button starts a self-exclusion, which email address or form carries a complaint. Those answers are binding because they describe a procedure the operator itself has set up. If the FAQ says a withdrawal request is made from the cashier page, that is where the request is made. If it says a proof-of-address document must show the player's name and a date, that is the document standard.
What an FAQ almost never contains is a promise about an outcome. It will not state that a specific withdrawal will clear on a specific day, because that depends on the account, the method, the amount and the verification state. It will not state that a specific bonus will apply to a specific deposit, because eligibility is decided against the promotion terms at the moment of the deposit. The reader who treats an FAQ answer as a guarantee has misread the document type.
Where the FAQ stops and the terms begin
The cleanest way to understand an operator FAQ is to see it as a map, not a contract. A map shows the roads. A contract states who owes what. When a question is about a road - "where do I upload a document?" - the FAQ is the right place. When a question is about an obligation - "how much must I wager before I can withdraw?" - the FAQ may repeat the number, but the number is only binding where the promotion terms state it. If the two ever differ, the terms govern.
This is why a careful reader checks the FAQ against the terms page on anything that involves a figure. A wagering multiple, a minimum withdrawal, a maximum deposit, a fee, a processing window: each of these belongs to a specific terms document. The FAQ is a summary. Summaries go stale. The terms page is the source that can be enforced in a dispute.
What the FAQ cannot know about the reader's account
Every FAQ is written before the reader's account exists. It cannot know whether this reader has passed verification, whether this reader's deposit method supports withdrawals, whether this reader's bonus is active, or whether this reader's country is restricted. Any FAQ answer that touches those things is necessarily conditional. The reader's actual status is visible only in the account itself: the cashier shows the available methods, the verification page shows the outstanding documents, the bonus page shows the active offers and their progress.
This is not a defect in the FAQ. It is the nature of a general document. A reader who asks "why is my withdrawal pending?" and reads only the FAQ will get a list of common reasons - verification incomplete, method mismatch, amount below minimum, wagering not met - but not the reason that applies to them. The reason that applies to them is on the withdrawal page or in the message attached to the request.
Which items on an FAQ page decide what happens to the reader's money
The following table separates the items an FAQ typically covers into those that can be read off the FAQ and those that must be read elsewhere. The table is about the kind of page, not about any one operator's version of it.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit routes available to the reader | Methods are offered by country, account level and currency; the FAQ lists the general set, not the reader's set | Cashier page, after login |
| Withdrawal routes for a given deposit method | Not every deposit method has a matching withdrawal route, and the mapping changes with processor availability | Withdrawal page or payment terms |
| Document types for verification | The list is stable, but which documents are asked from a given reader depends on their profile and deposit history | Verification page in the account |
| Wagering multiple for a bonus | Promotions change; the FAQ may carry an old multiple | Promotion terms page, current at the time of the deposit |
| Minimum and maximum withdrawal amounts | These are set per method and per currency, and are revised periodically | Withdrawal terms or cashier page |
| Processing time for a withdrawal | Depends on verification state, method, amount and review triggers; the FAQ gives a range, not a promise | Withdrawal request status in the account |
| Self-exclusion and cooling-off controls | The control itself is stable, but its effect on pending bonuses or withdrawals is governed by terms | Responsible gaming page and account settings |
| Complaint and dispute channel | The channel is stable, but the outcome of any single complaint is not | FAQ contact section or support page |
The pattern in the table is consistent: the FAQ names the road, the account or the terms state the destination. A reader who needs a binding answer on money should read the FAQ only to learn which other page to open.
Why an FAQ answer read today may not hold tomorrow
Operator FAQs are maintained documents, but they are maintained on the operator's schedule, not the reader's. A promotion ends and its FAQ entry lingers. A payment method is removed and the FAQ still lists it for a week. A verification rule changes and the old wording stays up until the next content update. This is normal across operators, and it is why no FAQ figure should be treated as current unless it is confirmed on the page that controls the transaction.
The items that change most often are the ones tied to third parties: payment processor availability, currency support, and the exact document a compliance team currently accepts. The items that change least are the structural ones: where the cashier is, how to open a support ticket, what self-exclusion does. A reader can rely on the structural answers. For everything else, the FAQ is a starting point.
What it means when the FAQ does not state an item
An absence in an FAQ is itself information. If the FAQ does not state a withdrawal minimum, the reader cannot assume there is none; the minimum is simply stated elsewhere or applied at the time of the request. If the FAQ does not name a testing laboratory or a licence, the reader cannot assume one exists; the absence means the FAQ is not the place where that status would be published, and the reader must look to the operator's legal or footer pages, or conclude that no such status is being claimed. If the FAQ does not explain how a bonus is released, the promotion terms remain the only binding source, and a reader who claims the bonus without reading them is acting on no information at all.
The correct response to an absent item is not to guess. It is to note that the question is unanswered by this page and to find the page that owns the answer. For money, that is the cashier and the terms. For status, that is the legal or about page. For the reader's own account, that is the account itself.
How to use an FAQ without being misled by it
The safest reading habit is to use the FAQ only for navigation. Ask it: which page do I open, which document do I prepare, which button do I press. Then go to that page and read the current state. Do not ask the FAQ: how much, how long, am I eligible, is my money safe. Those questions have answers, but the FAQ is not the document that carries them bindingly.
A second habit is to note the date or version marker if one is present. An FAQ with no date is not necessarily wrong, but it gives the reader no way to know whether it predates the current promotion. An FAQ with a date still does not override the terms; it only tells the reader how old the summary is.
FAQ
Can I rely on the FAQ for withdrawal times?
The FAQ may state a typical processing range, but the time that applies to a specific withdrawal depends on the method, the amount, the verification state and any review triggers. The binding status of a withdrawal is shown on the withdrawal request page in the account, not in the FAQ.
Does the FAQ tell me which documents I must upload?
It usually lists the accepted document types, such as proof of identity and proof of address. Which of those a given reader must upload is determined by the verification page after login, which reflects the current state of that reader's account.
If the FAQ does not mention a wagering requirement, is there none?
No. The absence of a wagering multiple from the FAQ means only that the FAQ does not state it. The promotion terms page is the binding source for any wagering requirement, and a reader should read that page before claiming a bonus.
Where is the binding answer when the FAQ and the terms disagree?
The terms and conditions, and the specific promotion terms, govern. An FAQ is a summary and may be out of date. In any conflict, the document that creates the obligation is the one that can be enforced.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Crypto Casino Dice, 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.
