A player opens an operator's FAQ because one specific thing has gone wrong or is about to: a deposit has not appeared, a withdrawal is stuck, a document was rejected, or a bonus did not credit. The FAQ is the first place that promises an answer without waiting for a support ticket. The useful question is not whether the FAQ is long or short, but which of its answers can be relied on, and which ones are only a summary of something that lives somewhere else.
The split every FAQ is built on
An operator FAQ is not one document. It is a collection of short answers to questions the operator expects to be asked often. Those questions fall into two groups, and the groups behave differently.
The first group covers process: how to open an account, which documents are accepted for verification, how to find a transaction history, what to do when a deposit method is declined, how a self-exclusion request is submitted. These answers describe a route. They say what the reader has to do, in what order, and where in the account interface each step happens. A process answer can be binding because the route does not depend on who the reader is. If the FAQ says a withdrawal request is made from the cashier page, that is true for every account.
The second group covers status and entitlement: how long a withdrawal takes, whether a bonus applies to a particular game, what wagering requirement is attached to a promotion, whether a document has been approved, whether an account is restricted. These answers cannot be binding in an FAQ, because they depend on the reader's own account or on terms that change. An FAQ that says withdrawals take a certain number of days is describing a typical case, not promising that case to any particular reader. The binding answer for a specific withdrawal is the status shown on that withdrawal in the reader's account, plus the withdrawal policy page.
What an FAQ can answer bindingly
Three kinds of answer hold up when read from an FAQ. The first is a route: which menu opens the deposit screen, which button starts a withdrawal, where the verification upload field is. The second is a document list: which identity documents the operator asks for, in which format, with what size limits. The third is a definition: what the operator means by a term it uses on its own pages, such as what counts as a wagering requirement or what a self-exclusion period covers.
These answers stay true because they describe the operator's own interface and its own vocabulary. The interface may change, but at the moment the reader is looking at the FAQ, the route described is either there or it is not. The reader can verify it immediately by following the steps.
A route answer is also the kind most likely to go stale without anyone noticing. An FAQ page is updated less often than the account interface. A menu item may move, a button may be renamed, a document format may change. When a route in the FAQ does not match what the reader sees on screen, the screen is the current truth, and the FAQ is the outdated one.
What an FAQ cannot answer bindingly
Anything that depends on the reader's account state is outside what an FAQ can promise. The most common example is a withdrawal timeline. The FAQ may describe a standard processing window, but the reader's own withdrawal has a status attached to it in the account, and that status is the only answer that applies to that withdrawal. The FAQ answer is background; the account status is the decision.
The same holds for verification. An FAQ can list the documents the operator generally asks for. It cannot say whether the reader's specific document has been accepted, rejected, or is still under review. That answer lives in the verification section of the account, or in a message sent to the reader.
Bonus terms are a third case. An FAQ may explain what a wagering requirement is and how it works in general. It cannot state the multiple attached to a specific promotion, because promotions change and the multiple is set on the promotion's own terms page. A reader who reads a number in an FAQ and treats it as the number for their bonus is reading the wrong page.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Withdrawal processing window | Depends on the reader's account status, the method, and the operator's current queue | Status shown on the withdrawal in the account; withdrawal policy page |
| Accepted verification documents | Document format and size limits are updated as the operator's systems change | Verification section of the account; the upload screen itself |
| Wagering requirement for a bonus | Each promotion sets its own multiple, and promotions are replaced frequently | Terms page of the specific promotion; the bonus's own details in the account |
| Deposit method availability | Methods are added and removed by region and by provider | Cashier page, which shows only the methods currently available to that account |
| Self-exclusion terms | The operator's responsible-gaming policy may be revised | Responsible gaming page; the self-exclusion request form itself |
| Account restriction reasons | Specific to the reader's account and the operator's current risk rules | Message sent to the reader; support channel |
Where the binding answer lives
For every question the FAQ cannot answer bindingly, there is a page or screen that can. The rule is simple: the closer a source is to the reader's own account, the more binding it is. The FAQ is the furthest away. The terms and conditions page is closer, because it is the operator's standing contract. The promotion's own terms page is closer still for anything bonus-related. The account screen is the closest, because it shows the state of the reader's own money, documents, and requests.
This hierarchy matters when the FAQ and another page disagree. If the FAQ describes a withdrawal window and the withdrawal policy page describes a different one, the policy page governs. If the policy page describes a window and the account shows a specific status for the reader's withdrawal, the account status governs. The FAQ is a map, not the territory.
A reader who treats the FAQ as the final word on their own account will make decisions on stale or generic information. A reader who treats it as a pointer to the binding source will go to the right place and read the answer that applies to them.
When the FAQ says nothing at all
An FAQ is selective. The operator chooses which questions to include, and the choice is an editorial decision. The absence of a question from the FAQ is not an answer. It does not mean the operator has no policy on the matter. It means the operator has not chosen to publish a short answer there.
The most important absences are the ones where the reader needs a number: a withdrawal fee, a wagering multiple, a maximum deposit. If the FAQ does not state one of these, the reader cannot infer a number from silence. The number, if it exists, is on the page that governs that item. If that page also does not state it, then there is no published number to rely on, and the reader should treat the item as unstated rather than guessing.
The same applies to status. An FAQ that does not mention self-exclusion does not mean self-exclusion is unavailable. The responsible gaming page is the place to look. An FAQ that does not mention a particular payment method does not mean the method is unsupported. The cashier page shows what is available.
Reading the FAQ as a decision tool
The practical use of an operator FAQ is to answer two questions quickly: what is the route, and where is the binding source. Everything else on the page is context. A reader who opens the FAQ with a specific problem should look for the route answer first, follow it, and then check the binding source for the status or number that applies to them.
If the FAQ gives a route that no longer works, the reader has learned something useful: the FAQ is out of date, and the account interface is the current truth. If the FAQ gives a definition that matches the terms page, the reader can rely on that definition. If the FAQ gives a number that does not appear on the governing page, the reader should treat the governing page as correct and the FAQ as a summary that has drifted.
None of this requires trusting the FAQ. It requires knowing what kind of answer the FAQ is capable of giving, and checking the answer against the source that can bind.
FAQ
Does the Fundedtrading FAQ tell me how long my withdrawal will take?
The FAQ may describe a general processing window, but that window is not a promise for any specific withdrawal. The binding answer is the status shown on the withdrawal in the reader's own account, read together with the withdrawal policy page. If the two disagree, the account status governs.
Can I rely on the document list in the FAQ for verification?
The FAQ can list the kinds of documents the operator generally asks for, but the verification screen in the account shows what is required at the moment of upload. Formats and size limits change, and the upload screen is the current truth. A document rejected by the upload screen is rejected regardless of what the FAQ says.
Does the FAQ state the wagering requirement for my bonus?
It may explain what a wagering requirement is, but the multiple attached to a specific promotion is set on that promotion's own terms page. Promotions are replaced frequently, and an FAQ number can be stale. The reader should read the multiple from the bonus's own terms, not from the FAQ.
What should I do when the FAQ and the account screen disagree?
Follow the account screen. The FAQ is a general summary, and the account screen shows the state of the reader's own money, documents, and requests. When a route in the FAQ no longer matches the interface, the interface is the current truth and the FAQ is outdated.
This page is an independent summary of what an operator FAQ page covers and where its answers stop being binding; it is not published by Fundedtrading, and it states no figure or status for that operator, whose own FAQ and governing pages are the only binding sources.
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.
