The page a player opens when something has already gone wrong
A player does not usually open an operator's FAQ out of curiosity. They open it because a deposit has not appeared, a withdrawal is sitting in a pending state, a document was rejected, or a bonus did not credit the way the promotion page seemed to promise. The FAQ is the first place Cooked directs that player, and it is worth understanding what kind of page it is before trusting it with a decision.
A FAQ is a curated list of questions the operator expects to receive often. It is written to reduce support volume, which means it answers the questions that have one stable answer for most players. That is also its limit. The moment a question depends on the reader's own account, the FAQ stops being able to answer it, because the operator cannot publish one answer that is true for every account.
This matters more than it appears. A player who reads a FAQ answer about withdrawal times and then treats it as a promise about their own withdrawal has misunderstood what the page can do. The FAQ describes the process. The account itself decides the outcome.
What a FAQ can answer bindingly
A well-built FAQ answers questions about process. Process questions have answers that do not change from one account to the next: which menu opens the cashier, which document types the verification team accepts, what the steps are to set a deposit limit, how to find the game rules for a particular title, what happens when a session disconnects mid-round.
These answers are binding in a narrow sense. If Cooked's FAQ states that a passport, driver's licence or national ID card is accepted for verification, then a player who submits one of those has followed the stated process. If the FAQ states that withdrawals are requested from the cashier and not from support, then a player who requests one from support has not followed the stated process. The FAQ is authoritative about the route, not about the destination.
That distinction runs through every section of a typical operator FAQ. The deposit section says which methods the cashier can show. The withdrawal section says which steps a request must pass through. The verification section says which documents are in the accepted set. The responsible-gaming section says which tools exist and where they are switched on. None of those answers promise an outcome for a specific account; all of them tell the reader which button to press and which document to upload.
What a FAQ cannot answer, and where the answer lives instead
Three kinds of question fall outside what any operator FAQ can settle. The first is anything account-specific: why a particular withdrawal is still pending, whether a particular document was accepted, whether a particular bonus was credited. The FAQ cannot know the answer, because the answer lives in the account record, not in a published page. The binding source is the account itself, as shown in the cashier, the verification centre, or the message thread with support.
The second is anything that depends on current terms. Bonus percentages, wagering multiples, minimum deposits, maximum withdrawal amounts, and fee schedules all change. A FAQ page is usually updated less often than the terms page or the promotion page, and a figure read in a FAQ may be older than the figure on the page that governs the transaction. Where a FAQ repeats a figure, the reader should confirm it against the terms page or the promotion page before acting on it.
The third is anything that depends on the reader's jurisdiction or payment method. A FAQ can say that withdrawals are processed in a certain order, but it cannot say which methods are available to a particular player, because method availability is shown in the cashier after login and can differ by country, currency, and account status. The FAQ describes the general shape; the cashier shows the reader's actual options.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Document lists are revised as compliance requirements change | Verification centre after login, or the FAQ's verification section |
| Deposit methods available to the reader | Method availability depends on country, currency and account status | Cashier after login, not the FAQ |
| Bonus percentage and wagering multiple | Promotions are updated independently of the FAQ | The promotion's own terms page |
| Withdrawal processing order and steps | The process is stable, but a specific request's status is not | FAQ for the process; cashier or support for the status |
| Responsible-gaming tools and where to set them | Tool names and locations are stable, but limits are account-specific | FAQ for the route; account settings for the value |
| Game rules for a particular title | Rules are fixed per title but vary between titles | The game's own rules screen, opened from the lobby |
The FAQ is a map, not the territory
Treat Cooked's FAQ as a map of the operator's processes. A map tells you which roads exist and which direction they run. It does not tell you whether your car will start, whether the road is closed today, or whether you have enough fuel. The FAQ tells the reader which steps exist and in what order they run. It does not tell the reader whether their own request will clear, whether their document will pass, or whether their bonus will credit.
That is not a defect in the FAQ. It is the nature of the page. A FAQ that tried to answer account-specific questions would be wrong for most of its readers most of the time. The operator therefore writes it at the level of the process, and the reader who understands that reads it more accurately than the reader who expects it to be a personal answer.
When a FAQ answer and the reader's account disagree, the account wins. If the FAQ says a withdrawal is processed within a certain window and the reader's withdrawal has been pending longer, the FAQ has not been broken; it has simply reached the edge of what it can say. The next step is not to re-read the FAQ but to open the cashier or contact support, because the answer now lives in the account record.
Which sections of a FAQ deserve the closest reading
Three sections repay careful reading more than the rest. The verification section matters because a rejected document delays every withdrawal and deposit method that depends on a verified account. The reader should note exactly which document types are listed, whether a document must be current or merely valid, and whether a utility bill or bank statement is accepted for address proof. A mismatch between what the reader uploads and what the section lists is the most common cause of a stalled verification.
The withdrawal section matters because it states the order of operations: whether a withdrawal must be requested from the cashier, whether a bonus must be completed or forfeited first, and whether the method used for deposit must be used for withdrawal. These are process constraints, not promises, and they are binding in the sense that a request which violates them will not proceed.
The responsible-gaming section matters because it is the one place where the reader can set limits that the operator must honour. Deposit limits, loss limits, session limits, cool-off periods and self-exclusion are all tools that change what the account can do. The FAQ states where each tool is found and how it is activated. The actual limit values are set by the reader, not by the FAQ.
What the FAQ cannot tell you about money
No FAQ can tell a player how much money they will win or lose. It can state the process for withdrawing, but not the amount that will arrive, because the amount depends on the account balance, any pending bonus conditions, and any fees applied by the payment method. It can state the process for depositing, but not the amount that will be credited, because the credit depends on the payment provider and the operator's cashier.
The same applies to time. A FAQ may describe the order in which withdrawals are processed, but it cannot promise a clearing time for a specific request, because clearing time depends on the payment method, the verification status of the account, and the operator's processing queue. A reader who needs a date should read the cashier's status field, not the FAQ.
Where the FAQ does state a figure, read it as a snapshot. Bonus percentages, wagering multiples, minimum and maximum amounts, and fee schedules are all set on other pages, and those pages are the binding source. If the FAQ and the terms page disagree, the terms page governs, because it is the document the operator updates when a promotion changes.
When the FAQ is silent
Silence in a FAQ is itself information. If the FAQ does not state which documents are accepted for verification, the reader cannot assume that any particular document will pass. If the FAQ does not state whether a deposit method can be used for withdrawal, the reader cannot assume that it can. If the FAQ does not state a processing time, the reader cannot assume one exists.
In each of those cases, the absence is the answer to the question as asked. The reader who asks "which documents are accepted" and finds no list has learned that the list is not published on that page, and must be found in the verification centre or by asking support. The reader who asks "how long will my withdrawal take" and finds no window has learned that no window is published, and must read the status of their own request instead.
This is why a FAQ is best read as a set of routes, not as a set of guarantees. Each answer tells the reader which page to open, which button to press, or which document to prepare. The outcome is decided elsewhere, by the account, the terms, and the payment provider.
FAQ
Does the Cooked FAQ tell me why my withdrawal is still pending?
No. A FAQ describes the withdrawal process in general, but the status of a specific withdrawal lives in the account record. Open the cashier to see the current status of your request, and contact support if the status does not explain the delay.
Can I rely on the bonus figures in the FAQ?
Only as a starting point. Bonus percentages and wagering multiples are set on the promotion's own terms page, which is updated more often than the FAQ. Before claiming a bonus, read the terms page and treat it as the binding source.
Where do I find which documents Cooked accepts for verification?
The FAQ's verification section, if it lists them, states the accepted document types. The authoritative list is the one shown in the verification centre after login, because it reflects the current requirements for your account.
What should I do when the FAQ and my account disagree?
Trust the account. The FAQ describes the general process; the account shows your actual balance, status, and options. If they disagree, the account is the more current and more specific source, and support can explain the difference.
This page is an independent summary of what an operator FAQ covers and where its answers stop; it is not published by Cooked, and it states no figure or status for that operator, whose 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.
