The question a player brings to an FAQ is rarely the question the FAQ answers
A player lands on Fortunica's FAQ because a deposit has not arrived, a withdrawal is stuck, a document has been rejected, or a bonus did not behave the way the promotion page implied. The FAQ is the first place most players look, and it is also the place most likely to give an answer that is true for the average account but false for theirs. An operator FAQ is written before the reader's problem exists. It describes the standard route, the standard document list, the standard trigger. It cannot know whether the reader's account has a flag, a pending verification step, a payment method that behaves differently, or a promotion whose terms have changed since the FAQ was last edited.
What a reader needs from this kind of page is therefore not a single sentence that settles their case. They need to know which items on it are binding, which are illustrative, and which cannot be answered by any FAQ at all because the answer lives in the reader's own account or in a document that changes more often than the FAQ does. The rest of this article walks through that split for Fortunica's FAQ, item by item.
What an operator FAQ governs, and what it only describes
An FAQ page on a casino site is a curated list of questions the operator expects to receive often. Its answers are written by the operator's staff, and they describe the operator's own processes: how a deposit is initiated, which documents are normally requested for verification, what happens when a withdrawal is requested, how a bonus is activated. Those descriptions are useful because they tell the reader what the operator believes its own process to be. They are not the process itself.
The binding version of any process lives in the instrument that defines it. A deposit route is defined by the cashier and the payment page. A withdrawal condition is defined by the withdrawal policy and the terms that applied to the deposit. A document requirement is defined by the verification or KYC policy. The FAQ is a summary of those instruments, and a summary can lag behind the instrument. When the two disagree, the instrument wins, and the support team will apply the instrument, not the FAQ.
This is the first thing to understand about Fortunica's FAQ: it is a reading aid, not a contract. A player who relies on an FAQ sentence that is six months old, while the terms page has been updated twice since, will be held to the terms page. The FAQ does not carry the power to override it.
The three kinds of answer an FAQ can give
Questions on an operator FAQ fall into three groups, and they are not equally reliable. The first group is process questions: what are the steps to deposit, how does a player open an account, where does a player find their transaction history. These answers are stable because the steps themselves rarely change, and when they do, the FAQ is usually updated at the same time as the interface. A reader can treat a process answer as a reasonable guide to what the operator's site will show them.
The second group is route and document questions: which payment methods are available, which identity documents are accepted, which currencies the cashier supports. These answers are more fragile. Payment methods change when a provider ends an agreement or a region becomes unavailable. Document lists change when regulation or internal policy changes. The FAQ may name a method that the cashier no longer offers, or a document that is no longer sufficient. The reader must confirm these against the live cashier and the verification page, not against the FAQ.
The third group is account-specific questions: why is my withdrawal pending, why was my document rejected, why did my bonus not activate. No FAQ can answer these bindingly, because the answer depends on the reader's own account state, and the FAQ was not written about that account. The only binding answer comes from the account itself, the support team, or the specific communication the operator sent. A reader who asks the FAQ "why is my withdrawal pending" and receives a list of common reasons has not received an answer about their withdrawal. They have received a list of possibilities, and they still need to check their account.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Available deposit methods | Provider agreements and regional availability shift over time | The cashier page, not the FAQ |
| Accepted identity documents | Internal policy and regulatory requirements change | The verification or KYC policy page |
| Withdrawal processing steps | The operator's queue, the method, and the account's verification state all affect it | The withdrawal policy and the reader's own account |
| Bonus activation conditions | Promotion terms are updated more often than the FAQ | The specific promotion's terms page |
| Currency support | Currencies can be added or removed without an FAQ update | The cashier or account settings |
| Verification triggers | Thresholds and risk rules change | The AML or KYC policy page |
Where the FAQ stops: figures and statuses
An FAQ page is the wrong place to look for any number that matters to the reader's money. Withdrawal times, deposit minimums, bonus percentages, wagering multiples, fee amounts - none of these belong in an FAQ as a binding statement, because all of them are set by documents that change on their own schedule. If Fortunica's FAQ names a withdrawal time, that time is a snapshot of the withdrawal policy at the moment the FAQ was written. The policy may have changed since. The reader must read the withdrawal policy for the figure that applies to their request.
The same is true of statuses. An FAQ cannot tell the reader that the operator is licensed, that a game is certified, or that a payment method is secure. Those are statements about the operator's standing, and they are made on the pages that carry the licences, certificates, and provider agreements. If the FAQ repeats them, it is repeating, not establishing. The reader who wants to verify a licence must look at the licence page and the regulator's register, not at the FAQ.
When the FAQ does not state a figure, that absence is not a gap in the FAQ. It is the correct design. The FAQ's job is to route the reader to the document that carries the figure. A reader who treats the FAQ as the source of the figure has misread the page's function.
What changes on an FAQ, and what stays fixed
The parts of an FAQ that stay fixed are the parts that describe the site's structure: how to navigate to the cashier, where the account settings live, how to open a support ticket. These are unlikely to change without a redesign, and a redesign is announced. The parts that change are the parts that describe the operator's commercial and compliance choices: payment methods, bonus structures, document requirements, processing times, and any sentence that contains a number.
A reader should therefore read an FAQ twice. The first reading is for navigation: where do I go to do the thing I want to do. The second reading is for staleness: which of these answers contains a figure or a named method, and does the live page still say the same thing. The second reading is the one that protects the reader's money.
There is also a category of FAQ answer that changes without the FAQ itself changing: any answer that says "contact support" or "check your account". The support team's answer will depend on the reader's account state, which changes constantly. The FAQ's job here is to point, not to answer.
What a reader should do when the FAQ and the live page disagree
The rule is simple: the live page wins. If the FAQ says a withdrawal takes three days and the withdrawal policy says five, the policy is the binding document. If the FAQ says a document is accepted and the verification page rejects it, the verification page is the binding document. If the FAQ names a payment method and the cashier does not show it, the cashier is the binding interface. The FAQ is a summary, and a summary is always subordinate to the thing it summarises.
A reader who encounters a disagreement should not argue with support using the FAQ as evidence. Support will apply the live instrument, and the reader's only effective move is to read the live instrument and understand what it requires. The FAQ is useful for finding the instrument. It is not useful for overriding it.
There is one exception to the live-page-wins rule, and it is narrow. If the operator's own support team gives a written answer that contradicts the live page, and the reader can show that the answer was given after the live page was last updated, the reader may have a basis to ask for the answer to be honoured. But that is a support matter, not an FAQ matter, and it depends on the operator's own complaint process. The FAQ plays no part in it.
Reading Fortunica's FAQ without reading it as a promise
The correct way to read an operator FAQ is as a map of the operator's site, not as a set of promises. The map tells the reader where the cashier is, where the verification page is, where the withdrawal policy is, where the promotion terms are. The map does not tell the reader what the cashier will show, what the verification page will require, or what the promotion terms will say. Those are read off the pages themselves.
This is why the most useful sentence on any FAQ is often the one that says "for the current terms, see the terms page" or "for your specific case, contact support". Those sentences are not evasions. They are the FAQ doing its actual job: routing the reader to the only place where a binding answer exists.
A reader who approaches Fortunica's FAQ with this understanding will get more from it than a reader who expects the FAQ to settle their case. The first reader uses the FAQ to find the right page, reads the right page, and acts on what it says. The second reader reads a summary, treats it as a ruling, and is surprised when the cashier or the support team applies a different rule. The difference is not in the FAQ. It is in how the reader reads it.
FAQ
Can I rely on the Fortunica FAQ for withdrawal times?
No. Withdrawal times are set by the withdrawal policy and by the reader's own account state, and both change. The FAQ may describe a typical process, but the binding figure is on the withdrawal policy page and in the reader's account. Read those, not the FAQ.
Why does the FAQ not answer my specific account question?
Because the FAQ is written for the average account, not for any particular one. Questions about a pending withdrawal, a rejected document, or a bonus that did not activate depend on the reader's own account state, which the FAQ cannot know. The answer lives in the account, in the operator's communication, or with support.
What should I do if the FAQ says something different from the terms page?
Follow the terms page. The FAQ is a summary, and the terms page is the binding instrument. If the two disagree, the terms page is what the operator will apply, and it is what the reader should read before acting.
Where do I find the binding version of a rule the FAQ mentions?
On the page that governs that rule. Deposit rules are on the cashier and payment pages, withdrawal rules on the withdrawal policy, bonus rules on the specific promotion's terms, and verification rules on the KYC or AML policy. The FAQ points to these pages; it does not replace them.
This page is an independent summary of what an operator FAQ page covers and where its answers stop being binding. It is not published by Fortunica, and it states no figure or status for the operator; Fortunica's own FAQ and the documents it links to are the only binding sources for the reader's account.
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.
