A player who opens an operator's FAQ usually arrives with one of two problems: a process has stopped, or a number looks different from what they expected. The FAQ is the page built for exactly that moment, and the first thing to understand about it is that it is not one document. It is a collection of short answers that point to other documents, and the pointing is what makes it useful or useless. On Cozino's FAQ, the reader is not reading the terms; they are reading a map of the terms.
The split between what an FAQ settles and what it only points to
Every operator FAQ, Cozino's included, is written for the player who is already inside the site and already has an account. That changes what the page can say. A question like "how do I withdraw" gets a process answer: open the cashier, choose a method, enter an amount, confirm. A question like "why is my withdrawal pending" cannot get a binding answer from any FAQ, because the reason lives in the reader's own account, in the verification state of their documents, and in the terms that applied on the day they accepted a bonus. The FAQ can list the common reasons; it cannot know which one applies to this reader.
That split runs through every section of the page. Questions about routes and document lists are stable enough to answer on a static page. Questions about amounts, timeframes and eligibility are not, because those are set by the reader's account state and by the current version of the promotions terms, the withdrawal policy and the AML policy. The FAQ is the index; the binding answer is always one click further in.
What an FAQ answers bindingly: process, routes, document lists
There is a class of question where the FAQ is itself the source a reader can rely on, and it is worth knowing which class that is. These are questions whose answer does not change from one account to another and does not change from one week to the next:
- Which steps a deposit or withdrawal follows, in what order;
- Which document types are accepted for identity, address and payment verification;
- Which payment routes exist at all, as categories rather than as promises about a specific account;
- How to reach a support channel, and what that channel can and cannot do;
- Which account tools exist, such as limits, self-exclusion and session reminders, and how to reach them.
For these, the FAQ answer is normally safe to act on, because the operator has no reason to vary it by account and every reason to keep it accurate. The reader should still confirm the route exists in their own cashier, because an FAQ can list a method that is not offered in the reader's region or to the reader's account class. The list is the general rule; the cashier is the specific one.
What an FAQ cannot answer bindingly, and where the binding answer lives
The second class is larger, and the reader who treats an FAQ answer in this class as final is the reader who later finds a withdrawal held or a bonus forfeited. These are questions whose answer depends on the reader's own account, on a current term, or on a figure that changes:
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Wagering multiple on a bonus | Promotions terms are revised between campaigns; the multiple on today's offer is not the one on last month's | The promotions terms page, under the specific offer the reader accepted |
| Withdrawal processing window | Depends on method, verification state, and the queue at the time of the request | The withdrawal policy page, and the status shown on the reader's own withdrawal in the cashier |
| Minimum deposit or withdrawal amount | Set per method and sometimes per account class or region | The cashier, which shows the limits for the method selected |
| Which documents are required for verification | Depends on deposit method, withdrawal amount, and the risk rules in force | The verification request itself, which lists the documents the operator wants from this reader at this time |
| Whether a bonus is still active | Expiry dates and forfeiture conditions are per bonus, not per FAQ | The reader's own bonus balance and the terms attached to that specific bonus |
| Which payment methods are available to this reader | Availability varies by country, currency and account status | The deposit and withdrawal screens in the reader's own cashier |
| Self-exclusion duration and reversibility | Set at the moment the reader activates the tool, and the rules on reversing it are in the responsible gaming policy | The responsible gaming page and the confirmation shown when the tool is activated |
The pattern is consistent: the FAQ tells the reader that a rule exists and roughly where it lives; the rule itself, with the figure or the deadline or the condition, is on the page the FAQ points to. A reader who wants the number must go to the page that owns the number.
Why an FAQ answer can be stale even when it is well written
An FAQ is a maintenance burden, and every operator page of this kind ages in the same predictable places. The paragraphs about how to open an account or how to contact support stay accurate for years. The paragraphs that mention a percentage, a timeframe, a fee or a named payment brand go stale the moment the operator changes the underlying term, and the FAQ is often the last page to be updated when that happens. The reader should treat any figure read on an FAQ as a pointer to the page that owns the figure, not as the figure itself.
This is not a defect of Cozino's FAQ specifically; it is the nature of the page type. An FAQ is a summary layer, and a summary layer is only as current as the last edit. The terms page, the withdrawal policy and the promotions page are the documents the operator updates first, because those are the documents a dispute will be judged against. The FAQ is updated second, if at all. A reader who needs certainty reads the document the FAQ points to, not the FAQ's paraphrase of it.
The account-state problem: why the FAQ cannot see the reader
There is a deeper reason an FAQ cannot answer many of the questions a player types into it. The page is static. It does not know who is reading it, what currency they use, what country they are in, what their verification status is, or which bonus they accepted. Every answer that would require that knowledge is, by construction, a generalisation. The reader's real question is usually "what is true for me right now", and the only pages that can answer that are the ones that read the account: the cashier, the bonus balance, the verification centre, the withdrawal status screen.
This is why the most useful sentence on any FAQ is often the one that says where the account-specific answer is, not the one that tries to give the answer. A reader who learns to read the FAQ as a directory of binding pages gets more from it than a reader who expects the FAQ itself to be binding.
Where the FAQ stops and the binding documents begin
Every operator publishes a small set of documents that are binding in a dispute, and the FAQ is not among them. The binding set is the terms and conditions, the privacy policy, the withdrawal or payments policy, the promotions terms, the AML policy and the responsible gaming policy. The FAQ may summarise any of these, but a summary is not the document. When a reader finds a conflict between an FAQ answer and a term on one of those pages, the term on the binding page is the one that will be applied. The FAQ is an aid to navigation, not a source of rights.
For Cozino, the reader should expect the same structure: an FAQ that answers process questions directly and points to the binding pages for everything that carries a figure, a deadline, a condition or a status. The reader's job is to notice which kind of question they are asking and to follow the pointer when the answer matters.
Reading an FAQ before a first deposit
A reader who has not yet deposited is in the best position to use an FAQ well, because nothing is urgent yet. The questions worth asking before any money moves are the ones whose answers are stable and binding: what document types will be needed for verification, which payment routes exist at all, what the responsible gaming tools are and where they sit, and how a withdrawal is requested. The questions not worth asking yet are the ones whose answer will be set by the deposit itself: the wagering multiple on a bonus, the processing window on a withdrawal, the minimum amount for a specific method. Those are answered after the deposit, by the pages that know about the deposit.
The pre-deposit reader should also note what the FAQ does not say. If a question that matters to them is absent, that absence is information. It means the operator has not committed to a public answer, and the reader should ask support before acting, not after. An FAQ that is silent on a point is not an FAQ that has answered the point in the negative; it is an FAQ that has not answered it at all.
What changes on an FAQ, and what stays fixed
The fixed parts of any operator FAQ are the mechanics: how to open the cashier, how to upload a document, how to set a limit, how to contact support. These change only when the operator rebuilds the site. The moving parts are everything else: payment method lists, verification document lists, any mention of a timeframe or a limit, any mention of a bonus structure, any mention of a fee. A reader returning to an FAQ after months away should assume the moving parts have moved and re-read them as if for the first time.
The practical rule is simple. If an FAQ sentence contains a number, a brand name, a deadline or a condition, that sentence is only as good as the page it summarises. If it contains only a sequence of steps, it is probably current. The reader who applies that rule will rarely be surprised by an FAQ.
FAQ
Does the Cozino FAQ tell me my withdrawal will be processed in a specific time?
No FAQ can answer that for a specific reader, because the processing window depends on the method, the verification state of the account and the queue at the time of the request. The FAQ may describe the general process and may point to the withdrawal policy, but the binding status is the one shown on the reader's own withdrawal in the cashier.
Can I rely on the FAQ's list of payment methods?
Only as a general indication of what the operator supports somewhere. The methods available to a specific reader depend on country, currency and account status, and the only reliable list is the one shown in the reader's own deposit and withdrawal screens. A method listed on the FAQ but absent from the cashier is simply not available to that reader.
Where do I find the wagering requirement for a bonus I accepted?
Not on the FAQ. The wagering multiple is set by the specific promotion the reader accepted, and it is stated on the promotions terms page under that offer. The FAQ may explain what wagering means in general, but the figure that applies to a given bonus is on the bonus's own terms, and that is the figure a dispute would be judged against.
What should I do if the FAQ says one thing and the terms page says another?
Follow the terms page. The FAQ is a summary layer, and the binding documents are the terms and conditions, the withdrawal policy, the promotions terms and the other policy pages. Where a summary conflicts with the document it summarises, the document governs. If the conflict matters, ask support to confirm in writing before acting.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Cozino, and it states no figure or status for that operator, whose own FAQ and binding policy pages are the only source for those.
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.
