Why an FAQ page is a map, not a contract
A player who opens Hh98's FAQ page is usually trying to solve one of a small set of problems: a deposit that has not appeared, a withdrawal that is not moving, a bonus that will not activate, or a document the account page keeps asking for. The FAQ page is built for exactly those moments. It collects the questions the operator expects to be asked most often and answers them in a form that is shorter and easier to scan than a full terms document. What it is not is a contract. The answers on an FAQ page explain how a process is supposed to work in general, but the figure that decides what happens to a particular player's money — the amount, the deadline, the document list, the wagering multiple — is almost always written somewhere else, and that other place is the one that binds.
The useful way to read an FAQ page is therefore as a map of where each answer lives. The FAQ may say that withdrawals are processed after verification. The verification policy page says which documents are accepted and what makes one fail. The FAQ may say that a bonus has wagering requirements. The promotions terms page states the multiple and the games that count toward it. The FAQ is the signpost; the other page is the rule. A reader who treats the FAQ as the final word on a money question has read the wrong document.
What an FAQ can answer bindingly
An FAQ page is at its most reliable when it describes a sequence of steps that does not change from one account to another. How to open the cashier, where the deposit button is, what the verification upload screen looks like, which menu contains the transaction history — these are interface facts. They are true for every player who sees the same version of the site, and the FAQ can state them without needing to know anything about the reader's account. The same applies to the order of operations: that a withdrawal request is reviewed before it is released, that a bonus is credited only after the qualifying deposit settles, that a self-exclusion request takes effect only after it is confirmed. The FAQ can describe that order because the order is a property of the system, not of the player.
An FAQ can also answer questions about what a player must do, as opposed to what the operator will do. The list of documents accepted for identity verification, the file formats the upload screen takes, the minimum age a player must confirm — these are obligations placed on the player, and the FAQ can state them plainly because they do not depend on the reader's balance or history. When the FAQ says "you must submit a government-issued document", that is an instruction the reader can follow. When it says "withdrawals take two days", that is a prediction the reader cannot rely on, because the actual time depends on the payment route, the verification state of the account, and the operator's current processing load. The first kind of answer is binding; the second is a summary of a policy that lives elsewhere.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Document lists are updated as regulation and fraud patterns change | Verification or KYC policy page |
| Minimum and maximum deposit | Limits vary by payment method and player status | Cashier or payments page, per method |
| Wagering multiple for a bonus | Each promotion carries its own multiple and game weighting | Promotions terms page for that specific offer |
| Withdrawal processing time | Depends on method, verification state and queue length | Withdrawal policy page, per method |
| Self-exclusion duration options | Options may be revised; the chosen period is fixed at request time | Responsible gaming page or account settings |
| Which games count toward wagering | Weighting tables differ across game categories and promotions | Promotions terms page, game weighting table |
What an FAQ cannot answer, and why
Every question that depends on the reader's own account is outside what an FAQ page can settle. The FAQ cannot say whether a specific withdrawal has been approved, because that depends on the documents the reader has uploaded, the payment method chosen, and the operator's review queue at the moment the request was made. The FAQ cannot say why a specific deposit has not appeared, because that depends on the reader's bank, the payment provider's processing window, and whether the deposit was made from a method the account is allowed to use. The FAQ cannot say whether a bonus is available to a specific player, because bonus eligibility is usually tied to deposit history, geographic location, and whether the player has already claimed the same offer. An FAQ page that tried to answer these questions for every reader would have to be rewritten every time any account changed state, which is why it does not attempt it. The answer to an account-specific question is always in the account itself: the transaction history, the verification status panel, the bonus section, or the support channel that can see the reader's file.
The same limit applies to anything that is a current term rather than a fixed process. A wagering multiple is a current term: the operator can change it for a new promotion without changing the FAQ page. A withdrawal fee is a current term: it can differ by method and by region. A list of accepted payment brands is a current term: methods are added and removed as providers change their terms. An FAQ page may summarize these things, but the summary is a snapshot. The binding version is the page that is updated when the term changes — the promotions terms page, the withdrawal policy page, the payments page. A reader who needs the number should read the number off the page that owns it, not off the FAQ that points to it.
Where the binding answer lives
For each common question, there is a home document, and the reader should know which one it is. For anything about a bonus — eligibility, wagering, game weighting, expiry — the home document is the promotions terms page, and specifically the terms block attached to the individual offer, not the general promotions overview. For anything about money movement — deposit limits, withdrawal minimums, fees, processing windows, method availability — the home document is the payments or banking page, and the cashier itself is the most current version, because it shows only the methods available to the reader's own account at that moment. For anything about verification — which documents, which formats, how long review takes, what happens if a document is rejected — the home document is the verification or KYC policy page. For anything about account closure, self-exclusion or cooling-off periods, the home document is the responsible gaming page, and the account settings screen shows the options currently offered.
When the FAQ page does not state one of these items, that absence is itself information. If the FAQ mentions verification but does not list the accepted documents, the reader should not guess from a forum or a review site; the document list is on the verification policy page, and if that page also does not state it, the only way to get a binding list is through the support channel, because the operator can change the list without updating a summary page. If the FAQ mentions withdrawal times but gives no figure, the reader should not assume a number from a third-party site; the figure is method-specific and is stated in the cashier or the withdrawal policy page, and if neither states it, the answer is that the operator has not published a binding figure, which means the reader should ask support before committing funds they need by a date.
How to use an FAQ page without being misled
The disciplined way to use an FAQ page is to read it as a directory. Find the question that matches the reader's situation, note the process it describes, then identify the page that owns the figure or rule that process depends on, and read that page. If the FAQ says a withdrawal requires verification, the next step is the verification policy page, not the FAQ's summary of it. If the FAQ says a bonus has wagering, the next step is the promotions terms page, not the FAQ's paraphrase. If the FAQ says a deposit method is available, the next step is the cashier, because the cashier shows only what the reader's own account can use. The FAQ shortens the search; it does not end it.
A reader should also be alert to the difference between a process answer and a term answer on the same page. "Upload your document in the verification section" is a process answer: it tells the reader what to do, and it is safe to follow. "Withdrawals are processed within two business days" is a term answer: it tells the reader what the operator aims to do, and it is a summary of a policy that may carry method-specific exceptions. The process answer can be acted on immediately. The term answer should be checked against the page that owns the term, especially when the reader's money is already in motion. The FAQ page is most useful to a player who uses it as the first step in that check, not as the last word.
The same discipline applies to questions the FAQ page does not contain at all. A missing FAQ entry is not a sign that the question has no answer; it is a sign that the answer lives in a document the FAQ does not summarize, or in the support channel. If the reader's question is about a specific transaction, a specific bonus, or a specific account state, the FAQ page is the wrong place to look, and the reader should go to the account itself or to support. The FAQ page is a general reference, and a general reference cannot see the reader's file.
FAQ
Does the Hh98 FAQ page state the wagering requirement for a bonus?
It may summarize that a wagering requirement applies, but the multiple itself is a term of the individual promotion, not a property of the FAQ page. The binding figure is on the promotions terms page for the specific offer, and it can differ from one promotion to the next. A reader should read the figure off that page before accepting the bonus.
Can the FAQ page tell me why my withdrawal is delayed?
No. A withdrawal delay depends on the reader's verification state, the payment method, and the operator's processing queue, none of which the FAQ page can see. The FAQ can describe the general order of operations — verification before release, review before approval — but the status of a specific withdrawal is in the account's transaction history or with support.
Where does the FAQ page get its information?
An FAQ page is a summary written by the operator to answer common questions, and it draws on the operator's own policy pages: terms and conditions, promotions terms, payment policy, verification policy and responsible gaming pages. It is not an independent source. When the FAQ and a policy page conflict, the policy page is the one that binds, because it is the document updated when a term changes.
What should I do if the FAQ page does not answer my question?
Identify which kind of question it is. If it is about a specific account, transaction or bonus, open the account and read the relevant screen, or contact support, which can see the reader's file. If it is about a general term, read the policy page that owns that term. If neither states the answer, the operator has not published a binding figure, and support is the only channel that can give one.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Hh98, and it states no figure or status for them, so the operator's own FAQ and policy pages are the only binding source.
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.
