The situation an FAQ page is built for
A player lands on an operator's FAQ page with a specific question already formed: how long a withdrawal takes, why a document was rejected, whether a deposit method can also be used for payouts, what happens when a bonus is forfeited. The FAQ is the operator's attempt to answer those questions once, in writing, so that support staff do not answer the same ticket a thousand times. That makes the FAQ useful for process questions and nearly useless for account questions, and the reader who confuses the two walks away with an answer that was never binding.
I8's FAQ page sits inside that same structure. It is a collection of short answers to recurring questions, organised by topic. The page is published by the operator and updated by the operator, which means it carries the operator's framing of its own processes. It is not an independent source, and it is not a contract. What it can do is tell a reader which steps exist, which documents are usually requested, and which routes are available. What it cannot do is tell a reader what will happen to their own account, because no static page can know that.
The useful way to read any operator FAQ is to treat it as a map of processes, not a promise of outcomes. The map shows the roads. The reader's own account file shows which roads are open to them.
What an FAQ can answer bindingly
An FAQ is strongest where the answer is the same for every reader. Those are the questions about procedure: what documents are accepted for verification, how to find the cashier, what the wagering requirement means in general, how to set a deposit limit, where the transaction history is displayed. The operator can state those things once and be done, because they do not depend on who is asking.
Within that category, three kinds of answer are genuinely binding. The first is a list of accepted document types for KYC. If the FAQ says a passport, national ID card or driving licence is accepted, that list applies to every account. The second is the route a process takes: a withdrawal is requested in the cashier, moves to a pending state, is reviewed, and is then released or declined. The FAQ can describe that sequence accurately for all players. The third is the location of controls: where the responsible gambling tools are, where the bonus terms are linked, where the transaction history sits. Those locations do not vary by account.
What the FAQ cannot do is answer a question whose answer depends on the reader's own file. Whether a specific withdrawal will be approved, whether a specific document will pass review, whether a specific deposit method is available in the reader's country - those are account questions. The FAQ can say what usually happens, but the binding answer is in the account itself, and the reader should read the page that way.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted KYC document types | The list is updated when the operator changes its verification vendor or policy | The verification section of the FAQ, and the document upload screen in the account |
| Withdrawal processing sequence | The steps are stable, but the time each step takes is not stated in a static FAQ | The FAQ's withdrawal section for the sequence; the cashier for the current status |
| Deposit methods available | Method lists vary by country, currency and account status | The cashier after login, not the FAQ, which can only list methods in general |
| Bonus wagering requirement | The multiple is set in the promotion terms, which the operator can change between promotions | The promotions terms page linked from the specific offer, not the FAQ |
| Responsible gambling controls | The controls themselves are stable, but limits available may vary by jurisdiction | The responsible gambling page and the account settings |
| Support contact channels | Channels and hours can change without notice | The contact or support page, and the footer of the operator's site |
Where the FAQ stops being the source
The line an FAQ cannot cross is the line between a process and a rate. A process is a sequence of steps: request, review, release. A rate is a number attached to that process: a processing time, a fee, a wagering multiple, a minimum or maximum amount. An FAQ can describe the process accurately. It cannot state the rate bindingly, because the rate lives in a different document that the operator can change without rewriting the FAQ.
That distinction matters most for money. A reader who wants to know how long their withdrawal will take is asking for a rate. The FAQ may say that withdrawals are reviewed in order, or that verification must be complete first. Those are process statements and they are true. But the number of hours or days is a rate, and the only place that number is binding is the withdrawal policy or the terms page, read at the moment the withdrawal is requested. If the FAQ repeats a number, it is repeating a snapshot that may already be stale.
The same applies to bonuses. The FAQ can explain what a wagering requirement is: a multiple of the bonus amount that must be wagered before winnings from the bonus can be withdrawn. It cannot state the multiple for a specific promotion, because that multiple is set in the promotion's own terms, and two promotions running at the same time can carry different multiples. The reader who reads the FAQ for the multiple and stops there has read the wrong page.
For I8, the same structure applies. The FAQ is where a reader learns what a wagering requirement is and why it exists. The promotion terms page, linked from the specific offer, is where the reader learns what the requirement is for that offer. The two pages do different jobs, and neither substitutes for the other.
What the FAQ cannot know about the reader's account
An FAQ is a static page. It is the same for every visitor, whether they are logged in or not. That is its strength for process questions and its weakness for account questions. A static page cannot know whether the reader's account has passed verification, whether a document was rejected and why, whether a withdrawal is pending review, or whether a bonus is active. Those facts live in the account database, not in the FAQ.
This creates a specific failure mode. A reader whose withdrawal is delayed reads the FAQ, finds a sentence that says withdrawals are processed within a certain window, and concludes that something is wrong with their account. But the FAQ sentence is a general statement about the process, not a promise about their withdrawal. The reader's own withdrawal has a status, visible in the cashier, and that status is the only binding answer to the question "where is my money". The FAQ cannot know the answer, and the reader should not expect it to.
The same applies to verification. The FAQ can list the documents that are generally accepted. It cannot say whether the reader's specific document will pass. A document can be rejected for reasons the FAQ cannot anticipate: the image is blurry, the name does not match the account, the document is expired, the address is not visible. The FAQ cannot list every rejection reason, and it does not try. The rejection message in the reader's account is the binding answer, and the FAQ is only a general guide to what is usually requested.
Account-specific questions therefore have a different home. The binding answer is in the account itself: the cashier for withdrawal status, the verification screen for document status, the bonus section for active offers, the transaction history for deposits and payouts. The FAQ is the map. The account is the territory.
Which questions the FAQ answers better than support
There is a class of question where the FAQ is more reliable than a live support agent. Support agents work from scripts and have limited authority. They can misstate a policy under time pressure, or give an answer that applies to a different jurisdiction. The FAQ is reviewed and published, which means it goes through an approval process that a live chat message does not.
For process questions, the FAQ is therefore the better first stop. "What documents do I need to verify my account?" "How do I set a deposit limit?" "Where do I find my transaction history?" "What does a wagering requirement mean?" These are the questions the FAQ is built to answer, and the answer is the same whether the reader asks the FAQ or a support agent. Reading the FAQ first saves the reader from waiting in a queue for an answer that is already published.
But the FAQ is not better for everything. For a question about the reader's own account, support is the only channel that can see the account. The FAQ cannot see it. The reader who asks the FAQ "why was my withdrawal declined" gets a general answer about common decline reasons. The reader who asks support the same question gets the specific reason for their withdrawal. The two answers are different in kind, and the reader should know which kind of question they are asking before they choose where to look.
The practical rule is simple: if the question begins with "how do I", the FAQ is probably the right place. If it begins with "why is my", the account or support is the right place. The FAQ answers the first kind. The account answers the second.
Reading the FAQ against the terms
An FAQ is a summary. It is written to be read quickly, which means it omits detail. The terms and conditions are the full text. Where the two conflict, the terms control, because the terms are the contract and the FAQ is a paraphrase. A reader who relies on the FAQ for a legal question has read a summary and mistaken it for the source.
This matters most for anything that can cost money. A bonus offer, a withdrawal condition, a fee, a limit - these are all defined in the terms, and the FAQ can only summarise them. The summary may be accurate, but it is still a summary. The reader who wants the binding answer must read the terms page for the specific offer or policy, not the FAQ's summary of it.
For I8, the same reading discipline applies. The FAQ is a useful orientation. It tells the reader what kinds of pages exist and what they govern. It does not replace any of them. The reader who reads the FAQ and stops has read the map but not the contract, and the contract is where the money lives.
This page is an independent summary of what an operator FAQ page covers and where it stops. It is not published by I8, and it states no figure or status for them; the operator's own FAQ and terms pages are the only binding sources for what the operator states.
FAQ
Does the I8 FAQ state withdrawal times?
An FAQ can describe the withdrawal process, but any number attached to that process is a rate that lives in the withdrawal policy or terms page. The FAQ may repeat a number, but the binding figure is the one on the policy page at the moment the withdrawal is requested. If the FAQ does not state a time, the reader should read the withdrawal policy.
Can the FAQ tell me why my document was rejected?
No. The FAQ can list the document types that are generally accepted, but it cannot see the reader's account or the specific rejection reason. The rejection message in the account's verification screen is the binding answer. The FAQ is a general guide, not an account lookup.
Is the FAQ the same as the terms and conditions?
No. The FAQ is a summary written for quick reading. The terms and conditions are the full contract. Where the two conflict, the terms control. For anything that can cost money - a bonus, a fee, a withdrawal condition - the terms page is the binding source.
Should I read the FAQ before contacting support?
For process questions - how to verify, how to set a limit, where to find history - the FAQ is often faster and more consistent than a live agent. For account questions - why a withdrawal is pending, why a document failed - support is the only channel that can see the account. Match the question to the channel.
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.
