The page a reader opens when something has already gone wrong
Most readers do not arrive at an operator's FAQ out of curiosity. They arrive because a deposit has not appeared, a withdrawal is sitting in a state they do not recognise, a document has been rejected, or a bonus did not behave the way the promotion page seemed to promise. The FAQ is the first place they look, and the first place they learn what kind of answer they are going to get. An operator FAQ is a collection of short, standardised answers to the questions the operator expects to receive most often. It is written before the reader's specific problem exists, which means it can only ever answer questions that are the same for every reader. The moment a question depends on the reader's own account, the FAQ stops being able to answer it, and the reader needs to know that boundary before they waste an hour looking for an answer that is not there.
What an FAQ can answer bindingly is process: which steps a withdrawal goes through, which documents the verification team typically asks for, which deposit routes exist as a category, what happens when a bonus is claimed. What it cannot answer is anything that depends on the state of one particular account. Why is my withdrawal still pending? That depends on the reader's verification status, the method they chose, the amount, and the operator's current queue. The FAQ can explain what "pending" means as a status and which factors move it forward; it cannot tell this reader why theirs is pending. The reader's own account area, the cashier, and any message the operator has sent them are the only places that answer exists. The FAQ is a map of the operator's processes, not a diagnosis of the reader's situation.
Which questions the FAQ answers, and which it does not
The line that divides an answerable FAQ question from an unanswerable one is whether the answer is the same for every reader. "What documents do I need to verify my account?" is answerable, because the list of acceptable document types is the same for everyone: a government-issued ID, a recent utility bill or bank statement, sometimes a photo of the payment card. "Why was my document rejected?" is not answerable by the FAQ, because the reason is specific to the document the reader uploaded: the name did not match, the address was out of date, the image was cropped, the document expired. The FAQ can list the common rejection reasons; it cannot say which one applies to this reader. The operator's message about the rejection, or the verification screen in the account area, carries that answer.
The same split runs through every topic an FAQ covers. Deposit questions are answerable when they are about routes and limits as categories; they are not answerable when they are about a specific missing deposit. Withdrawal questions are answerable when they are about the sequence of steps and the meaning of statuses; they are not answerable when they are about why this withdrawal has not moved. Bonus questions are answerable when they are about how wagering works as a mechanism; they are not answerable when they are about whether this reader has met the requirement. Game questions are answerable when they are about rules and how a round resolves; they are not answerable when they are about a specific disputed round. The reader who understands this split stops expecting the FAQ to be a support ticket and starts using it as what it is: a reference for the rules that apply to everyone.
| Question type | What the FAQ can state | What the FAQ cannot state | Where the binding answer lives |
|---|---|---|---|
| Deposit routes | Which categories of payment method exist, and the general steps for each | Whether a specific method is available to this reader, or why a deposit has not arrived | The cashier in the reader's account, and the deposit history screen |
| Withdrawal steps | The sequence from request to release, and what each status means | Why this reader's withdrawal is at a particular status, or when it will clear | The withdrawal screen, and any message from the operator |
| Verification documents | The categories of documents accepted, and the common rejection reasons | Which document this reader should upload, or why theirs was rejected | The verification screen, and the operator's rejection notice |
| Bonus terms | How wagering, eligible games, and expiry work as mechanisms | Whether this reader has met the requirement, or how much is left | The bonus terms page, and the bonus progress display in the account |
| Game rules | How a round resolves, what the paytable means, and what the house keeps | Whether a specific round was resolved correctly, or what happened in one session | The game's own rules and paytable, and the game history log |
| Account closure | The steps to request closure, and what closure means for a balance | Whether this reader's account can be closed, or what will happen to their specific balance | The responsible gambling tools, and the operator's confirmation message |
What changes between the FAQ and the page that governs it
An FAQ is a summary, and a summary is the first thing to go stale. The operator's terms and conditions page, its promotion terms, its withdrawal policy, and its privacy policy are the documents that bind the operator and the reader. The FAQ is a convenience layer on top of them, written in plainer language and organised by question rather than by clause. When the two disagree, the underlying document wins, and the reader should assume the underlying document is the more current of the two. An FAQ may say a withdrawal is processed within a certain window, but the withdrawal policy may have been updated to a different window; the FAQ may describe a bonus wagering requirement that the promotion terms have since changed. The reader who reads only the FAQ is reading a paraphrase of a document that may have moved on.
This is not a flaw unique to any one operator. It is the nature of a summary. The FAQ is maintained by a different team, on a different schedule, than the legal and compliance documents it summarises. The reader's protection is to treat the FAQ as a starting point and the underlying page as the authority. When the FAQ states a figure, a timeframe, a limit, or a document list, the reader should find the page that governs that item and read the figure there. If the two differ, the governing page is the one the operator will point to in a dispute. If the FAQ does not state a figure at all, that is itself information: the reader should not assume a default exists, and should read the governing page before acting.
Some items in an FAQ are stable because they are structural: the sequence of a withdrawal, the categories of accepted documents, the meaning of a status. Other items are unstable because they are commercial or regulatory: the specific payment brands offered, the limits applied to a method, the wagering multiple on a bonus, the processing window. The reader can usually tell which is which by asking whether the item could change without the operator rewriting its whole FAQ. A payment brand can be added or removed; a withdrawal sequence cannot. A bonus percentage can be changed; the fact that a bonus must be wagered cannot. The stable items are safe to read from the FAQ. The unstable items should always be confirmed on the page that owns them.
Reading the FAQ against the reader's own account
The most common misreading of an FAQ is to treat it as a personalised answer. A reader sees "withdrawals are processed within two business days" and concludes their withdrawal will clear in two business days. But the FAQ is describing the operator's process in general, not this reader's withdrawal in particular. The reader's withdrawal may be subject to verification that has not been completed, to a payment method that clears more slowly, to a weekend or public holiday, to an amount that triggers additional review, or to a queue that is longer than usual. None of those factors is knowable from the FAQ. The reader's own withdrawal screen is the only place that shows the current status and any action the reader needs to take.
The same applies to every other account-specific question. A reader who wants to know whether their document was accepted must look at the verification screen, not the FAQ's list of accepted document types. A reader who wants to know how much of a bonus wagering requirement remains must look at the bonus progress display, not the FAQ's explanation of how wagering works. A reader who wants to know why a deposit has not arrived must look at the deposit history and any message from the operator, not the FAQ's description of deposit processing times. The FAQ tells the reader what the process is; the account area tells the reader where they are in it. Confusing the two is the single most common source of frustration with any operator's help pages.
There is one exception to this rule, and it is worth stating plainly. When the FAQ describes a control the reader can exercise themselves, the FAQ is the answer. A self-exclusion request, a deposit limit, a cooling-off period, a session reminder: these are tools the reader sets, and the FAQ's description of how to set them is accurate for every reader. The reader does not need the operator to confirm that the tool exists or how it works; the reader needs only to find the control in their account and set it. The FAQ is the right place to learn that these controls exist and where they live. The one thing the FAQ cannot do is set the control for the reader, or undo it once set. A self-exclusion, in particular, is not reversible on request, and the reader should read the responsible gambling page before using it.
Where the FAQ stops and the binding answer begins
Every FAQ has a boundary, and the reader who can see it is better off than the reader who cannot. The FAQ answers questions about process, routes, document lists, and the meaning of statuses. It does not answer questions about this reader's account, this reader's withdrawal, this reader's document, or this reader's bonus. The binding answer to a process question is the governing page: the terms and conditions, the withdrawal policy, the promotion terms, the privacy policy. The binding answer to an account question is the account area itself: the cashier, the verification screen, the bonus progress display, the deposit and withdrawal history. The binding answer to a dispute is the operator's support channel, and ultimately the operator's complaint procedure.
A reader who wants to use the FAQ well should read it in this order. First, read the FAQ entry for the topic, to learn the shape of the process and the vocabulary the operator uses. Second, read the governing page the FAQ summarises, to confirm the figures and conditions that apply. Third, open the account area and read the specific state of their own account. Fourth, if the account area does not answer the question, contact support with the specific facts: the date, the amount, the method, the status, the document. The FAQ cannot replace any of these steps, but it makes each of them faster, because the reader arrives knowing which words to use and which page to open. That is what an FAQ is for.
This page is an independent summary of what an operator FAQ covers and where it stops. It is not published by Bonanza, and it states no figure or status for them; the operator's own FAQ and the pages it summarises are the only binding source for what Bonanza states.
FAQ
Can the Bonanza FAQ tell me why my withdrawal is still pending?
No. The FAQ can explain what the pending status means and which factors commonly move a withdrawal forward, but the reason a specific withdrawal is pending depends on the reader's own account: verification status, payment method, amount, and the operator's current queue. The withdrawal screen in the reader's account and any message from the operator are the only places that answer exists.
Should I trust the figures in the FAQ, or the figures on the terms page?
The terms page. An FAQ is a summary, and summaries go stale faster than the documents they summarise. When the FAQ and the governing page differ, the governing page is the one the operator will point to in a dispute. If the FAQ does not state a figure at all, the reader should not assume a default exists.
What can the FAQ tell me about verification documents?
The FAQ can list the categories of documents the operator typically accepts, such as a government-issued ID and a recent utility bill or bank statement, and the common reasons a document is rejected. It cannot say which document this reader should upload, or why a specific document was rejected. The verification screen and the operator's rejection notice carry that answer.
Is the FAQ the right place to learn about self-exclusion?
Yes, for learning that the control exists, how it works, and where it lives in the account. The FAQ describes the tool accurately for every reader. What it cannot do is set the control for the reader, or undo it once set. A self-exclusion is not reversible on request, and the reader should read the responsible gambling page before using it.
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.
