The page a player opens when something has already gone wrong
Most readers arrive at an operator's FAQ not from curiosity but from a stalled process. A deposit has not appeared, a withdrawal is sitting in a pending state, a document was rejected, or a bonus did not credit. The FAQ is the first place a player looks for an answer, and its structure reflects that: it is organized around the moments when money or account access stops moving. Understanding what an FAQ is built to do — and what it is structurally unable to do — changes how a reader uses every answer on it.
An FAQ is a collection of short, standardized responses to recurring questions. It is written once and read thousands of times. That means every answer on it is a general statement about how the operator's processes are supposed to work for a typical account. It is not a statement about any particular reader's account. The distinction matters more than almost anything else on the page.
What an FAQ can answer bindingly
An FAQ is strongest when it describes a process that does not depend on the reader's individual circumstances. These are the answers a player can take as reliable, because they describe the operator's own procedures rather than a promise about an outcome.
The first category is document lists. When an FAQ says which identity documents are accepted for verification, that is a stable statement. The list of acceptable documents — a passport, a national identity card, a driving licence, a recent utility bill — does not change from one account to the next. A reader can gather those documents before starting verification and expect them to be usable.
The second category is route availability. An FAQ can state which withdrawal methods the operator offers in general, and which deposit methods have a corresponding withdrawal route. This is a statement about the operator's payment infrastructure, not about the reader's balance. It holds for every account.
The third category is sequence. An FAQ can describe the order of steps in a process: verification before a first withdrawal, a wagering requirement completed before bonus funds become withdrawable, a self-exclusion request processed before account closure. Sequences are procedural facts, and the FAQ is the operator's own description of its procedure.
None of these answers requires the operator to know anything about the reader. That is what makes them binding. They are the closest thing an FAQ has to a guarantee, because they describe what the operator will ask for or offer, not what it will decide.
What an FAQ cannot answer, no matter how specific it sounds
The moment an answer depends on the reader's account, the FAQ stops being authoritative. It may still be useful as a guide to what typically happens, but it cannot settle the reader's actual situation.
The clearest example is a pending withdrawal. An FAQ may say that withdrawals are processed in a certain number of business days. That is a general statement about the operator's usual processing time. It does not tell the reader why their particular withdrawal is still pending, whether it has passed verification, or when it will clear. Those facts live in the reader's account, not in the FAQ.
The same applies to any question about a specific bonus. An FAQ can explain how wagering requirements work in general, and what counts as a qualifying bet. It cannot tell the reader how much of their own particular wagering requirement remains, or why their bonus was not credited. The answer to those questions is in the reader's bonus terms and transaction history, not in a general help page.
Account restrictions are another area where the FAQ is necessarily silent. If an account is limited, closed, or under review, the FAQ will not say why. It may list general reasons why accounts are reviewed, but it cannot identify the reason for a specific account. The reader's only route to that answer is the operator's support channel or the account notification itself.
Finally, an FAQ cannot override the terms and conditions. If the FAQ and the terms document disagree on a point — a fee, a limit, a processing window — the terms document is the binding source. The FAQ is a summary, and summaries can lag behind the document they summarize. A reader who relies on an FAQ answer that conflicts with the current terms has no claim based on the FAQ.
The hierarchy: where the binding answer lives
Every operator publishes multiple kinds of pages, and they do not all carry the same weight. Understanding where the FAQ sits in that hierarchy prevents a reader from treating a help page as a contract.
The terms and conditions are the base document. They define the relationship between the operator and the player, and they are the source every other page summarizes. When a dispute arises, the terms are what the operator points to. The FAQ is a convenience, not a substitute.
The promotions terms are a specific instance of the same principle. A bonus offer has its own terms, and those terms state the wagering multiple, the eligible games, the maximum bet during wagering, and the expiry window. The FAQ may describe wagering in general terms, but the specific numbers for a specific bonus are in the promotion's own terms page, not in the FAQ.
The payment policy or withdrawal policy page is where limits, fees, and processing windows are stated with the precision an FAQ usually avoids. An FAQ answer may say "withdrawals are processed within a few business days," while the payment policy states the exact window and any conditions that extend it. The payment policy is the binding source.
The privacy policy governs data questions. An FAQ may explain what data is collected and why in broad terms, but the privacy policy is the document that states the legal basis for processing, the retention period, and the reader's rights. A reader asking about data should read the privacy policy, not the FAQ summary of it.
This hierarchy has a practical consequence: when a reader needs a number, a limit, or a deadline, the FAQ is the wrong page. The right page is the one whose entire purpose is to state that number, limit, or deadline.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Document lists are stable, but an operator may add or remove accepted types as its compliance requirements change | The FAQ's verification section, or the account verification page reached from the cashier |
| Withdrawal processing window | Processing times vary by method, verification status, and current volume; a general FAQ answer cannot reflect the reader's specific queue position | The withdrawal policy or payment policy page, and the reader's own withdrawal status screen |
| Wagering requirement for a specific bonus | Each promotion carries its own multiple, eligible games, and expiry; these are set per offer and can change between offers | The specific promotion's terms page, not the FAQ's general explanation of wagering |
| Deposit and withdrawal method availability | Payment routes are added and removed as provider agreements change, and availability can vary by region | The cashier's deposit and withdrawal screens, which show only the methods currently available to the logged-in account |
| Account restriction or closure reason | Every restriction is account-specific and based on the reader's own activity, documents, or jurisdiction | The account notification, or the operator's support channel, never the FAQ |
| Data retention period | Retention periods are set by legal requirements the operator must follow, and they can change when those requirements change | The privacy policy, which states retention periods and the legal basis for processing |
When the FAQ does not state an item, that absence is an answer
A reader often treats a missing FAQ answer as a gap to be filled by asking support. But the absence itself carries information. If the FAQ does not state a processing window, the operator has chosen not to commit to one on a general help page. The reader should not infer a window from other operators' FAQs, and should not assume the absence means there is no window. It means the window is stated elsewhere, or is determined per account, or is deliberately not published.
The same applies to fees. If the FAQ does not mention a withdrawal fee, the reader cannot conclude that withdrawals are free. The fee schedule, if one exists, is on the payment policy page or shown in the cashier at the moment of withdrawal. An FAQ that is silent on fees is not evidence of their absence.
When the FAQ is silent on a topic the reader considers important, the correct move is to find the page whose job is to state that topic. The FAQ's silence is a signpost, not a dead end.
Reading an FAQ answer without overreading it
Every FAQ answer should be read with one question in mind: is this a statement about the operator's process, or a statement about the reader's account? If it is the former, it is reliable. If it is the latter, it is at best a general indication, and the reader's own account screens carry the truth.
A useful habit is to check the date or version of the FAQ if one is shown. An FAQ that has not been updated in a long time may describe processes that have since changed. The terms and conditions and the payment policy are more likely to be maintained, because they carry legal weight. The FAQ is a convenience page, and convenience pages are sometimes the last to be updated.
Another habit is to treat every FAQ answer as a summary of a more specific document. When the FAQ says "you may be asked for proof of address," the specific document is the verification policy. When it says "bonus funds are subject to wagering," the specific document is the promotion's terms. The FAQ points toward the binding source; it is not itself the binding source.
FAQ
Does the FAQ tell me why my withdrawal is still pending?
No. The FAQ can describe the operator's general processing sequence and the typical window, but it cannot see the reader's account. The reason a specific withdrawal is pending — verification incomplete, method-specific delay, or a review — is shown on the reader's withdrawal status screen or explained by support.
Can I rely on the FAQ's explanation of wagering requirements?
Only as a general explanation of how wagering works. The specific multiple, eligible games, maximum bet, and expiry for a particular bonus are stated in that promotion's own terms page. If the FAQ and the promotion terms disagree, the promotion terms control.
What should I do if the FAQ does not answer my question?
First, check the page whose job is to state the answer: the terms and conditions, the payment policy, the privacy policy, or the specific promotion's terms. If the answer is account-specific, such as a restriction reason or a pending withdrawal, the support channel is the only route to the binding answer.
Is the FAQ a legal document?
No. The FAQ is a help page that summarizes the operator's processes. The legal relationship between the operator and the player is defined by the terms and conditions, the privacy policy, and any specific promotion terms. The FAQ cannot override those documents.
What this page is and is not
This article is an independent summary of what an operator FAQ is for and where it stops, not a page published by Perx Getmybalance, and it states no figure or status for that operator — the operator's own FAQ and its underlying terms pages are the only binding sources for any specific answer.
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.
