A reader opens an operator's FAQ page in the middle of a transaction: a deposit has not arrived, a withdrawal is showing as pending, or a document was rejected during verification. The FAQ is the first place they look, and it is also the place where a wrong assumption costs the most. The page answers general process questions, but it does not answer questions about a specific account, and it does not override the terms that govern the transaction.
The two jobs an FAQ performs
An operator FAQ does two distinct things. First, it explains the mechanism of ordinary processes: how a deposit route works, what documents verification asks for, what a wagering requirement means in practice, how a self-exclusion request is handled. Second, it tells the reader where the binding version of each rule lives. The FAQ is a map, not a contract. A sentence in the FAQ can describe a withdrawal route, but the withdrawal policy page is the document that states the route as a condition of the account.
The distinction matters because the FAQ is usually maintained separately from the legal pages. An FAQ can be updated for clarity without a change to the terms, and it can fall out of date while the terms page remains binding. When the two conflict, the terms page governs. A reader who quotes the FAQ in a dispute has quoted a summary; a reader who quotes the terms page has quoted the rule.
Which questions the FAQ answers bindingly
A question is answerable by the FAQ only when the answer does not depend on the reader's account state or on a figure that changes. "What documents are accepted for verification?" is a process question: the list of accepted document types is a stable fact about the operator's procedure. "Why was my document rejected?" is not: the answer depends on the specific document, the account, and the stage of verification. The FAQ can list the common reasons for rejection, but only the message attached to the reader's own submission states the actual reason.
The same split applies to payments. "Which withdrawal methods are available?" is a process question, and the FAQ can answer it in general terms. "When will my withdrawal arrive?" depends on the method, the amount, the verification state of the account, and the operator's processing queue. The FAQ can describe the stages a withdrawal passes through, but the cashier or the withdrawal page shows the current state of a specific request.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted document types for verification | Document rules change when the operator updates its KYC procedure or when a document type is withdrawn as acceptable | Verification or KYC section of the FAQ, cross-checked against the account verification page |
| Deposit methods and any per-method conditions | Payment routes are added and removed, and a method may carry different limits by region or account tier | Deposit or payments section of the FAQ, with the cashier as the live source for the reader's own account |
| Withdrawal processing stages | The number of stages and the order in which they happen can change without notice, and a specific request may sit longer at one stage than another | Withdrawal section of the FAQ, with the withdrawal page showing the live status of a request |
| Bonus wagering requirement definition | The definition of a wagering requirement is stable, but the multiple attached to a specific bonus changes by promotion | Promotions terms page, not the FAQ; the FAQ explains the concept, the terms page states the number |
| Self-exclusion and cooling-off process | The process steps are stable, but the available periods and the method of applying them can be revised | Responsible gaming or account tools section of the FAQ, with the account settings page as the live control |
| Currency and conversion handling | Exchange rates move continuously, and the rate applied to a transaction is the rate at the moment of processing, not the rate at deposit | Payments or currency section of the FAQ, with the cashier or the transaction record showing the applied rate |
Where the FAQ stops and the account begins
Every question that begins with "my" is outside the FAQ's reach. "My deposit has not arrived," "my withdrawal is pending," "my document was rejected," "my bonus is not showing" - these are account-state questions. The FAQ can describe the normal flow and the common failure points, but it cannot look at the reader's account. The answer to a "my" question lives in the account itself: the transaction history, the cashier, the verification centre, or the message attached to the specific action.
This is not a defect of the FAQ; it is the boundary of the format. A help page written for every reader at once cannot contain the answer that is true for exactly one reader. The operator's support channel exists precisely because the FAQ cannot answer account-specific questions. A reader who has read the FAQ and still cannot resolve a transaction should use the support channel, and should bring the transaction ID or the document reference with them, because that is what turns a general question into a specific one.
What changes and what stays fixed on an FAQ page
An FAQ page is edited more often than the legal pages, and the edits are usually small: a method is added to the deposit list, a document type is removed from the verification list, a processing stage is renamed. These edits do not change the reader's obligations, but they do change what the page says about the operator's process. A reader who relies on a printed copy of an FAQ is reading a snapshot that may no longer describe the process.
The terms pages change less often, and when they change, the change is usually announced or dated. The FAQ changes silently. For that reason, the FAQ is a good place to learn what to look for, and a poor place to store a fact that will be quoted later. If a reader needs to rely on a statement, they should find the same statement on the terms page or the policy page that governs it, and note the date on that page.
Reading the FAQ against the terms pages
The correct use of an FAQ is as an index. A reader who wants to know what a wagering requirement is reads the FAQ's explanation; a reader who wants to know what wagering requirement applies to their bonus reads the promotion's terms. A reader who wants to know what documents are accepted reads the FAQ; a reader who wants to know why their document failed reads the message on their verification screen. The FAQ tells the reader which page to open next, and it tells them what to look for when they open it.
When the FAQ and a terms page disagree, the terms page is the binding document. The FAQ is a summary, and a summary can be out of date without anyone noticing. The terms page is the document the operator will point to in a dispute. A reader who notices a conflict should treat the terms page as the rule and the FAQ as the explanation that has fallen behind.
What the FAQ cannot tell a reader about Sportshoka
No FAQ page can state the current status of a reader's account, the reason a specific transaction is held, or the amount that will be credited after a conversion. These are facts that exist only in the account record, and they change from minute to minute. The FAQ can describe the categories of these facts, and it can tell the reader where to look, but it cannot carry the fact itself. A reader who asks the FAQ a question that only the account can answer has asked the wrong page.
The same is true of anything that depends on current terms: a bonus amount, a wagering multiple, a withdrawal limit, a fee. These are printed on the pages that define them, and they change by promotion, by region, and by account tier. The FAQ can explain what a wagering multiple is and how it is applied, but the number itself is on the promotion's terms page, and the number on that page is the only number that binds.
FAQ
Can I rely on the FAQ if it conflicts with the terms page?
No. The terms page is the binding document. The FAQ is a summary that can fall out of date. If the two disagree, the terms page governs, and the reader should treat the FAQ's version as an explanation that has not been updated.
Why does the FAQ not answer my specific account question?
Because the answer depends on your account state, and the FAQ is written for every reader at once. The answer to a specific question lives in the account itself: the transaction history, the cashier, the verification centre, or the support channel.
How do I know if an FAQ answer is still current?
You cannot know from the FAQ alone. Cross-check the statement against the terms page or policy page that governs it, and note the date on that page. If the FAQ and the terms page disagree, the terms page is current.
What should I bring when I contact support about a transaction?
The transaction ID or the document reference. That is what turns a general question into a specific one, and it is the only way support can look at your account rather than at the FAQ.
This page is an independent summary of what an operator FAQ page covers and where it stops. It is not published by Sportshoka, and it states no figure or status for that operator; Sportshoka's own FAQ and terms pages are the only binding source for what the operator states.
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.
