The reader arrives with one question and leaves with another
A player opens an operator's FAQ page because something has gone slightly wrong, or is about to. A deposit did not arrive. A withdrawal is stuck on "pending". A document was rejected. The FAQ is the first place anyone looks, and the place where the answer is most likely to be half an answer. The reason is structural: an FAQ is written for the average reader, but the question the player has is about their own account, their own amount, their own jurisdiction. The page can tell them what the process is. It cannot tell them what the process will do to them today.
That is the distinction the whole page turns on. Zombillion2's FAQ, like every operator FAQ, is a map of the operator's standard procedures. It names the routes money takes, the documents verification asks for, the order in which steps happen. What it cannot do is bind the operator to a specific outcome for a specific reader at a specific moment. The FAQ describes the machine. The reader's own account page, and the terms linked from it, describe the machine's current settings.
What an FAQ can settle: process, routes, document lists
An FAQ is at its most reliable when it answers questions that have the same answer for every reader. These are questions about process, not about outcome. The reader can learn from the FAQ what deposit methods exist, what the general flow of a withdrawal is, which documents are commonly requested for verification, and where to find the pages that carry the current figures for each of those things.
The key word is "where". A well-built FAQ does not restate the wagering multiple or the withdrawal minimum; it points to the promotions terms or the cashier page where that number is printed. The FAQ itself is a directory, not a ledger. When a reader reads a figure inside an FAQ answer, that figure is a snapshot. It may be correct today and wrong next week. The only place a figure is binding is the page that owns it: the terms page for a wagering requirement, the cashier for a deposit minimum, the withdrawal policy for a processing window.
This means the reader should treat every FAQ answer as a pointer to a source, not as the source itself. The sentence "see the withdrawal policy for current processing times" is the most useful sentence an FAQ can contain. The sentence "withdrawals take two days" is the most dangerous, because it will be read as a promise and remembered long after it has been changed.
What an FAQ cannot settle: anything that depends on the reader's account
The moment a question contains the word "my", the FAQ stops being able to answer it. "Why is my withdrawal pending?" "Why was my document rejected?" "Which bonus applies to my deposit?" These are the questions players type, and they are precisely the questions no FAQ can answer, because the answer is stored in the reader's account, not in the operator's standard procedures.
A withdrawal may be pending because the account has not completed verification, because the amount exceeds a threshold that triggers a manual review, because the chosen method has a different clearing time, or because the operator's risk team has flagged the transaction. The FAQ can list all four possibilities. It cannot say which one applies to this reader. That answer lives in the account's withdrawal history, in the verification status panel, and in any message the operator has sent. The reader who asks the FAQ "why is my withdrawal pending" is asking the wrong page. The right page is their own account.
The same holds for document rejection. An FAQ can list the reasons a document is commonly rejected: it is expired, the name does not match, the image is cropped, the address is older than the operator accepts. It cannot say which reason applied to the reader's document. That answer comes from the rejection notice itself, which is the one message the operator sends that is specific to the reader.
This is not a defect in the FAQ. It is the FAQ's design. A page written for everyone cannot contain an answer that is true for only one person. The reader who understands this stops expecting the FAQ to solve their case and starts using it as the index it is.
The items that change, and where the current value is stated
Every FAQ carries a small number of items that are both important and unstable. These are the items the reader should never take from the FAQ, because the FAQ's version is the one most likely to be out of date. The table below lists the items, why they change, and the page that carries the binding value.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit minimum and maximum | Operators adjust limits by method, currency and player status; a figure in an FAQ is a snapshot | The cashier page for the chosen method, or the deposit terms |
| Withdrawal processing window | Depends on verification status, amount, method and current queue; not a fixed promise | The withdrawal policy page, and the account's withdrawal history |
| Wagering requirement on a bonus | Each promotion carries its own multiple; the FAQ may state a range, not a value | The specific promotion's terms, linked from the offer itself |
| Verification documents requested | Varies by jurisdiction, deposit method and risk assessment; the list can expand | The verification request sent to the reader's account, and the KYC page |
| Self-exclusion and cooling-off options | Tool availability and duration options differ by market and regulatory requirement | The responsible gambling page and the account settings |
| Supported payment methods | Methods are added and removed by region; an FAQ list ages quickly | The cashier, filtered by the reader's country and currency |
The pattern is consistent: the FAQ tells the reader that a thing exists and roughly how it works. The page that owns the thing tells the reader what it currently is. A reader who copies a figure from an FAQ into their planning is planning on a rumour.
The FAQ as a directory, not a ledger
The most useful way to read any operator FAQ is as a table of contents for the operator's binding pages. Each FAQ answer should be mined for two things: the name of the page that owns the topic, and the name of the process that governs it. The actual number, limit, window or requirement is then read off that page, at the moment the reader needs it, not before.
This has a practical consequence. If the FAQ answers a question but does not name the page where the binding value lives, the reader has not been answered; they have been deflected. A sentence like "withdrawal times vary" without a pointer to the withdrawal policy is not an answer. A sentence like "see the withdrawal policy for current processing times" is. The reader should judge every FAQ answer by whether it ends in a pointer. If it does not, the answer is incomplete, and the reader should go looking for the page themselves.
The same test applies in reverse. If the FAQ names a page but that page does not state the figure the reader needs, then the figure is not published, and the reader cannot know it in advance. That absence is itself information. It means the operator will state the figure only inside the reader's account, at the moment it applies. A withdrawal limit that is not published anywhere is a limit the reader discovers by attempting the withdrawal.
When the FAQ and the terms page disagree
FAQ pages are maintained by a different team than terms pages, and they are updated on a different schedule. The result is that an FAQ can carry a figure that the terms page changed weeks ago. When a reader finds a conflict, the rule is simple: the terms page wins. The FAQ is a summary; the terms are the contract. No operator will honour an FAQ answer against its own terms, and no reader should expect it to.
The reader who spots a conflict has two options. They can act on the terms page, which is the safe course, or they can contact the operator and ask which version applies. The second course produces a written answer, which is useful if the operator later takes a different position. But the reader should not act on the FAQ version while the conflict is unresolved. The FAQ is not a promise; it is a description of a promise that lives elsewhere.
This is why the FAQ's own caveats matter. Many operator FAQs contain a line stating that the terms and conditions prevail in any conflict. That line is not boilerplate; it is the operator telling the reader which page is authoritative. The reader who skips it is choosing to rely on the wrong document.
FAQ
Can an FAQ answer tell me why my withdrawal is pending?
No. An FAQ can list the common reasons a withdrawal is held — verification incomplete, amount above a review threshold, method-specific clearing time — but it cannot say which reason applies to a specific account. The reader's own withdrawal history and any message from the operator carry the specific answer.
Where is the binding version of a bonus wagering requirement?
On the specific promotion's terms page, linked from the offer itself. An FAQ may describe wagering requirements in general, but the multiple that applies to a particular bonus is stated only in that bonus's own terms, and it can differ between promotions.
What should I do if the FAQ and the terms page give different figures?
Act on the terms page. It is the binding document, and an FAQ is a summary that may be out of date. If the conflict matters, the reader can ask the operator in writing which version applies, but the safe course is to treat the terms page as authoritative.
Does the FAQ tell me which documents I will need for verification?
It can tell you which documents are commonly requested, but not which ones will be requested from you. The specific list depends on the reader's jurisdiction, deposit method and risk assessment, and it arrives in the verification request sent to the account.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Zombillion2 and it states no figure or status for them, and the operator's own FAQ and the pages it links to 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.
