The page a reader opens when something is already wrong
A player usually arrives at Just Dice's FAQ not before a problem, but after one. A deposit has not appeared, a withdrawal is sitting in a state the player does not recognise, a document was rejected, or a game rule did not behave the way the player expected. The FAQ is the first place the operator organises the answers it is willing to give without looking at the reader's account. That is the whole function of the page: it answers the questions that have one answer for every player, and it points away from the questions that do not.
That distinction matters more than any single answer on the page. A question about which documents the operator normally asks for has one answer that can be written down and published. A question about why this particular reader's document was rejected does not, because the answer depends on the file the reader uploaded, the name on the account, and the operator's current verification queue. The FAQ can describe the first kind of question. It cannot settle the second, and a reader who expects it to will misread the page.
What an FAQ can answer bindingly
The binding part of an FAQ is the part that describes process. Process is stable because it is the operator's own workflow, not the reader's circumstances. The page can state which routes exist for moving money in and out, which document categories the verification team accepts, what happens to an account when self-exclusion is requested, and how a bonus is attached to a deposit. Those answers are binding in the sense that the operator has committed to them in writing on its own domain.
But even a process answer has a limit. The FAQ states the route, not the outcome. It can say that withdrawals are processed through the cashier and that the method used for deposit is the first method offered for withdrawal. It cannot say how long this reader's withdrawal will take, because the answer depends on the amount, the method, the verification state of the account, and the operator's current queue. The FAQ is the map of the process. The reader's account is the territory.
The same holds for game rules. A game-specific FAQ can state the objective of a game, the order of play, and what the player may do at each decision point. It cannot state what the player should do, and it cannot state what the player will win. The rule is binding; the result is not.
Where the FAQ stops and the account begins
Every FAQ stops at the point where the answer depends on the reader's account. The operator cannot publish a page that says "your withdrawal is delayed because your document was rejected", because the page is the same for every visitor. The operator can publish a page that says "a withdrawal stays pending while the account is under review, and the review ends when verification passes". The first sentence is support. The second is an FAQ entry. The reader who understands this will stop looking in the FAQ for an answer that can only come from the account itself.
That is why the most useful FAQ entries are the ones that name the next step. A good entry does not just describe the process; it says which screen shows the current state, which document list applies, and which channel carries the question that remains. The FAQ is a directory as much as it is an explanation.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit routes available | Payment methods are added and removed by the operator and by the providers themselves | The cashier or deposit page, not the FAQ, carries the current list |
| Withdrawal method for a deposit | Route availability depends on the method used, the amount, and the account's verification state | The withdrawal screen shows which routes are open for the reader's account |
| Document categories accepted | Verification requirements change with regulation and with the operator's own risk rules | The verification or KYC page, and the request the operator sends to the reader |
| Bonus wagering condition | Promotions are re-priced, replaced and withdrawn; a figure read in an FAQ may be stale | The promotion's own terms page, which is the only binding statement of the multiple |
| Self-exclusion effect | The policy itself changes, and the effect depends on the date and scope of the request | The responsible-gaming or self-exclusion page, and the confirmation the operator sends |
| Withdrawal processing time | Queue length, method, amount and verification state all move the answer | The withdrawal screen's status field, not a static FAQ entry |
The items that change even while the FAQ stays the same
An FAQ is a snapshot. The operator writes it once and updates it occasionally. The things it describes change more often than the page does. Payment methods are added and removed. Bonus terms are re-priced. Verification requirements shift when the operator changes its own risk rules or when a regulator changes what it expects. A reader who copies a figure from an FAQ and treats it as permanent is reading a document that was already out of date when it was published, because the things it describes move faster than the page.
This is not a defect of the FAQ. It is the nature of the page. The FAQ is the right place to learn the shape of a process: which steps exist, in what order, and which screen carries the current value. It is the wrong place to learn the current value itself. The current value lives on the page that performs the action: the cashier for methods, the promotion page for a wagering multiple, the verification page for document requirements, the withdrawal screen for a status.
Across operators, the same pattern holds. Deposit routes commonly number anywhere from a handful to several dozen, and they change without notice. Withdrawal processing commonly ranges from under an hour for small amounts on a method the operator already trusts, to several business days for a first withdrawal on a new account. Verification commonly asks for a government-issued photo ID, a proof of address, and sometimes a proof of the payment method itself. Those ranges are useful orientation. They are not this operator's numbers, and they are not a promise.
How to read the page without being misled
The first move is to separate the entries that describe a process from the entries that state a value. A process entry says what happens, in what order, and what the reader must do. A value entry says how much, how long, or how many. The process entry is safe to read as written. The value entry is safe only as a pointer to the page that carries the live number.
The second move is to check the date. If the FAQ carries a revision date, a reader can see how old the snapshot is. If it does not, the reader should assume the page is older than the things it describes. Either way, the FAQ is a starting point, not a finish line.
The third move is to read the FAQ against the terms. Where the FAQ and the terms disagree, the terms win. The terms are the contract. The FAQ is an explanation of the contract, and an explanation can be wrong or stale. A reader who finds a conflict has found something worth asking support about, because the conflict itself is information.
What the FAQ cannot settle, and where the binding answer lives
There is a class of questions that no FAQ can settle, no matter how well it is written. Anything that depends on the reader's account state is out of scope. Anything that depends on the current promotion is out of scope. Anything that depends on the operator's current risk appetite is out of scope. For those questions, the FAQ can only say which channel carries the answer.
The binding answer for an account question lives in the account itself, on the screen that shows the state. The binding answer for a promotion question lives on the promotion's own terms page. The binding answer for a verification question lives in the request the operator sends to the reader, because that request names the documents the operator wants from this reader at this moment. The FAQ is the index to those places. It is not a substitute for them.
When the FAQ does not state an item, the absence is itself an answer. If the FAQ does not name a withdrawal time, the reader cannot assume one. If the FAQ does not list a deposit method, the reader cannot assume the method exists. If the FAQ does not state a wagering multiple, the reader cannot assume the bonus is withdrawable at all. The silence is not an oversight. It is the operator declining to commit in writing, and a reader should treat that silence as a reason to check the binding page before acting.
FAQ
Does the Just Dice FAQ tell me how long my withdrawal will take?
It can tell you the process: which steps a withdrawal passes through, and which screen shows the current state. It cannot tell you the time for your withdrawal, because the time depends on the amount, the method, the verification state of your account, and the operator's current queue. The withdrawal screen's status field is the place that carries your answer.
Can I rely on the deposit methods listed in the FAQ?
Only as a guide to what has been available at some point. Payment methods change without notice, and the FAQ is a snapshot. The cashier or deposit page is the only place that lists the methods open to you right now.
If the FAQ and the terms say different things, which one wins?
The terms. The FAQ is an explanation of the terms, and an explanation can be stale or wrong. The terms are the contract. A conflict between the two is worth raising with support, but the terms remain the binding document.
What should I do when the FAQ does not answer my question?
Look for the page that performs the action your question is about: the cashier for money movement, the verification page for documents, the promotion page for bonus terms, the withdrawal screen for status. If the answer is not on any of those, the support channel is the remaining route, and the question is one that depends on your account rather than on a published process.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Just Dice, and it states no figure or status for them — the operator's 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.
