The page that answers what the cashier cannot
A player sits in front of a deposit screen that refuses a card, or a withdrawal button that stays grey, and the first place they are told to look is the FAQ. That is the moment the page is being used: not as a manual to read cover to cover, but as a triage desk for a blocked action. The Cagliari FAQ exists to answer the questions that repeat across thousands of accounts, and to send the reader somewhere else when the answer depends on their own account. Understanding that split is the whole skill of using it.
An operator FAQ is not a contract and it is not a support ticket. It is a published summary of the operator's most stable processes. When it says which documents open a withdrawal, that is process. When it says how long a withdrawal takes, that is usually a range that the operator's own terms page can override for a given method or amount. And when it says whether a specific reader's deposit failed, it is guessing, because no static page can see a live account. The reader who treats the FAQ as a map of where answers live, rather than as the answers themselves, gets further with less frustration.
What an FAQ can answer bindingly
There is a class of question where the FAQ is genuinely the final word, because the answer is the same for every account and changes only when the operator publishes a new version of the page. These are the structural questions: which payment routes exist, which documents the operator asks for before a first withdrawal, which currencies the cashier will display, which self-service tools are available in the account menu. If Cagliari's FAQ states that a given document type is accepted, that statement is binding in the sense that the operator has published it as its own current process. The reader can rely on it until the page itself changes.
The table below separates the questions an FAQ can settle from those it cannot, and shows where the binding answer lives for each.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted document types for verification | Operators revise document lists as regulation or risk policy changes | The FAQ's verification section, and the upload screen itself |
| Available deposit routes | Payment providers enter and leave markets; a method listed today may be withdrawn tomorrow | The cashier's deposit tab, which reflects live availability |
| Withdrawal minimum and maximum | Figures are method-specific and change with operator policy | The withdrawal screen and the terms page, not the FAQ |
| Processing time for a withdrawal | Depends on method, verification status, and the operator's queue | The withdrawal confirmation screen and the terms page |
| Bonus wagering multiple | Each promotion carries its own multiple and expiry | The specific promotion's terms, never the FAQ |
| Whether a specific deposit failed | Account-specific, tied to the reader's bank, card issuer, or account state | Live support or the transaction history, not the FAQ |
The FAQ stops where the account begins
Every answer that depends on the reader's own balance, history, verification state, or jurisdiction is outside what a static FAQ can decide. The page may describe the general rule: that a first withdrawal requires verification, that a deposit can be held while its source is checked, that a bonus is forfeited if wagering is not met. But it cannot say whether this reader's verification has passed, whether this deposit is the one being held, or whether this bonus has met its multiple. For those, the account itself is the only source, and the FAQ's job is to point there.
This is not a defect of the page. It is the correct division of labour. A page that tried to answer account-specific questions would have to be generated per reader, and would still be wrong the moment the account changed. The reader who asks the FAQ a personal question and gets a general answer has not been failed; they have been told, correctly, that the answer lives one click further in, on the transaction history, the verification screen, or a live support conversation.
Which items on the FAQ commonly change
An FAQ is a snapshot of the operator's current processes, and some parts of the snapshot go stale faster than others. Payment routes are the most volatile, because a card scheme or e-wallet can stop serving a market with little notice, and the FAQ may lag the cashier by days. Document lists change less often but do change, usually when a regulator or a banking partner tightens a requirement. Withdrawal timeframes are published as ranges precisely because they are targets, not promises; a reader who reads a range as a guarantee has misread the page.
The reader's defence against staleness is to treat the FAQ as a starting point and the live screen as the authority. If the FAQ lists a deposit method and the cashier does not show it, the cashier wins. If the FAQ says a document is accepted and the upload screen rejects the file type, the upload screen wins. The FAQ is the operator's general statement; the live screen is the operator's current behaviour. Where the two conflict, the reader should resolve the conflict in favour of the screen and, if the difference matters, ask live support to reconcile them.
Where the binding answer lives instead
For anything the FAQ cannot decide, the operator publishes the binding answer in a specific place, and the reader who knows which place is which saves themselves a support ticket. The terms and conditions page is the binding source for anything contractual: wagering multiples, bonus expiry, withdrawal limits, account closure rules. The privacy policy is the binding source for what the operator does with the reader's data. The AML policy is the binding source for what triggers a source-of-funds check. The cashier and the account screens are the binding source for what is available to this reader right now.
A reader who wants to know whether a particular withdrawal route exists should not ask the FAQ; they should open the withdrawal screen and look. A reader who wants to know whether a bonus can be withdrawn should not ask the FAQ; they should open the promotion's own terms. The FAQ's value is that it tells the reader which of those places to open, and what to look for when they get there. It is an index, not an encyclopaedia.
Reading the FAQ as a checklist, not a story
The practical way to use the Cagliari FAQ is to turn it into a checklist for the action the reader is trying to complete. Before a first withdrawal, the checklist is: which documents does the FAQ say to prepare, which of those does the upload screen accept, and which withdrawal route does the cashier show for the deposit method used. Before a deposit, the checklist is: which routes does the FAQ list, which does the cashier show, and what does the deposit screen say about minimums and fees. The FAQ supplies the shape of the checklist; the live screens fill in the values.
This checklist reading has one more advantage: it makes the reader notice when the FAQ is silent. If the FAQ does not state a withdrawal minimum, the reader should not assume there is none; they should look for the figure on the withdrawal screen or in the terms. If the FAQ does not name a payment provider, the reader should not assume it is accepted; they should open the cashier. An absence on the FAQ is not an answer. It is a sign that the answer lives somewhere else, and the reader who follows the sign is the one who gets the question resolved.
What the FAQ cannot protect the reader from
There are some harms an FAQ cannot prevent, and it is worth stating them plainly. A wagering requirement is a condition on withdrawing bonus winnings, not a gift; the FAQ may explain the concept, but only the promotion's own terms state the multiple that applies. A self-exclusion tool is the one control that cannot be undone on request; the FAQ may describe where the tool is, but the reader should understand that activating it is a serious step with a cooling-off period that the operator will not waive on a support ticket. KYC exists partly to stop the reader themselves from being used as a money mule; the FAQ may list the documents, but the reason behind the list is not convenience.
None of this is a reason to avoid the FAQ. It is a reason to read it with the right expectations. The page is the operator's own summary of its processes, published so that the same question does not have to be answered a thousand times in support chat. It is useful exactly to the extent that the reader treats it as a map of where the binding answers live, and not as the answers themselves.
FAQ
Can the Cagliari FAQ tell me why my withdrawal is pending?
No. The FAQ can explain the general reasons a withdrawal might be pending, such as verification not being complete or the amount exceeding a threshold. But the specific reason for your withdrawal is visible only in your account's transaction history or from live support. The FAQ is a general explanation, not a status check.
If the FAQ lists a deposit method, does that mean it works for me?
Not necessarily. The FAQ lists methods the operator generally supports, but availability depends on your country, your account state, and the payment provider's current service. The cashier's deposit tab is the only place that shows what is available to you right now. If a method appears in the FAQ but not in the cashier, the cashier is the authority.
Where do I find the wagering requirement for a bonus?
Not in the FAQ. The FAQ may explain what a wagering requirement is, but the specific multiple, the games that count toward it, and the expiry are stated only in the terms of the specific promotion you claimed. Open that promotion's terms page and read the wagering section. The FAQ cannot state a figure that differs from one bonus to the next.
What should I do if the FAQ contradicts what I see on the screen?
Follow the screen. The FAQ is a published summary that can lag behind live changes, while the screen reflects the operator's current behaviour for your account. If the difference matters, note both versions and ask live support to reconcile them. The screen is the operator acting; the FAQ is the operator describing.
This page is an independent summary of what an operator FAQ covers and where it stops, it is not published by Cagliari, and it states no figure or status for them; the operator's own FAQ and account screens 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.
