A reader lands on an operator's FAQ because a deposit has not arrived, a withdrawal is stuck at a step whose name they do not recognise, or a bonus they accepted now seems to have conditions attached. The first thing to understand is what kind of page an FAQ is. It is a triage document, not a contract. It tells the reader which department owns their problem and which document governs it. It rarely settles the problem itself.
The division of labour an FAQ exists to mark
Every operator site of this kind is built from two layers. The binding layer is the set of documents that can be enforced against the reader or by the reader: the terms and conditions, the privacy policy, the withdrawal policy, the AML policy, and any promotion-specific terms. The navigation layer is everything that points at those documents: the cashier screens, the help centre, the chat widget, and the FAQ.
An FAQ sits deliberately in the navigation layer. Its job is to route. When it says that a withdrawal requires verification, it is pointing at the verification procedure described in the withdrawal policy. When it says a bonus has a wagering requirement, it is pointing at the promotion terms where the multiple is printed. The FAQ sentence itself is a summary, and a summary has no independent force. If the summary and the underlying document disagree, the underlying document wins, and the reader has no claim based on having read the summary.
This is not a defect of any particular operator. It is the structure of the page type. The reader who treats an FAQ answer as the final word has read the wrong layer.
Which questions an FAQ can answer bindingly
Some questions are about process, not about the reader's specific position. An FAQ can answer those, because the answer does not change from account to account. The table below separates the kinds of answers an FAQ can give from the kinds it cannot.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Which documents are accepted for identity verification | The list is a policy choice, and operators revise it as fraud patterns change | On the operator's own verification or KYC page, not in the FAQ summary |
| Which deposit methods appear in the cashier | Method availability varies by country, currency and account status | In the cashier itself, after login, for the reader's own account |
| Whether a withdrawal route exists for a deposit method | Route mapping changes as payment providers alter their terms | On the withdrawal policy page, under the method-by-method table |
| What the wagering multiple is on a given bonus | Each promotion carries its own multiple, and it is revised between campaigns | In the promotion-specific terms, not in the general FAQ |
| Which games contribute to a wagering requirement, and at what rate | Contribution rates are set per game category and adjusted periodically | In the bonus terms, usually in a table headed "game weighting" |
| What happens when an account is dormant | The dormancy trigger and the fee, if any, are set in the terms and revised | In the general terms and conditions, under a dormancy or inactive account clause |
| Which regulator or licence the operator holds | Licence status can change, and the FAQ may lag behind a renewal | In the footer of the operator's site, on the licence page, or in the regulator's public register |
The pattern is consistent. An FAQ can tell the reader that a category of rule exists and roughly where it lives. It cannot tell the reader what the current value of that rule is for their account, because the FAQ is written once and read by thousands of accounts in different states.
Which questions an FAQ cannot answer at all
The line is easiest to see from the other side. A question whose answer depends on the reader's own account cannot be answered by any FAQ, however well written. The FAQ does not know the reader's balance, their verification status, their country of residence, their deposit history, or whether their last bonus is still active. Any answer it gives to such a question is either a restatement of policy or a guess.
Consider the question "why is my withdrawal pending?" The FAQ can list the generic reasons a withdrawal might be pending: verification incomplete, a wagering requirement unmet, a payment provider delay, a review triggered by the amount. It cannot say which of those reasons applies to this reader on this day. The answer that matters is on the withdrawal screen in the reader's own account, or in the message the operator sent when the withdrawal was submitted.
The same holds for "why was my deposit declined?" The FAQ can list the generic causes: the card issuer refused the transaction, the method is not available in the reader's country, the amount is outside the allowed range, the account has a restriction. It cannot see the decline code the payment provider returned. That code is visible to the operator's payments team, and sometimes to the reader in their bank statement or card app.
Account-specific questions are not a failure of the FAQ. They are outside its design. The reader who expects the FAQ to resolve them is asking the navigation layer to do the work of the account layer.
What changes, and why an FAQ answer read today may not hold tomorrow
Every operator revises its terms. Bonuses are re-priced, wagering multiples are adjusted, payment methods are added and removed, verification requirements are tightened or loosened, and dormant-account rules are rewritten. The FAQ is a summary of the current state of those documents, and it is revised on a different schedule from the documents themselves.
The gap matters. A reader who reads the FAQ in January and acts on it in March may be acting on a version that has been superseded. The promotion terms may have changed the wagering multiple; the withdrawal policy may have added a new verification step; the cashier may have removed a payment method the FAQ still lists. The FAQ is not the place where the current value is binding. The binding value is on the page that owns the rule.
This is why the careful reader treats the FAQ as an index, not as a source. The index tells you which shelf the book is on. It does not tell you what is on page forty-seven.
Where the binding answer lives, for each kind of question
For a deposit question, the binding answer is in the cashier, after login. The cashier shows the methods available to that account, the minimum and maximum amounts for each, and any fee the operator applies. The FAQ can describe the cashier; it cannot substitute for it.
For a withdrawal question, the binding answer is the withdrawal policy page and the withdrawal screen in the reader's account. The policy states the verification steps, the processing windows, the method-by-method routes, and the triggers for review. The screen shows the current state of a specific withdrawal. The FAQ can point at both; it can answer neither.
For a bonus question, the binding answer is the promotion's own terms. Those terms state the wagering multiple, the game contribution rates, the time limit, and the maximum bet while a bonus is active. The FAQ can say that such terms exist; it cannot state their values, because the values differ from one promotion to the next.
For an account question — verification, restriction, closure, self-exclusion — the binding answer is in the account section of the operator's site and in the messages the operator has sent. The FAQ can list the documents accepted for verification and the general grounds for restriction. It cannot say what has happened to this account.
Reading the FAQ without being misled by it
The reader who wants the FAQ to serve them should read it as a map of the operator's documents, not as the documents themselves. When the FAQ says a thing exists, the next step is to find the page where that thing is stated and read the current value there. When the FAQ is silent on a value, the silence is itself information: it means the value is account-specific or promotion-specific, and the FAQ is not the place to look.
A useful habit is to note the date. Many operator FAQs carry no visible revision date, which means the reader cannot tell whether an answer is current. Where a date is present, it applies to the FAQ page, not to the documents it summarises. The terms may have changed after the FAQ was last edited. The only way to be certain is to open the underlying document and read it.
The same habit applies to screenshots and quoted figures in third-party reviews. A review written six months ago may quote an FAQ answer that has since been removed. The operator's own site is the only version that counts, and it is the only version the reader can hold the operator to.
What the FAQ page is not
An FAQ is not a substitute for the terms and conditions. It is not a record of the reader's account. It is not a channel for resolving a specific dispute. It is not a guarantee that a process will complete within a stated time. It is not a licence certificate, an audit report, or a fairness statement. Each of those things has its own page, and the FAQ's only role is to say that the page exists.
The reader who needs a binding answer should go to the document that owns the rule, read the current value there, and keep a record of what they read and when. The FAQ is the signpost, not the destination.
FAQ
Can I rely on an FAQ answer if it conflicts with the terms and conditions?
No. The terms and conditions are the binding document. If the FAQ summarises a rule differently from the way the terms state it, the terms govern. The reader has no claim based on having read the FAQ summary.
Why does the FAQ not tell me why my withdrawal is pending?
Because the reason is specific to your account and your withdrawal. The FAQ can list the generic causes, but the actual cause is shown on your withdrawal screen or in the message the operator sent when you submitted the withdrawal.
How do I find the current wagering requirement for a bonus?
Open the promotion's own terms, not the general FAQ. Each promotion carries its own wagering multiple, game contribution rates and time limit, and those values are revised between campaigns. The FAQ will not state them.
Does the FAQ tell me which payment methods I can use?
It may list the methods the operator generally supports, but the methods available to you depend on your country, currency and account status. The cashier, after login, shows the methods available to your account.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Allstargames, and it states no figure or status for that operator — the operator's own pages are the only binding source for any value that matters.
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.
