The situation an FAQ page is built for
A player lands on an FAQ page because something about their account, their money or a game rule is not behaving the way they expected. The question is usually concrete: why a deposit has not appeared, which document unlocks a withdrawal, whether a bonus can be used on a particular game, or how to close an account. An FAQ is the operator's attempt to answer the most common versions of those questions once, in public, so that the same answer does not have to be written out for every player individually.
The reader's job on this kind of page is not to absorb everything. It is to work out which of their questions the page can answer bindingly, and which ones it cannot answer at all. The distinction is not about how the page is written. It is about what kind of fact the question depends on.
Where an FAQ is binding, and where it is not
A published FAQ is a statement by the operator about its own processes. When it says that withdrawals are processed by a certain route, that a document must be uploaded in a certain format, or that a self-exclusion request has to be made from the logged-in account, that is a commitment the operator has made to every reader. The reader can hold the operator to it. If the page says a withdrawal method is available, and the cashier does not show it, the player has a legitimate complaint.
But an FAQ cannot bind the operator to anything that depends on the individual account. Whether a withdrawal is approved, how long a verification takes for this particular player, whether a bonus is credited to this account, whether a document is acceptable — all of those depend on facts the FAQ writer does not have. The page can state the general rule. It cannot state the outcome for a specific reader. The moment the answer depends on the account, the binding answer moves to the account itself, to the cashier, to the support channel, or to the terms document.
The same applies to anything that depends on current terms. An FAQ may explain how a wagering requirement works in general, but the number that applies to a specific bonus is in the promotion's own terms. An FAQ may explain that withdrawals are processed in order, but the current processing time is a figure that changes and is stated on the withdrawal page or in the cashier. An FAQ is a map of the operator's processes, not a guarantee of any particular figure.
What an FAQ can and cannot settle
| Question type | What the FAQ can do | What the FAQ cannot do | Where the binding answer lives |
|---|---|---|---|
| Deposit routes | List the methods the operator generally accepts | Confirm that a specific method works for this reader's country or bank | The cashier, which filters methods by the logged-in account |
| Withdrawal process | State the steps: request, verification, release | State when this withdrawal will clear | The withdrawal page and the account's transaction history |
| Verification documents | List the document types and formats accepted | Confirm that this reader's document will pass | The verification panel in the account |
| Bonus rules | Explain what a wagering requirement is and how it works | State the multiple that applies to a specific bonus | The promotion's own terms page |
| Game rules | Describe how a game is played | State the house edge or RTP for a specific title | The game's own help or rules screen |
| Account closure | State the route for requesting closure or self-exclusion | Confirm that a request has been received or actioned | The account settings or a confirmation from support |
| Fees and limits | State that fees or limits may apply | State the amount or percentage for this reader | The cashier or the terms document |
The three questions every FAQ reader should ask
Before trusting an FAQ answer, the reader should ask three questions about it. The first is whether the answer is a rule or a figure. A rule is stable: a document must be valid, a withdrawal must go to a method the player has used, a bonus must be wagered before withdrawal. A figure is not stable: processing times, fees, limits, wagering multiples. A rule on an FAQ is more likely to be binding. A figure on an FAQ is more likely to be a snapshot that has since changed.
The second question is whether the answer depends on the account. If it does, the FAQ can only state the general rule, and the reader must check their own account for the specific outcome. The third question is whether the answer conflicts with a more specific document. Terms and conditions override an FAQ. A promotion's own terms override the general bonus FAQ. A game's rules screen overrides a general game FAQ. Where two documents conflict, the more specific one wins, and the FAQ is the least specific document the operator publishes.
What changes on an FAQ, and how often
An FAQ is one of the most frequently edited pages an operator publishes. Every time a payment method is added or removed, every time a verification step changes, every time a fee or limit is adjusted, the FAQ is supposed to be updated. The reader should treat any figure on an FAQ as valid only on the day it was read. A withdrawal time stated as two days may have been accurate when the page was written and inaccurate by the time the reader requests the withdrawal.
Process changes are more durable. The steps for requesting a withdrawal, the requirement to verify identity before a first withdrawal, the route for self-exclusion — these change rarely, and when they do, the change is usually announced. But even a process can change without the FAQ being updated. The reader's own account is always the more current source. If the FAQ says one thing and the cashier shows another, the cashier wins, because the cashier is generated from the reader's actual account state.
Reading X365's FAQ against the terms
X365 publishes its FAQ as a convenience page. The reader should read it as a summary of the operator's processes, not as a contract. The contract is the terms and conditions. Where the FAQ repeats a term, the term is binding because it is in the terms, not because it is in the FAQ. Where the FAQ states something the terms do not, the reader should check whether the terms contradict it. If they do, the terms win. If they are silent, the FAQ is the operator's public statement, and the reader can reasonably rely on it.
This matters most for anything involving money. A reader who follows an FAQ instruction and loses money because the instruction was wrong has a weaker position than a reader who followed the terms. The terms are the document the operator drafted carefully and is held to. The FAQ is the document the operator drafted quickly and edits often. The reader who treats the FAQ as the final word on a withdrawal route or a bonus condition is reading the wrong document.
When the FAQ does not state an item
The absence of an item from an FAQ is itself information. If the FAQ does not state a processing time, that is usually because the time varies too much to publish, or because the operator does not want to be held to a figure. If the FAQ does not list payment methods, the reader must open the cashier to see what is available. If the FAQ does not state a wagering multiple, the multiple is in the promotion's own terms, and the reader must read that document before claiming the bonus.
An FAQ that says nothing about a topic is not evidence that the topic does not exist. It is evidence that the operator has chosen not to answer that question in public. The reader should not conclude that a withdrawal method is unavailable just because the FAQ does not list it. The cashier is the source for availability. The reader should not conclude that a bonus has no wagering requirement just because the FAQ does not mention one. The promotion's terms are the source for that.
FAQ
Does an FAQ answer count as a binding statement from the operator?
For process questions, yes. When X365's FAQ states a route, a step or a document requirement, that is a public commitment. For figures, no. A processing time or fee on an FAQ is a snapshot, and the reader should confirm it in the cashier or the terms before relying on it.
What should I do if the FAQ says one thing and the cashier says another?
Trust the cashier. The cashier is generated from the logged-in account and reflects the methods and limits that apply to that reader. The FAQ is a general statement that may be out of date or may not account for the reader's country, verification status or history.
Can I use the FAQ to argue a withdrawal should be paid?
Only if the FAQ states a process rule and the operator did not follow it. If the FAQ says withdrawals are processed in order of receipt, and the reader can show theirs was skipped, that is a valid complaint. If the FAQ states a time and the time has passed, that is weaker, because times change and the FAQ is not the binding source for them.
Where do I find the wagering requirement for a bonus?
On the promotion's own terms page, not on the general FAQ. The FAQ may explain what a wagering requirement is, but the multiple that applies to a specific bonus is stated only in that bonus's terms. Read those before claiming.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by X365, and it states no figure or status for the operator — the operator's own FAQ and terms 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.
