The Situation a Reader Brings to an FAQ
A player opens an operator's FAQ because something in their account is not moving the way they expected. A deposit has not appeared, a withdrawal is marked pending, a document was rejected, or a bonus did not trigger. The FAQ is the first place they look, and the most common mistake is to treat every sentence on it as a promise that applies to their account. It does not. An FAQ describes the operator's general process. It cannot see the reader's account, and it is not the document that decides what happens to their money.
The useful way to read a Free Games FAQ is as a map of where each decision gets made. Some questions the FAQ can answer bindingly, because the answer is the same for every account: which documents are accepted, which deposit routes exist, what the wagering multiple is for a given promotion. Other questions it can only point at, because the answer depends on the reader's own account or on terms that change: why a specific withdrawal is delayed, whether a specific document will pass, what bonus a specific account is eligible for. The skill is telling those two kinds of answer apart.
What an FAQ Can Answer Bindingly
An operator FAQ is written to be stable. The answers that are safe to treat as binding are the ones that do not change from one account to the next and do not change from one week to the next. Those are process answers and list answers.
Process answers describe the sequence a transaction goes through. A deposit moves from the cashier to the game balance; a withdrawal moves from the balance to a pending state, then to a cleared state, then to the payment route. The FAQ can state that sequence because it is the same for every player who uses that route. It can state which documents are accepted for verification, because the operator sets that list once and applies it to everyone. It can state the wagering multiple for a named promotion, because that number is printed in the promotion's own terms.
List answers are the other stable category. The FAQ can list the deposit methods the cashier supports, the withdrawal routes that are available, the file formats accepted for documents, the restricted territories. Those lists are operator-level settings, not account-level facts. A reader can rely on them in the sense that if the FAQ lists a method, the cashier should offer it; if the FAQ does not list a method, the reader should not assume it exists.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit methods available | The operator adds or removes payment routes without rewriting the FAQ | The cashier page, which shows only the methods live for the reader's region |
| Withdrawal routes for a deposit method | A route may be deposit-only; the return route can differ by method and region | The withdrawal screen after login, not the FAQ's general list |
| Accepted verification documents | The list is stable, but what passes for a given reader depends on their details | The verification page and any email the operator sends after a rejection |
| Wagering multiple for a promotion | Multiples differ per promotion and can be updated between campaigns | The promotion's own terms page, which the FAQ links to but does not replace |
| Processing time for a withdrawal | Times are ranges that shift with volume, method and verification status | The withdrawal page, which shows the current state of the specific request |
| Bonus eligibility | Eligibility depends on account history, region and deposit method | The promotion terms and the account's bonus panel |
Where the FAQ Stops: Account-Dependent Answers
The clearest boundary in any operator FAQ is the one between what the operator knows in general and what it knows about a specific account. The FAQ is written before the reader logs in. It cannot say why a particular withdrawal is still pending, because that depends on whether the account has passed verification, whether the payment route is available, and whether the amount triggers any review. It cannot say whether a particular document will pass, because that depends on the document itself. It cannot say which bonus a reader is eligible for, because eligibility is computed against the account's history.
When a reader asks the FAQ one of those questions, the honest answer is not on the FAQ page. The FAQ may describe the general reason a withdrawal can be delayed, but the specific reason for this reader's withdrawal lives in the account's transaction history and in any message the operator has sent. The FAQ may list the documents that are accepted, but the specific reason a document was rejected lives in the rejection notice. The FAQ may describe how bonuses are credited, but the specific bonus available to this account lives in the account's bonus panel.
A reader who treats the FAQ as the final answer to an account-specific question will be misled. The FAQ's answer is the general rule. The account's answer is the specific application of that rule, and the two can differ for reasons the FAQ cannot see.
What Changes, and What That Means for a Reader
Operator FAQs go stale in predictable places. Payment methods change as providers are added or removed. Processing times shift with volume and with the operator's own procedures. Promotion terms are rewritten between campaigns, and the wagering multiple on the FAQ may describe a promotion that no longer exists. Verification requirements tighten when regulation changes or when the operator's risk rules change.
The reader's protection against staleness is to check the binding page for the item they care about. The FAQ is a summary; the cashier, the withdrawal screen, the promotion terms and the verification page are the live documents. Where the FAQ and a live page disagree, the live page wins, because the live page is what the operator's system uses.
This is not a defect in the FAQ. It is what an FAQ is for. An FAQ is a directory, not a contract. It tells the reader which page to open and what kind of answer to expect there. The reader who uses it that way gets the benefit of it; the reader who treats it as the contract gets the stale version of a rule that may have changed.
Reading the FAQ Alongside the Binding Documents
The practical method is to read the FAQ and the binding page together, in that order. The FAQ gives the shape of the answer: which documents, which routes, which sequence, which conditions. The binding page gives the current value of each item. A reader checking a withdrawal should read the FAQ's description of the withdrawal sequence, then open the withdrawal screen to see where their own request sits in that sequence. A reader checking a bonus should read the FAQ's description of wagering, then open the promotion terms to see the multiple that applies to the specific offer.
Where the FAQ does not state an item at all, that absence is itself information. If the FAQ does not list a withdrawal route for a deposit method, the reader cannot assume one exists. If the FAQ does not state a processing time, the reader should not invent one. If the FAQ does not name a testing laboratory or a regulator, there is nothing for the reader to verify on that page, and the absence is the answer to that question.
The same discipline applies in the other direction. If the FAQ states a figure, the reader should still confirm it on the binding page before acting on it, because the FAQ may be older than the terms. The FAQ is the starting point, never the endpoint.
FAQ
Can I rely on the Free Games FAQ for withdrawal times?
The FAQ can state the general sequence and the usual range across operators, but the time for a specific withdrawal depends on the account's verification state, the payment route and the operator's current volume. The withdrawal screen after login shows the live state of the request, and that is the binding source for this reader's money.
Does the FAQ tell me which documents will pass verification?
It can list the accepted document types, which is stable. It cannot say whether a specific document will pass, because that depends on the document's clarity, expiry and match to the account details. The rejection notice from the operator states the specific reason a document failed.
If the FAQ lists a deposit method, is it guaranteed to work for me?
The FAQ lists methods the operator supports in general. Whether a method appears for a specific reader depends on region and account settings, and the cashier page shows only the methods live for that reader. A method on the FAQ but absent from the cashier is not available to that account.
Where is the binding answer when the FAQ and a promotion page disagree?
The promotion page wins. The FAQ is a summary that can go stale; the promotion's own terms are what the operator's system applies when a bonus is claimed or wagered. The reader should always confirm the multiple and conditions on the promotion page before depositing.
This page is an independent summary of what an operator FAQ covers and where it stops, it is not published by Free Games, and it states no figure or status for that operator; the operator's own FAQ and the binding pages it links to are the only sources for the reader's specific case.
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.
