A player opens an operator's FAQ because something has gone quiet: a deposit has not appeared, a withdrawal is sitting in a pending state, or a bonus has not unlocked the way the promotion page seemed to promise. The first thing to understand is what kind of page an FAQ is. It is a process document, not a contract and not a customer-service reply. It can tell a reader which steps exist, which documents are usually requested, and which route a request takes. It cannot tell that reader what will happen to their specific deposit, their specific withdrawal, or their specific account. The binding answer to those questions lives somewhere else, and part of reading an FAQ well is knowing where its authority stops.
The split every FAQ is built on
An operator FAQ is written for the average case. It describes the standard path: how a deposit is normally credited, what a withdrawal request normally requires, which verification documents are commonly asked for, how long a process usually takes across the industry. What it cannot do is describe this reader's case, because the operator's staff have not looked at that account when the FAQ was written. A FAQ can say that a withdrawal is released after verification; it cannot say whether this withdrawal has passed verification. A FAQ can say that a bank transfer is one of the routes that may appear in the cashier; it cannot say whether that route appears for this player, in this country, with this payment history.
That split matters because readers often treat a FAQ answer as a promise. If the FAQ says a document list includes a utility bill, a reader may believe that a utility bill is sufficient. In practice, the operator's risk team may ask for a bank statement as well, or a different document entirely, because the account has triggered a rule the FAQ does not mention. The FAQ describes the menu; the account review decides the order.
What a FAQ page can answer bindingly
There is a narrow set of questions where a FAQ is close to authoritative, because the answer does not depend on the reader's account and does not change from one hour to the next. These are questions about process architecture:
- What are the general steps from deposit to playable balance?
- Which categories of payment method exist, even if the specific brands are not named?
- What is the general order of a withdrawal: request, verification, processing, release?
- Which document types are commonly accepted for identity verification?
- What does a wagering requirement mean in principle, before any number is attached?
- Where in the account area a player finds their transaction history or bonus status?
For these, the FAQ can be read as a map of the operator's own systems. It tells the reader which screens exist, which buttons to press, and which team handles which step. That is useful, and it is the part of the FAQ that rarely goes stale.
What a FAQ page cannot answer
The other side of the page is where readers get into trouble. A FAQ cannot answer any question whose answer depends on the current state of one account. That includes:
- Whether a specific deposit has been credited, and if not, why not;
- Whether a specific withdrawal has been approved, and when the funds will arrive;
- Whether a bonus is active on this account, and what the remaining wagering is;
- Whether the account has passed verification, or what is still missing;
- Why a payment method that used to appear in the cashier is no longer listed;
- Whether a self-exclusion or limit applies to this account.
None of these can be answered by a static page. The FAQ may describe the general rule — for example, that a withdrawal is held until verification completes — but the specific instance is decided by the operator's back office, and the reader learns it from the cashier, the account messages, or a support reply, not from the FAQ.
The items that change without the FAQ changing
One of the least understood properties of an FAQ is that it can be out of date on the points that matter most, while still being the page the operator links from its footer. The reason is that some items are governed by documents that change on their own schedule, and the FAQ only summarises them. A promotions page can change a wagering multiple overnight; the FAQ may still describe the old one until someone edits it. A payment provider can be removed from the cashier; the FAQ may still list it as available. A regulator's document requirement can shift; the FAQ may still show the previous list.
This is not a defect unique to any one operator. It is a structural property of FAQ pages everywhere: they are secondary documents. The primary document is the terms page, the promotion page, the cashier itself, or the verification request in the account. When a reader needs a figure, a route, or a deadline, the FAQ is the wrong place to read it off. The right place is the screen or document that controls that item.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Withdrawal processing time | Depends on method, verification status, and current queue; FAQ often shows an outdated range | Cashier screen and withdrawal confirmation message |
| Wagering requirement multiple | Promotion terms change between campaigns; FAQ may lag behind | The specific promotion's terms section |
| Accepted document types for KYC | Risk rules and regulator expectations shift; FAQ lists a general set | The verification request in the account area |
| Available payment methods | Routes are added and removed by provider, region, and player history | The cashier, filtered by the logged-in account |
| Bonus eligibility rules | Depends on country, game, deposit method, and past bonus use | The promotion's eligibility clause and the account bonus panel |
| Self-exclusion and limit tools | Options vary by jurisdiction and account status | Responsible-gaming page and account settings |
Reading a FAQ as a map, not as a ruling
The useful way to read an operator FAQ is as a map of where things live. When the FAQ says that a withdrawal requires verification, the reader learns that there is a verification step, and that it happens before release. When the FAQ says that a bonus has wagering, the reader learns that a wagering condition exists and that it is attached to the promotion. When the FAQ says that a document list includes proof of address, the reader learns that proof of address is one of the categories the operator may request.
What the reader should not do is treat any FAQ sentence as a ruling on their own case. If the FAQ says a withdrawal is "usually" processed within a certain window, that is a description of the operator's general behaviour, not a promise about this withdrawal. If the FAQ says a document "may" be requested, that is a warning that it might be, not a guarantee that it will be. The words "usually", "may", "typically", and "in most cases" are doing real work in an FAQ. They are the operator's way of saying that the page describes the average, and the average is not the account.
Where the binding answer lives
For every question the FAQ cannot settle, there is a document or screen that can. The reader's task is to know which one applies:
- For a deposit or withdrawal that is stuck, the binding answer is in the cashier's transaction detail and in the account's message centre, not in the FAQ.
- For a bonus that has not unlocked, the binding answer is in the promotion's own terms, and in the bonus panel of the account, which shows remaining wagering and expiry.
- For a verification request, the binding answer is the list of documents in the account's verification section, which is generated for that account at that moment.
- For a payment method that has disappeared, the binding answer is the cashier as it appears when logged in, filtered by the player's region and history.
- For a rule about account closure or limits, the binding answer is the terms page and the responsible-gaming controls in the account settings.
The FAQ can point to these places, and a good one does. But the pointing is not the ruling. The ruling is made by the system that holds the account state.
What it means when the FAQ is silent
A silence in an FAQ is itself information. If the FAQ does not state a withdrawal timeframe, that is not an oversight; it is a decision not to commit to one in a static page, because the real answer depends on method and verification. If the FAQ does not name payment brands, that is because the available brands differ by region and account, and a static list would mislead. If the FAQ does not state a wagering multiple, that is because the multiple belongs to each promotion, not to the operator as a whole. If the FAQ does not name a testing laboratory or a regulator, that is because those are not process questions; they are status questions, and they are answered on the pages that carry those statuses.
A reader who finds a silence should not fill it with an assumption. The correct move is to go to the screen or document that would have to state the item if it existed. If the cashier does not show a withdrawal route for the deposit method used, the route is not available for that account at that time. If the promotion page does not state a multiple, the bonus may not exist in the form the reader thinks. The absence is the answer.
FAQ
Can I rely on the FAQ to know my withdrawal time?
No. The FAQ describes the general process, but the specific time for a specific withdrawal depends on the method, the verification state of the account, and the operator's current processing queue. The binding answer appears in the cashier and in the withdrawal confirmation message for that transaction.
Why does the FAQ not list the payment methods available to me?
Because the available methods depend on the reader's country, account history, and sometimes the deposit method already used. A static page cannot know those things. The cashier, when logged in, is the only place that shows the real list.
Where do I find the wagering requirement for a bonus?
On the promotion's own terms page, not in the FAQ. The FAQ may explain what wagering means, but the multiple, the eligible games, and the expiry are stated on the promotion page and in the bonus panel of the account.
What should I do if the FAQ says one thing and my account says another?
Trust the account. The account's screens are generated from live data; the FAQ is a static summary that may be out of date. If the two conflict, the account state and the operator's support reply are the binding sources.
This page is an independent summary of what an operator FAQ covers and where its authority stops; it is not published by Pommi, and it states no figure or status for them. Pommi's own FAQ and the screens it points to are the only binding sources for that operator's processes.
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.
