A player who opens the On Stardustcasino FAQ is usually not looking for a definition of the word "FAQ." They are standing in front of a blocked deposit, a withdrawal that has not arrived, or a verification request they do not understand, and they want the one sentence that tells them what to do next. The first thing to understand about an operator FAQ is therefore not what it contains, but what kind of document it is: a convenience layer. It restates, in shorter form, rules and processes that live somewhere else. It is not the place where those rules are made, and it is not the place where they are changed.
The split between what an FAQ can and cannot settle
An operator FAQ sits between two very different kinds of reader questions. The first kind is about process: which document to send for verification, which payment route appears in the cashier, which button starts a self-exclusion, which page carries the wagering multiple for a bonus. Those questions have answers that are the same for every player, and an FAQ can state them usefully. The second kind is about the reader's own account: why a specific withdrawal is still pending, whether a particular document was accepted, whether a bonus is active on a particular balance. No static FAQ page can answer those, because the answer depends on data the FAQ does not have. The reader's task is to recognise which kind of question they are holding, because that decides whether the FAQ is the end of the search or only the signpost to it.
Where process answers are binding
For process questions, the FAQ is a summary, not a source. A sentence in an FAQ that names a document type for verification is only as good as the verification page it points to. A sentence about withdrawal routes is only as good as the cashier at the moment of the withdrawal. The binding answer always lives in the instrument that executes the process: the cashier, the verification upload screen, the terms page, the responsible-gaming tool. The FAQ's value is that it tells the reader which instrument to open. Its limit is that the instrument can change without the FAQ changing at the same time.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Operators revise document lists as their risk procedures change | The verification or KYC page, not the FAQ |
| Withdrawal routes for a deposit method | Payment availability shifts by region, method and processor | The cashier at the moment of withdrawal |
| Wagering multiple for a bonus | Promotions are reissued with new terms; old terms do not carry forward | The promotions terms page for that specific offer |
| Self-exclusion and cooling-off controls | Tool names and durations are revised as responsible-gaming policies change | The responsible-gaming page and the account settings |
| Withdrawal processing time | Depends on method, verification status and the operator's current queue | The withdrawal policy page, read together with the account status |
| Deposit minimums and maximums | Set per payment method and adjusted without notice | The cashier or deposit page for the chosen method |
Why the FAQ cannot answer account-specific questions
A withdrawal that has been pending for three days is not a process question. It is a state question. The answer depends on whether the account has passed verification, whether the chosen method has a holding period, whether the amount triggered an additional review, and whether the operator's payment team has released the transaction. None of that is knowable from a static page. An FAQ that attempts to answer it would have to invent a player, and no operator FAQ does that. What a well-built FAQ does instead is tell the reader which channel carries the account-specific answer: the account's withdrawal history, the support channel, or the notification that accompanies the hold. The reader who expects the FAQ to resolve a state question will read it as a failure. The reader who expects it to route them to the state-bearing screen will read it as a map.
What it means when the FAQ does not state an item
Silence in an FAQ is not an oversight. It is a boundary. If the FAQ does not state a withdrawal processing time, that is because the time is not a property of the FAQ; it is a property of the method and the account. If the FAQ does not state a wagering multiple, that is because the multiple is a property of a specific promotion, not of the operator as a whole. If the FAQ does not name a testing laboratory or a regulator, that is because those are not FAQ material; they belong to footer pages and certificate pages. The absence of an item from the FAQ is therefore itself an answer: it tells the reader that the item is governed elsewhere, by an instrument that can carry the binding value. A reader who treats FAQ silence as a gap to be filled by assumption is reading the wrong document.
Reading an FAQ against its own terms
The most common misreading of an operator FAQ is to treat it as a contract. It is not. A contract is a document whose terms bind both parties. An FAQ is a document whose terms bind no one until they are read back against the instrument that executes them. The correct reading posture is therefore comparative: when the FAQ says a thing, the reader asks which page makes that thing true, and opens that page. When the two conflict, the executing instrument wins. When the FAQ says nothing, the reader asks which page could have said it, and opens that page. The FAQ is the index, not the text.
What the reader should take away
An operator FAQ is worth exactly as much as the pages it points to. It can save a reader from searching the site for a process answer that is already summarised. It cannot save a reader from the work of confirming that answer against the live instrument, because the live instrument is the only thing that acts on the reader's money, account or data. The reader who leaves the FAQ with the name of the right page and the right screen has used it correctly. The reader who leaves with a number they read in a sentence and never confirmed has not.
FAQ
Can I rely on the On Stardustcasino FAQ for withdrawal times?
No static FAQ can state a withdrawal time that applies to a particular reader, because the time depends on the method, the verification status and the operator's current processing queue. The FAQ can name the page that governs withdrawals and the channel that shows the account's own status. The binding answer is on that page and in the account's withdrawal history, not in the FAQ.
Why does the FAQ not list every payment method?
Payment availability is a property of the cashier at the moment of the transaction, and it varies by region, method and processor. An FAQ that listed methods would go stale. The FAQ's job is to point to the cashier, where the reader sees the methods available to their account.
Does the FAQ tell me whether my verification document was accepted?
No. Document acceptance is an account state, not a process rule. The FAQ can list the document types that are generally requested, but the acceptance or rejection of a specific upload is visible only in the account's verification screen or in the notification the operator sends.
If the FAQ and the terms page disagree, which one applies?
The terms page applies. The FAQ is a summary, and summaries can lag behind the instrument they summarise. Where the two conflict, the document that executes the rule is the binding one, and that is the terms page, the cashier, or the verification screen, not the FAQ.
This page is an independent summary of what an operator FAQ is for and where its authority stops; it is not published by On Stardustcasino, and it states no figure or status for that operator, whose own FAQ and governing pages 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.
