The situation an FAQ is built for
A player who opens an operator's FAQ usually has a transaction or an account action in progress. A deposit has not appeared, a withdrawal is pending, a document was rejected, a bonus was not credited, or a game rule is unclear. The FAQ exists to answer the questions that recur across thousands of accounts, so the player does not have to open a support ticket for every routine step. That is its strength and its limit: it answers what is the same for everyone, and it stops exactly where one player's account differs from another's.
Reading an FAQ well means knowing which of your questions it can settle and which it cannot. A question about the steps of a withdrawal is answerable in an FAQ. A question about why your withdrawal is still pending is not, because the answer depends on your verification state, your payment method, your amount, and the operator's current review queue. The FAQ can tell you where to look and what normally happens; it cannot tell you what is true of your account right now.
What an FAQ can answer bindingly
An operator FAQ is a binding source for questions whose answer is a fixed process or a fixed route, not a variable outcome. These are the categories where the FAQ is the right document to read:
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Which documents are accepted for identity verification | Accepted document lists are usually stable, but the operator can add or remove a document type at any time | The verification or KYC section of the FAQ, and the upload screen in the player's account |
| The order of steps in a withdrawal | The sequence is fixed by the operator's process, but the time each step takes varies by method and account state | The withdrawal section of the FAQ, and the cashier's withdrawal screen |
| Which deposit routes are offered | Payment methods are added and removed by region and by provider availability | The deposit or payments section of the FAQ, and the cashier's deposit screen |
| What a wagering requirement means | The definition is fixed, but the multiple attached to any specific bonus is not | The bonus section of the FAQ, and the promotions terms page |
| How self-exclusion is requested | The request route is fixed, but the operator may change the form or the channel | The responsible gaming section of the FAQ, and the account settings page |
| What happens when a document is rejected | The rejection reasons are standard, but the specific reason for any one rejection is account-specific | The verification section of the FAQ, and the email or notification the player received |
In each of these rows, the FAQ can state the mechanism: what the player does, what the operator does next, and where the player sees the result. The FAQ cannot state the result itself for any individual player, because the result is produced by the player's own inputs.
Where the FAQ stops
The boundary of an FAQ is the boundary of the general. Any question whose answer depends on a number, a status, or a current term is outside what an FAQ can settle. These are the questions a reader should not expect the FAQ to answer, and should instead take to the document or channel that owns them:
- Why is my withdrawal still pending? The FAQ can describe the review steps and the typical order of operations, but the reason any one withdrawal is held is in the player's account history, the verification status shown there, and any message the operator has sent. The binding answer is in the account, not in the FAQ.
- How much can I withdraw at once? Any limit is a number, and numbers live in the withdrawal policy or the cashier screen, not in the FAQ. If the FAQ mentions a limit, it is a summary of the policy at the time of writing, and the policy is the binding source.
- Is my bonus active? Bonus state is account-specific and changes with every wager, deposit, and expiry. The FAQ can explain what active, locked, and expired mean, but it cannot say which state any one bonus is in.
- What is the current wagering multiple? The multiple is a term, and terms change. The promotions page is the binding source; the FAQ may describe what a multiple is, but any figure it carries is a copy, not the original.
- Which payment method is fastest for me? Speed depends on the method, the region, the verification state, and the operator's processing queue. The FAQ can list the methods and the steps, but it cannot rank them for any one player.
The test is simple: if the answer would be the same for every player who reads it, the FAQ can answer it. If the answer would differ by account, by amount, by method, or by date, the FAQ can only point to the place where the specific answer is generated.
What changes, and why the FAQ is not the source of record
An FAQ is a summary document. It is written to be read quickly, and that means it compresses. The operator's terms, policies, and cashier screens are the source of record; the FAQ is a paraphrase. When the source changes, the FAQ may lag behind it. A player who reads a figure in an FAQ and acts on it without checking the source is acting on a copy.
The items that change most often across operators are the ones a player is most likely to search for in an FAQ: payment methods, withdrawal limits, verification document lists, and bonus terms. Payment methods are added and removed by region and by provider agreement. Withdrawal limits are adjusted by the operator's risk policy. Verification document lists change as regulations and fraud patterns change. Bonus terms change with every promotion cycle. In each case, the FAQ may be updated, but the update is not guaranteed to be simultaneous with the change.
This is why the FAQ is best used as a map, not as a contract. It tells the player which page owns which item, and what the item means in plain language. The player then reads the owning page for the current value. A reader who treats the FAQ as the final word on a limit or a multiple is reading the wrong document.
Reading the FAQ alongside the account
The most useful reading of an operator FAQ is a side-by-side reading with the player's own account. The FAQ supplies the general mechanism; the account supplies the specific state. For a withdrawal, the FAQ explains the steps and the typical order; the account's withdrawal screen shows the current status, the method, the amount, and any hold. For verification, the FAQ lists the accepted documents and the rejection reasons; the account's verification screen shows which documents have been uploaded, which were accepted, and which were rejected, with the reason for each rejection.
When the two conflict, the account wins. The account screen is generated from the operator's live data for that player; the FAQ is a static summary. If the FAQ says a document is accepted and the account screen does not offer it as an upload option, the account screen is the current truth. If the FAQ describes a withdrawal step that the account screen does not show, the account screen reflects the player's actual state, and the FAQ is describing a state the player has not reached or a step that does not apply to their method.
This is not a defect in the FAQ. It is the difference between a general description and a specific record. The FAQ is the general description; the account is the specific record. A player who needs the specific record should read the account, not the FAQ.
What the FAQ cannot do
There are three things an operator FAQ cannot do, and a reader who expects any of them will be misled. First, it cannot make a promise about an outcome. It can describe the process that produces an outcome, but it cannot guarantee that any one withdrawal will clear, any one document will be accepted, or any one bonus will be credited. The outcome is produced by the player's inputs and the operator's current rules, not by the FAQ's description.
Second, it cannot override the terms. If the FAQ says one thing and the terms say another, the terms govern. The FAQ is a summary; the terms are the contract. A player who relies on an FAQ statement that contradicts the terms has no claim based on the FAQ.
Third, it cannot answer a question the operator has not chosen to publish an answer to. If the FAQ does not state a withdrawal limit, the limit is not in the FAQ, and the player must find it in the withdrawal policy or the cashier screen. The absence of an item from the FAQ is not evidence that the item does not exist; it is evidence that the FAQ is not the place the operator has chosen to state it. The player should read the absence as a pointer: the answer lives somewhere else.
Where the binding answer lives
For each category of question, the binding answer lives in a specific place, and the FAQ's job is to route the reader there. The table below maps the question categories to their owning documents:
| Question category | Binding source | What the FAQ contributes |
|---|---|---|
| Deposit methods and minimums | The cashier's deposit screen | Lists the methods and explains the steps |
| Withdrawal methods, limits, and timeframes | The withdrawal policy and the cashier's withdrawal screen | Describes the process and the typical order of steps |
| Verification documents and rejection reasons | The verification screen in the account and the KYC policy | Lists the accepted documents and the standard rejection reasons |
| Bonus terms and wagering multiples | The promotions terms page for each specific bonus | Explains what a wagering multiple is and how it applies |
| Account closure and self-exclusion | The responsible gaming policy and the account settings page | Describes the request route and the consequences |
| Game rules and payout structures | The game's own rules screen and the operator's game rules page | Summarizes the objective and the main rule variants |
A reader who uses the FAQ as a routing table, and then reads the owning document for the current value, is using the FAQ exactly as it is designed to be used. A reader who stops at the FAQ and treats its summary as the final word is reading a copy instead of the original.
FAQ
Can the Srtpgs FAQ tell me why my withdrawal is pending?
No. The FAQ can describe the withdrawal process and the typical order of steps, but the reason any one withdrawal is pending depends on the player's verification state, payment method, amount, and the operator's current review queue. The binding answer is in the player's account history and any message the operator has sent.
If the FAQ does not state a withdrawal limit, does that mean there is no limit?
No. The absence of a limit from the FAQ means only that the FAQ is not the place the operator has chosen to state it. The limit, if any, is in the withdrawal policy or the cashier screen, and those are the binding sources.
Can I rely on a figure I read in the FAQ?
Only as a summary. Any figure in an FAQ is a copy of a term that lives in the promotions terms, the withdrawal policy, or the cashier screen. If the FAQ figure and the source figure differ, the source governs. Always read the owning document for the current value.
What should I do when the FAQ and my account screen disagree?
Trust the account screen. The account screen is generated from the operator's live data for your account; the FAQ is a static summary. If the account screen shows a different method, status, or option than the FAQ describes, the account screen reflects your actual state.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by the operator, and it states no figure or status for them, so the operator's own FAQ and the documents it points to 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.
