A player opens an FAQ page because something is stuck: a deposit has not appeared, a withdrawal is pending, a document was rejected, or a bonus did not credit. The page looks like it should solve the problem. What it does is narrower. An FAQ answers the questions that have one answer for every account. The moment the answer depends on the reader's balance, history, location, or verification state, the FAQ stops being able to help, and the reader is really looking for a different page.
The split between what an FAQ can and cannot settle
Every operator FAQ is built on the same division. On one side are questions about process: which menu opens the cashier, what a routing number is, what file formats the verification team accepts, how long a self-exclusion request takes to register. These have a single correct answer, and the FAQ can state it bindingly. On the other side are questions about a specific account: why this deposit is missing, whether this withdrawal will clear, whether this document is sufficient, why this bonus was not applied. The FAQ cannot answer any of those, because the answer is computed from data the FAQ does not have.
That division is not a weakness of the page. It is the page doing its job. A well-built FAQ tells the reader which questions it can answer and which ones require the account area, the cashier, or the support team. A reader who treats the FAQ as the final word on an account-specific matter will misread it. The FAQ describes the rule; the account area applies the rule to one reader.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit methods available | Payment routes are added and removed by region and provider | Cashier or deposit page, not the FAQ |
| Withdrawal processing steps | The sequence is fixed, but the time per step varies by method and verification state | Withdrawal policy page and the cashier status screen |
| Document formats accepted for KYC | Accepted file types and size limits are updated as the verification system changes | Verification or account page, sometimes the FAQ's document list |
| Bonus eligibility rules | Promotion terms are revised between campaigns | Promotions terms page for the specific offer |
| Self-exclusion and cooling-off options | The available durations and the effect on pending withdrawals are set by policy | Responsible gaming page and the account settings |
| Currency and conversion handling | Conversion rates move continuously; the operator's rate may differ from the reader's bank rate | Cashier at the moment of the transaction |
Process questions the FAQ is built to answer
Process questions are the FAQ's home ground. These are questions where the answer does not depend on who is asking. What documents does verification require? The list is the same for every new account. How does a withdrawal reach the reader? The route is the same for every withdrawal using that method. What happens when a deposit fails? The retry and reversal procedure is the same for every failed deposit of that type.
For these questions, the FAQ can be read as a binding statement. If the FAQ says a withdrawal must be made to the same method used for the deposit, that is a rule the reader can rely on. If the FAQ says a utility bill must be less than three months old, that is the standard the verification team applies. The reader should still check the date on the FAQ, because process answers change when the operator changes its systems or policies. But at any given moment, the process answer in the FAQ is the answer the operator will apply.
Account-specific questions the FAQ cannot touch
The second group is where readers get into trouble. "Why is my withdrawal still pending?" is the most common question any casino receives. The FAQ cannot answer it. The answer depends on whether the reader has passed verification, which method they used, whether the amount triggers a review, and what the payment provider is doing. None of that is in the FAQ. The FAQ may list the reasons a withdrawal can be delayed, but it cannot say which reason applies to this reader.
The same is true for "why was my document rejected?" The FAQ can list the common causes: blurry image, expired document, name mismatch, unsupported format. It cannot say which cause applies to a specific rejection. The rejection notice in the account area says that. The reader who reads the FAQ's list and assumes their document failed for the first reason on the list is guessing. The binding answer is in the account message, not in the FAQ's general list.
Bonus questions sit in the same place. The FAQ can explain what a wagering requirement is and how it is calculated in general. It cannot say whether a specific bonus has been credited, forfeited, or voided. That depends on the promotion's terms and on the reader's actions. The FAQ's general explanation is useful background; the promotion's own terms page is the binding document.
Where the binding answer lives
For every question the FAQ cannot answer, there is a page that can. The reader's job is to know which page that is. Deposit and withdrawal questions are answered by the cashier, which shows the status of each transaction. Verification questions are answered by the account area, which shows the list of required documents and the status of each one. Bonus questions are answered by the promotion's terms page, which is the only place the wagering multiple, the eligible games, and the expiry are stated for that specific offer.
The FAQ is best understood as a map to those pages, not a replacement for them. A good FAQ entry says: here is the rule, and here is where you see how it applies to you. The reader who skips the second half of that sentence and treats the FAQ's general statement as their specific answer will make decisions on the wrong information.
What changes and what stays fixed
Some FAQ content is stable. The explanation of what a wagering requirement is does not change from month to month. The definition of a self-exclusion period does not change. The list of document categories for verification is fairly stable. These are the parts of the FAQ a reader can rely on over time.
Other content moves. Deposit methods change when payment providers are added or dropped. Withdrawal timeframes change when the operator changes processors. Bonus rules change with every campaign. Document format requirements change when the verification system is updated. The FAQ may be updated to reflect these changes, or it may lag behind them. The reader should treat any figure read from an FAQ as current only as of the date on the page, and should confirm it against the page that governs the transaction.
One specific risk deserves attention: an FAQ that states a withdrawal timeframe. Across operators, withdrawal processing commonly ranges from a few hours to several business days, and the FAQ may repeat a figure from the operator's policy page. If the policy page changes and the FAQ does not, the FAQ is wrong. The reader should always read the figure from the withdrawal policy page, not from the FAQ, because the policy page is the one the operator updates when the process changes.
Reading the FAQ without over-reading it
The practical skill is to separate the two kinds of answer while reading. When the FAQ states a rule in general terms, the reader can take it as the rule. When the FAQ explains what might have happened, the reader should treat it as a list of possibilities, not a diagnosis. When the FAQ gives a timeframe or a limit, the reader should check the governing page before acting on it.
That discipline matters most when money is moving. A reader who withdraws to a method because the FAQ listed it as available, when the cashier no longer offers it, will have the withdrawal returned. A reader who sends a document in a format the FAQ listed, when the verification system now requires a different one, will have the document rejected. The cost of reading the FAQ as current is a failed transaction and a delay. The cost of checking the governing page is a minute.
This page is an independent summary of what an operator FAQ covers, not published by Gainflake, and it states no figure or status for them; the operator's own FAQ and the pages it points to are the only binding sources for any specific answer.
FAQ
Can the Gainflake FAQ tell me why my withdrawal is pending?
No. The FAQ can list the common reasons a withdrawal is held or delayed, but it cannot say which reason applies to a specific withdrawal. The cashier or withdrawal status screen in the account area shows the current state of each withdrawal and any action required.
Should I trust the deposit methods listed in the FAQ?
Only as a general guide. Payment methods are added and removed by region and provider, and the FAQ may not reflect the latest change. The cashier at the moment of deposit is the only place that shows which methods are available to a specific account.
Does the FAQ's explanation of a bonus apply to my bonus?
The FAQ can explain what a wagering requirement is and how it works in general. The specific terms for a bonus—the multiple, the eligible games, the expiry—are on the promotion's own terms page, and that page is the binding one.
What should I do when the FAQ and the cashier disagree?
Follow the cashier. The FAQ is a general reference and may lag behind changes to the operator's systems or policies. The cashier, the account area, and the terms pages are the live sources; the FAQ is secondary to all of them.
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.
