The situation an FAQ page addresses
A player lands on an operator's FAQ page in one of two states. Either they have hit a wall in a process — a deposit did not arrive, a withdrawal is pending, a document was rejected — or they are about to start one and want to know the route before they commit money. In both cases the FAQ is a map of the operator's standard procedures. It is not a contract, and it is not a ruling on the player's account.
For Xcolander, the FAQ page is the place where the operator publishes its general answers to the questions that come up most often. The page exists to reduce the number of individual support tickets, so it is written for the average case. A reader should treat every sentence on it as the operator's description of its own default process, not as a promise that the reader's specific case will follow that default.
What an FAQ can answer bindingly
There is a class of question where an FAQ is genuinely authoritative, because the answer is a description of a route or a list, not a decision. These are the items a reader can take from the page and act on:
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Which document types are accepted for identity verification | The operator may add or remove accepted document categories as its compliance process changes | The account verification or KYC section of the FAQ, cross-checked against the terms page |
| Which deposit methods are listed as available | Payment routes are added and withdrawn regularly, and availability can depend on the player's country | The deposits section of the FAQ, but the cashier screen at the moment of deposit is the live list |
| Which withdrawal routes are listed as available | Withdrawal routes do not always mirror deposit routes, and the operator can change them without notice | The withdrawals section of the FAQ, cross-checked against the withdrawal policy page |
| What the standard verification steps are | The order and number of steps can change as the operator updates its compliance procedure | The FAQ's account or verification section, with the final word in the terms page |
| Whether a bonus requires a separate opt-in | Promotion mechanics change between campaigns, and an FAQ entry may describe a previous campaign | The specific promotion's own terms, not the FAQ |
| What happens when a withdrawal is flagged for review | The review trigger and the documents requested can change with the operator's risk policy | The FAQ's withdrawal section, with the binding trigger in the AML or withdrawal policy |
These are the questions where the FAQ is the right first stop. The answer is a list, a sequence, or a route, and the reader can compare what the FAQ says against what the cashier or the account screen shows at the moment of action.
What an FAQ cannot answer bindingly
There is a second class of question where the FAQ is structurally incapable of giving the binding answer. These are the questions whose answer depends on the reader's own account, on the current terms, or on a decision the operator has not yet made. For these, the FAQ can describe the general policy, but it cannot rule on the reader's case.
The most important of these is any question about a specific transaction. A player who asks "why is my withdrawal still pending" will not find the answer in an FAQ, because the answer depends on the player's own verification status, the payment method used, the amount, and the operator's current review queue. The FAQ can say what the standard review steps are, but it cannot say which step the player's withdrawal is at.
The same applies to any question about a bonus. An FAQ may describe how bonuses work in general — that they carry wagering requirements, that they have expiry dates, that certain games contribute differently — but the binding numbers for a specific bonus live on that bonus's own terms page. A reader who reads a wagering multiple in an FAQ and then claims a bonus whose terms page states a different multiple is bound by the terms page, not the FAQ.
Account-specific questions are the third category. Whether a document will be accepted, whether a withdrawal route is available to a particular player, whether a self-exclusion request has been processed — none of these can be answered by a general FAQ. The reader must open the account screen, the cashier, or a support ticket, because the answer is generated from the reader's own data, which the FAQ does not have.
Where the binding answer lives instead
For every question where the FAQ is not binding, there is a specific document or screen that is. The reader's job is to know which one applies, because the FAQ will often point to it but will not reproduce it.
| Question type | Where the binding answer lives | Why the FAQ is not enough |
|---|---|---|
| Wagering requirement for a specific bonus | The promotion's own terms page, linked from the promotion itself | The FAQ describes bonuses in general; each campaign has its own numbers |
| Withdrawal minimum or maximum for a specific method | The withdrawal policy page and the cashier screen at the moment of withdrawal | Limits vary by method and can change without the FAQ being updated |
| Which documents are needed for a specific withdrawal | The withdrawal review screen and any email or ticket from the operator | The FAQ lists the standard set, but the operator can request more for a specific case |
| Whether a payment method is available to a specific player | The cashier screen, which filters methods by the player's country and status | The FAQ lists methods in general, not per-player availability |
| Whether a self-exclusion is in force | The account settings screen and the confirmation from the operator | The FAQ describes the tool, but the reader's own status is account data |
The pattern is consistent: the FAQ is a map of the operator's standard routes, while the binding answer is a document or screen that carries the reader's own data or the current numbers. A reader who treats the FAQ as the final word on a specific case is reading the wrong document.
What changes most often on an FAQ page
An FAQ page is one of the most frequently edited pages on an operator's site, because it tracks the operator's current procedures. The items that change most often are the payment method lists, the verification document lists, and the promotional mechanics. A reader who bookmarks an FAQ entry and returns to it weeks later may find that the entry has been rewritten or removed.
Payment method lists change because the operator adds and removes providers, and because a method's availability can shift by country. Verification document lists change because compliance requirements change, and because the operator may decide that a document type it previously accepted is no longer sufficient. Promotional mechanics change with every campaign, and an FAQ entry that describes a bonus from a previous campaign may be out of date even if the page itself has not been edited.
The practical consequence is that a reader should not rely on an FAQ entry for any number or list that matters to a transaction they are about to make. The cashier screen, the promotion's own terms page, and the withdrawal policy page are the live documents. The FAQ is the orientation, not the contract.
What it means when the FAQ does not state an item
Absence on an FAQ page is itself information. If the FAQ does not state a withdrawal minimum, that does not mean there is no minimum; it means the minimum is stated elsewhere, or that the operator has chosen not to publish it in the FAQ. If the FAQ does not list a deposit method, that does not mean the method is unavailable; it means the reader must check the cashier screen.
The same applies to verification. If the FAQ does not say which documents are accepted, the reader cannot assume that a particular document will be accepted. The operator's compliance team will decide, and the decision will be communicated through the account screen or a support ticket, not through the FAQ.
An FAQ that is silent on an item is not a loophole. It is a sign that the binding answer lives in a document the reader has not yet opened.
How to use the FAQ alongside the other pages
The correct reading order for a player who has a question about a process is: first the FAQ, to learn the standard route; then the specific document that governs the transaction, to learn the binding numbers; then the account screen or cashier, to see the live state. The FAQ is the first step, not the last.
For a deposit question, the reader checks the FAQ for the general list of methods, then opens the cashier to see which methods are available to them. For a withdrawal question, the reader checks the FAQ for the standard review steps, then opens the withdrawal policy page for the limits and triggers, then opens the withdrawal screen to see the state of their own request. For a bonus question, the reader checks the FAQ for the general mechanics, then opens the promotion's own terms page for the numbers.
This order works because each document has a different job. The FAQ describes the route. The terms page states the rules. The account screen shows the reader's own data. No one of these can do the job of the others.
FAQ
Does the Xcolander FAQ tell me my withdrawal status?
No. The FAQ describes the standard withdrawal review steps, but the status of a specific withdrawal is account data. The reader must open the withdrawal screen or a support ticket to see where their own request stands.
Can I rely on the wagering requirement stated in the FAQ?
No. The FAQ may describe wagering requirements in general, but the binding multiple for a specific bonus is on that bonus's own terms page. If the two differ, the terms page governs.
What should I do if the FAQ does not list my deposit method?
Check the cashier screen, which filters methods by the player's country and status. The FAQ lists methods in general, not per-player availability, and its absence from the FAQ does not mean the method is unavailable.
Where do I find the documents required for verification?
The FAQ lists the standard document types, but the operator can request more for a specific case. The binding list for a particular withdrawal or account review is communicated through the account screen or a support ticket, not the FAQ.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Xcolander, 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.
