The moment a player opens an FAQ
A player lands on Spindimension's FAQ page because something has already gone slightly wrong, or because they are about to do something that could go wrong. The deposit did not arrive. A withdrawal is pending and nobody has said why. A document was rejected. The live chat queue is long. The FAQ is the page a player reads when they want the answer without waiting for a person, and the first thing to understand about it is what kind of page it is: a curated list of questions the operator expects to receive often. It is not a contract, not a policy, and not a substitute for the terms and conditions. Spindimension's FAQ page is where the operator publishes its own explanations of common processes, and the reader's job is to know which of those explanations are binding and which are only a summary.
The FAQ page answers questions about how things work in general: where to find the deposit screen, what documents are commonly requested for verification, how to locate the withdrawal button, how to contact support. It does not answer questions about this particular reader's account. No FAQ page can, because the answer depends on data the FAQ does not have: the reader's balance, their verification status, their payment method, their jurisdiction, and the current version of the terms that apply to them. A well-read FAQ is a map of the operator's processes, not a verdict on the reader's situation.
What an FAQ can answer bindingly
The binding content of an FAQ is procedural. When Spindimension's FAQ page states the steps to make a deposit, the reader can rely on that sequence: open the cashier, choose a method, enter an amount, confirm. When it lists the documents commonly accepted for identity verification, that list is a starting point, though the final word belongs to the verification team's request. When it explains that withdrawals are processed through the same route as deposits where possible, that is a process statement, not a promise about any specific transaction.
The distinction that matters is between a route and a result. An FAQ can bind the route: where the button is, which menu contains the setting, what order the screens appear in. It cannot bind the result: whether this deposit will clear, whether this withdrawal will be approved, whether this document will pass. The reader should treat every process answer in the FAQ as reliable, and every outcome answer as a summary that the operator's own systems will confirm or deny case by case.
Where the FAQ stops
The FAQ stops at the boundary of the reader's account. Any question that begins with "why" and ends with "my" — why is my withdrawal pending, why was my document rejected, why is my bonus not showing — is outside what a static FAQ page can answer. The FAQ may list common reasons: a withdrawal can be pending because verification is incomplete, because the amount exceeds a threshold, because the payment method requires manual review. But it cannot say which of those reasons applies to this reader. The only place that answer exists is in the reader's account history, in the email the operator sent, or in a conversation with support.
The same boundary applies to anything that depends on current terms. Bonus percentages, wagering requirements, minimum deposits, maximum withdrawals, processing times — all of these are figures that operators change. An FAQ page may repeat them, but the repeated figure is only as current as the last time someone edited the FAQ. The binding version lives on the promotions page, the banking page, or the terms and conditions, and those pages carry a version date or a "last updated" line that the FAQ often lacks. When the FAQ and the terms disagree, the terms win, because the terms are the document the reader accepted.
Reading the FAQ against the binding sources
The practical method is to use the FAQ as an index. The reader finds the question, reads the summary answer, and then follows the link or the named page to the binding source. If the FAQ says "see our withdrawal policy," the reader should open that policy and read the clause that applies to their amount and method. If the FAQ says "contact support with your document," the reader should note that the FAQ is not the channel for submitting it; the support ticket or the upload screen is.
When the FAQ does not name a source, that absence is itself information. A question about self-exclusion that is answered with a general description but no link to the responsible gambling page tells the reader that the tool exists but the FAQ is not where it is activated. A question about withdrawal times that gives no range tells the reader that the figure is either method-dependent or subject to change, and the only place to read it is the banking page or the cashier screen at the moment of the request.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit methods available | Payment providers are added and removed; availability differs by country and account status | Cashier screen after login, not the FAQ |
| Withdrawal processing time | Depends on method, verification status, and current queue; operators revise published ranges | Banking or withdrawal policy page, and the withdrawal request itself |
| Documents required for verification | The list varies by jurisdiction, deposit method, and risk assessment | The verification request sent to the reader's account, not the FAQ's general list |
| Bonus wagering requirement | Each promotion carries its own multiple; operators change offers frequently | The specific promotion's terms, not a general FAQ entry |
| Minimum deposit or withdrawal | Thresholds differ by payment method and are revised | Cashier screen and banking page |
| Self-exclusion procedure | The steps are stable, but the cooling-off period options may change | Responsible gambling page and account settings |
| Support contact channels | Hours and available channels change; some channels are account-gated | Contact page and the support widget after login |
What the FAQ cannot tell the reader about their own account
The hardest questions for an FAQ to answer are the ones that feel most urgent. A pending withdrawal has a specific reason, and that reason is attached to a specific transaction ID. A rejected document has a specific defect, and that defect is described in the rejection notice. A locked account has a specific trigger, and that trigger is in the operator's risk log. The FAQ can list the categories of reason — verification, payment method, terms breach, responsible gambling intervention — but it cannot assign one to the reader's case. The reader who reads the FAQ hoping for a verdict will find only a menu of possibilities, and the correct next step is always the same: open the account, read the notification, and if it is unclear, ask support to state the reason in writing.
There is one exception worth naming: process questions that are genuinely the same for every account. How to find the deposit button, how to download a transaction history, how to change a password, how to set a deposit limit. These are stable because they do not depend on the reader's data. The FAQ can answer them bindingly, and the reader can act on them immediately. The line is whether the answer would be the same if a different person with a different account asked it. If yes, the FAQ is sufficient. If no, the FAQ is only the first step.
When the FAQ and the terms disagree
Operators update their terms more often than they update their FAQ pages. A reader who finds a figure in the FAQ and then finds a different figure in the terms should treat the terms as current and the FAQ as stale. The same applies to figures repeated in promotional banners, affiliate sites, or support chat: none of them override the terms, and none of them override the specific promotion's own conditions. The FAQ is a convenience, not a source of rights. If a dispute ever reaches a stage where the reader needs to point to a document, the document that matters is the one with the version date and the acceptance record.
This is not a criticism of the FAQ as a genre. It is a description of what the genre is. An FAQ is a help document, written by the operator's support team, maintained on whatever schedule the operator chooses. It carries no version number, no acceptance checkbox, and no audit trail. The reader who understands that will use it for what it is good at — finding the right page, the right button, the right channel — and will not ask it to be something it is not.
FAQ
Does the Spindimension FAQ tell me why my withdrawal is pending?
No. The FAQ can list common reasons for a pending withdrawal — incomplete verification, method review, amount thresholds — but it cannot say which reason applies to your transaction. The binding answer is in your account's withdrawal history, in the notification the operator sent, or in a written reply from support.
Can I rely on the deposit methods listed in the FAQ?
Only as a general indication. The methods available to you depend on your country, your account status, and the operator's current provider agreements. The cashier screen after login is the only place that shows the methods you can use right now.
Where do I find the wagering requirement for a bonus?
Not in the FAQ, unless the FAQ links to the specific promotion. Each bonus carries its own wagering multiple, and operators change offers frequently. The binding figure is on the promotion's own terms page, and you should read it before you accept the bonus, not after.
What should I do if the FAQ answer conflicts with the terms and conditions?
Follow the terms. The terms are the document you accepted when you opened the account, and they carry a version date. The FAQ is a summary that may be out of date. If the conflict matters to a transaction, write to support and ask them to confirm in writing which version applies.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Spindimension, and it states no figure or status for the operator, whose own FAQ and terms 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.
