The reader arrives at an operator FAQ because a specific process has stalled: a deposit did not appear, a withdrawal is pending, a document was rejected, or a game rule is unclear. The first thing to understand is what that page can and cannot do. An FAQ is a set of prepared answers to recurring questions. It is not a contract, not a live support ticket, and not a statement about the reader's own account. It describes how the operator's processes are designed to work in general. Whether they worked that way in a particular case is a different question, answered only by the account record and by support.
The decision an FAQ helps with
The reader is not deciding whether to trust the operator. The reader is deciding which of their questions can be settled by reading a prepared page, and which require a different action: checking the account, reading the terms, or opening a support conversation. The FAQ helps most when the question is about a route or a document list. It helps least when the question is about a number, a deadline, or a status. A reader who expects the FAQ to state the current withdrawal time for their method, or the exact bonus wagering multiple applying to their account, is reading the wrong page. The FAQ may point to the right page; it will not usually restate the figure, because figures change and the FAQ is the page least likely to be updated the same day.
What an operator FAQ normally governs
Across operators, an FAQ covers the mechanics of ordinary account actions. The typical sections are:
- how to open and close an account;
- which documents are accepted for identity verification, and in what format;
- which deposit methods exist and how a deposit is initiated;
- how a withdrawal is requested, and what happens between request and release;
- basic game rules and where full rules are published;
- what to do when a login fails or a document is rejected.
None of these answers is personal. The FAQ says what the operator accepts in general. It does not say what the operator accepted from this reader, or what will happen to this reader's pending request. That distinction runs through every section.
Where the FAQ stops being binding
Three kinds of question fall outside what an FAQ can answer bindingly, no matter how clearly the page is written.
First, anything that depends on the current terms. A bonus percentage, a wagering multiple, a minimum deposit, a fee, a maximum withdrawal — these are terms, and terms are amended. An FAQ written six months ago may describe a route that still exists but a figure that no longer applies. The binding source for a figure is the page where the operator publishes its current terms, not the FAQ.
Second, anything that depends on the account. Whether a document was accepted, whether a withdrawal passed review, whether a bonus was credited, whether a self-exclusion is active — these are states of one account. The FAQ cannot know them. The reader sees them in the account record, in the cashier, or in the message the operator sent.
Third, anything that depends on the operator's current policy toward a jurisdiction, a payment brand, or a game provider. An FAQ may say that withdrawals are processed by bank transfer, but whether bank transfer is available to this reader, from this country, right now, is a live question. The cashier shows the methods available to the account; the FAQ shows only the methods the operator has offered at some point.
What to confirm on an FAQ page
The useful reading of an FAQ is not to memorize its answers but to identify which items on it are process descriptions and which are references to other pages. The table below separates the items a reader can confirm from an FAQ, the reason each item can change, and where the current value is stated.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Compliance requirements change; the operator may add or remove accepted formats | The verification or KYC page, and the upload screen itself |
| Deposit methods | Payment providers are added and removed; availability varies by country | The cashier, which shows only methods available to the logged-in account |
| Withdrawal routes | A route may be closed for a method, a country, or a verification level | The withdrawal screen, after login |
| Bonus eligibility rules | Promotions are amended, replaced, or ended | The promotions terms page, which carries the current version |
| Minimum and maximum amounts | Limits are adjusted without notice to the FAQ | The cashier or the terms page, at the moment of the transaction |
| Withdrawal processing time | Processing depends on method, verification status, and volume | The withdrawal policy page, and the status shown on the pending request |
| Game rules | Rules are fixed per game, but variants differ across titles | The game's own rules panel, inside the game client |
Each row answers a different kind of reader question. The document list answers "what do I need to prepare". The cashier answers "what can I do right now". The terms page answers "what number applies". The FAQ is the index to these, not a substitute for any of them.
What it means when the FAQ does not state an item
An absence on an FAQ page is information. If the FAQ does not name a withdrawal route for a deposit method, the reader cannot assume the route exists. If the FAQ does not state a processing time, the reader cannot assume a time. If the FAQ does not list accepted documents, the reader should not upload anything until the verification page or a support reply confirms the list. An FAQ that is silent on a point is not evidence that the point is unimportant; it is evidence that the point is handled elsewhere, or that the operator has chosen not to publish it in a prepared answer.
The same applies to the reader's own account. An FAQ that describes a standard verification flow does not mean the reader's account has passed verification. An FAQ that describes a standard withdrawal flow does not mean the reader's withdrawal will follow it. The account status is the only place the individual outcome is visible, and the support channel is the only place the individual outcome can be questioned.
Reading the FAQ against the terms
The most common misreading is to treat the FAQ as a promise. A reader who sees "withdrawals are processed within a certain number of business days" in an FAQ and then waits longer has not been lied to; they have read a general description as a personal guarantee. The terms page and the withdrawal policy page carry the operator's current obligations. The FAQ carries a summary that may lag behind them. When the two conflict, the terms page wins, because it is the document the operator updates when a policy changes. The FAQ is updated when someone remembers to update it.
For the reader, the practical rule is: use the FAQ to learn which page governs the question, then read that page. If the FAQ says verification requires a photo ID, open the verification page and read the accepted list there. If the FAQ says withdrawals go back to the deposit method, open the cashier and see what the withdrawal screen offers for the account. The FAQ is a map, not the territory.
Account-specific questions the FAQ cannot answer
Several of the questions a reader most wants answered are precisely the ones an FAQ is structurally unable to answer. These include:
- Why was my document rejected? The FAQ can list common reasons; it cannot see the uploaded file.
- Where is my withdrawal? The FAQ can describe the stages; it cannot see the current stage of a particular request.
- Why was my deposit not credited? The FAQ can describe how deposits are credited; it cannot see the payment provider's confirmation.
- Am I eligible for this bonus? The FAQ can state general eligibility rules; it cannot see whether the account meets them.
For each of these, the answer lives in the account record or in a support conversation. The FAQ's value is to tell the reader what information to have ready before opening that conversation: the transaction reference, the document type, the date, the method. A reader who reads the FAQ before contacting support asks a better question and gets a faster answer.
What changes and what stays fixed
On an FAQ page, the stable content is the description of how a process works: what a verification review checks, what a withdrawal request triggers, what a self-exclusion does. The unstable content is every number attached to those processes: how long a review takes, how much a withdrawal costs, what percentage a bonus adds, what minimum a deposit requires. The reader can rely on the mechanism descriptions. The reader must re-check every figure on the page that governs it, at the moment the figure matters.
This split is not a defect of the FAQ. It is the nature of a prepared answer. A process description ages slowly; a figure ages quickly. The operator knows this, which is why the figures live on pages built to be updated, and the FAQ links to them rather than restating them. A reader who understands that split stops expecting the FAQ to be current and starts using it as the index it is.
FAQ
Can I rely on the FAQ for the current withdrawal time?
No. The FAQ may describe a typical processing flow, but the current time for a specific method and a specific account is stated on the withdrawal policy page and on the pending request itself. Read the FAQ to learn which page governs, then read that page.
Does the FAQ tell me which documents are accepted for verification?
It may list common examples, but the accepted list is set by the verification page and the upload screen. If the FAQ and the upload screen differ, the upload screen is the one that matters, because it is the gate the document must pass.
Why does the FAQ not state the bonus wagering multiple?
Because the multiple is a term, and terms are amended. The FAQ is a general help page, not a terms page. The current multiple is on the promotions terms page for the specific bonus, and it is the only binding statement of it.
What should I do when the FAQ does not answer my question?
Check the account record and the cashier first, because many account-specific answers are visible there. If the question remains, contact support with the transaction reference, date, and method ready. The FAQ is a starting point, not a substitute for the account or for a support reply.
This page is an independent summary of what an operator FAQ page covers and where its limits lie; it is not published by pushgaming.com, and it states no figure or status for them — the operator's own FAQ and the pages it links to are the only binding sources for their current processes and terms.
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.
