A player opens an operator's FAQ because something has already gone wrong, or because they are about to do something that could go wrong. The page they are reading is not a rulebook and not a support ticket. It is a filter: it answers the questions that repeat across thousands of accounts, and it silently passes everything else to another document or another channel. Reading it well means knowing which of those two things is happening with each answer.
What an operator FAQ is built to answer
An FAQ page exists to reduce the number of identical questions reaching a support team. The questions it can answer bindingly are the ones where the answer is the same for every reader and does not change from one day to the next. These are almost always questions about process and routes, not about outcomes.
Typical categories include:
- which documents are accepted for identity verification, and in what format;
- which deposit methods appear in the cashier, and whether a deposit method can also be used for withdrawal;
- what happens when a withdrawal is held, and which department reviews it;
- which games have a return-to-player figure published, and where that figure is displayed;
- how to set a deposit limit, a session reminder, or a self-exclusion.
These answers are about the shape of the system, not about any particular account. The FAQ can state that a passport or a driver's licence is accepted, because that is a standing rule. It cannot state that a specific reader's document will pass, because that decision belongs to a verification team looking at that specific upload.
Where the FAQ stops being binding
The boundary is not between "true" and "false" answers. It is between answers the operator can give once, for everyone, and answers that depend on the reader's own account or on the current version of a changing term.
Anything that depends on the reader's account is outside the FAQ's authority. A question like "why was my withdrawal held?" has no general answer. The FAQ can explain the categories of reason a withdrawal is held, and it can list the documents that typically resolve a hold, but it cannot say which reason applies to a particular reader. That answer lives in the account itself, in a message, a notification, or a support reply.
Anything that depends on current terms is also outside the FAQ's authority, even when the FAQ repeats it. A wagering requirement, a maximum withdrawal amount, a fee, a processing window: these are figures that an operator can change by publishing a new version of its terms or promotions page. If the FAQ states such a figure, the FAQ is a copy, not a source. The source is the terms page, the promotions page, or the cashier screen, and only the version current at the time of the transaction binds.
The practical test is this: if the answer would be the same for a brand-new account and a five-year-old account, and the same this week as last week, the FAQ can answer it. If either of those is false, the FAQ is pointing, not answering.
What changes, and what stays fixed
An FAQ page is not a static document. Operators revise it when a payment method is added or removed, when a verification requirement changes, when a game provider changes, or when a regulator requires a new disclosure. The structure of the page tends to stay stable; the items inside it do not.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Compliance requirements are revised, and the list of acceptable documents can shrink or grow | The verification or KYC section of the FAQ, and the upload screen itself at the moment of submission |
| Deposit methods | Payment providers are added and removed, and availability can differ by country | The cashier or deposit page, which shows only the methods available to the logged-in account |
| Withdrawal methods | A deposit method is not automatically a withdrawal method, and the list changes independently | The withdrawal screen, which shows the routes available for the specific balance and currency |
| Withdrawal processing windows | These are operational figures, not fixed constants, and they are revised without notice | The withdrawal policy or terms page, in the version current at the time of the request |
| Bonus wagering requirements | Each promotion carries its own multiple, and a new promotion can carry a new one | The specific promotion's terms, not the FAQ, because the FAQ cannot list every current offer |
| Game RTP figures | A provider can release a new version of a game, and the published figure follows the version | The game's own information panel or help file, not the FAQ |
| Responsible gambling tools | The tools themselves are stable, but the limits a reader has already set are account-specific | The responsible gambling page for the tool, and the account settings for the reader's own values |
Reading the FAQ against the account
The reader's own account is the only place where a general answer becomes a specific one. A deposit method listed in the FAQ may not appear in a particular reader's cashier, because method availability is filtered by country, currency, and account status. A verification document listed as accepted may still be rejected for a particular upload, because the file is unreadable, expired, or does not match the registered name.
This is not a defect in the FAQ. It is the difference between a general rule and an applied decision. The FAQ tells the reader which documents exist in the system; the upload screen tells them which documents the system will accept from them, today.
When a reader is about to take an action with money attached to it, the FAQ should be read as a checklist of what to confirm elsewhere, not as the confirmation itself. Before a first withdrawal, the reader should confirm on the withdrawal screen which methods are offered for their balance, and should read the withdrawal policy for the processing window and any amount limits. Before accepting a bonus, the reader should read that promotion's own terms for the wagering multiple and the games that count toward it. The FAQ can tell them that such a multiple exists; it cannot safely tell them what the number is.
What it means when the FAQ does not state an item
An FAQ page is a selection, not a complete manual. The absence of an item from the FAQ is not evidence that the item does not exist, and it is not evidence that the item is unimportant. It is evidence that the operator has chosen not to answer that question on that page.
Some absences are routine. An FAQ rarely lists every game's RTP, every promotion's wagering multiple, or every country's available payment methods, because those lists are long and change often. The reader is expected to find them on the game panel, the promotion page, or the cashier.
Other absences matter more. If the FAQ does not state what happens when a withdrawal exceeds a certain amount, the reader cannot assume there is no such threshold. The withdrawal policy or terms page is the place where amount triggers are stated, and if neither page states one, the reader has learned that the operator has not published a threshold, not that no threshold applies.
The same logic applies to verification. If the FAQ does not state which documents are accepted, the reader cannot assume that any document will pass. The upload screen, at the moment of submission, is the authoritative list, and a support reply can confirm it. The FAQ's silence is not permission.
When the FAQ contradicts another page
An operator publishes many documents: terms and conditions, a privacy policy, a withdrawal policy, promotion terms, a responsible gambling page, and an FAQ. These documents are written at different times, by different teams, and they are not always revised together. When two pages state different things, the reader needs a rule for deciding which one governs.
The rule is not "the FAQ is friendlier, so it wins." The rule is that the document closest to the transaction, and most recently dated, is the one that binds. For a bonus, that is the promotion's own terms. For a withdrawal, that is the withdrawal policy or the terms page in force at the time of the request. For a privacy question, that is the privacy policy. The FAQ is a summary layer, and a summary layer loses to the document it summarises whenever they conflict.
If a reader finds a direct contradiction, the correct move is not to choose the more favourable reading. It is to ask support, in writing, which document governs, and to keep the reply. A support reply that names a specific term is a binding statement about that term for that reader, where an FAQ line is not.
What the FAQ cannot do, no matter how complete it is
There is a class of question that no FAQ can answer, because the answer does not exist until the operator looks at the reader's account. These are the questions that begin with "why" and end with a specific event: why a deposit has not appeared, why a withdrawal is held, why a document was rejected, why a bonus was not credited, why an account was restricted.
The FAQ can describe the categories of reason. It can say that a deposit may be delayed by the payment provider, that a withdrawal may be held for verification, that a document may be rejected for a mismatch. What it cannot do is assign a reason to a particular event. That assignment is an account action, and it is communicated through the account's message centre, a notification, or a support reply.
A reader who asks the FAQ "why was my withdrawal held?" and finds only a list of possible reasons has not been given a non-answer. They have been given the correct answer at the FAQ's level of authority. The specific reason is one of the items on that list, and the only place it is named is the account record.
FAQ
Does the Cashyslots FAQ state the current wagering requirement for a bonus?
An FAQ may describe what a wagering requirement is and where it is stated, but the number itself belongs to the specific promotion's terms. Each offer carries its own multiple, and a new offer can carry a new one. The binding figure is on the promotion page, not in the FAQ.
Where does the reader find which withdrawal methods apply to their account?
The withdrawal screen is the authoritative place, because it shows only the methods available for the logged-in account, its currency, and its balance. The FAQ can list methods that exist across the operator, but it cannot filter them for a specific reader.
If the FAQ does not mention a document requirement, does that mean no document is needed?
No. An FAQ is a selection, and its silence is not permission. The upload screen at the moment of submission is the authoritative list of accepted documents for that reader, and a support reply can confirm it in writing.
What should a reader do when the FAQ and the terms page disagree?
The document closest to the transaction governs: promotion terms for a bonus, the withdrawal policy for a withdrawal, the privacy policy for data. If the conflict is material, the reader should ask support in writing which document applies and keep the reply.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Cashyslots, and it states no figure or status for them, so the operator's own FAQ and terms 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.
