A player who opens the Capitaleq FAQ is usually mid-task: a deposit has not landed, a withdrawal is pending, a document was rejected, or a bonus did not appear. The page they are reading is not the task itself, and treating it as the final word on their account is the most common way a small delay becomes a long one. An FAQ is a map of the operator's processes, not a record of what has happened to one reader's money.
Where the FAQ sits between the player and the binding documents
Every operator publishes several layers of text. At the bottom sit the terms and conditions, the privacy policy, the AML policy, and any payment or bonus terms. Those are the binding layer: when a dispute reaches support, those documents decide it. Above them sit process pages - the cashier, the verification portal, the promotions page - which show live data for the logged-in reader. The FAQ sits above both. It is a summary of what those layers contain, written for speed, not for adjudication.
That position gives the FAQ a specific power and a specific limit. Its power is that it can state, in plain language, how a process normally runs: which document types are accepted for verification, which routes exist for deposits and withdrawals, which steps must be completed before a first withdrawal. Its limit is that it cannot state what is true of one reader's account at this moment. A balance, a pending status, a document rejection with a reason attached, a bonus that has or has not been credited - none of those live in a static FAQ page. They live in the account, and the FAQ can only point to the screen where the reader sees them.
Which questions the FAQ can settle on its own
The questions an FAQ answers bindingly are the ones whose answer does not depend on the reader. If the question is "what documents does verification require", the answer is a list, and that list is the same for every player at that moment. If the question is "which withdrawal methods appear in the cashier", the answer is a route list, and it is the same for every player in the same region and currency. If the question is "what happens if I do not complete verification before withdrawing", the answer is a process consequence written in the terms, and the FAQ can repeat it.
Those answers are binding because they are copies of the binding layer. The reader can rely on them in the sense that the operator has published them as its own summary. But the reader should still confirm the current version, because an FAQ is revised less often than the terms it summarises. A route list that was accurate when the FAQ was last updated may not match the cashier today, and the cashier is the screen that executes the transaction.
Which questions the FAQ cannot settle
The questions an FAQ cannot answer are the ones whose answer is a fact about the reader. "Where is my withdrawal" is not answerable by a static page, because the answer is a status that changes minute to minute. "Why was my document rejected" is not answerable, because the rejection carries a reason attached to that specific upload. "Why did my bonus not appear" is not answerable, because the answer depends on the deposit amount, the time of the deposit, the bonus code entered, and the terms in force at that moment.
When a reader asks one of those questions of the FAQ, the page can only describe the process that governs the answer. It can say that withdrawals move through a queue, that documents are reviewed in the order received, that bonuses are credited after the qualifying deposit settles. It cannot say which stage this reader's item has reached. The reader who expects the FAQ to know their account has misread the page's function, and the reader who waits for the FAQ to update instead of opening the account or contacting support has chosen the slowest available route.
What changes, and where the current version lives
Several items on an FAQ page are time-sensitive, and the reader should treat any figure read there as a snapshot, not a promise. The table below separates the items that stay fixed in structure from the items that move, and names the screen or document where the live version is read off.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Compliance requirements are revised as regulations and internal risk rules change | The verification portal, which shows the current list for the logged-in account |
| Deposit methods and minimums | Payment providers are added and removed; limits are adjusted by region and currency | The cashier, at the moment a deposit is initiated |
| Withdrawal routes and processing stages | Route availability depends on the deposit method used and the account's verification state | The withdrawal screen, which shows only the routes available to that account |
| Bonus eligibility and wagering terms | Promotions are time-limited and their terms are revised between campaigns | The promotions page for the specific offer, plus the terms linked from it |
| Document review or withdrawal queue times | Volumes change daily; any stated window is an estimate, not a guarantee | The account's pending items, or support's response to a specific query |
| Contact hours and support channels | Staffing and channel availability are operational decisions that change without notice | The contact page, and the support widget if one is present |
The pattern is consistent: the FAQ describes the shape of the process, and the live screen executes it. A reader who copies a figure from the FAQ and later finds a different figure in the cashier has not been misled by the FAQ; they have read a summary as if it were the source.
What the FAQ is not
An FAQ is not a substitute for the terms and conditions. It is not a record of the reader's account activity. It is not a channel for support, though it may link to one. It is not, in most cases, a place where the operator states regulatory status, licence numbers, or audit details; those belong on dedicated pages, and their absence from the FAQ tells the reader nothing about their existence elsewhere.
It is also not a negotiation tool. A player who quotes the FAQ in a dispute with support is quoting a summary, and support will resolve the dispute against the terms, not against the summary. The FAQ's value is orientation: it tells the reader which document governs their question, and which screen shows the answer. The reader who uses it that way reaches the binding source faster, and the reader who treats it as the binding source reaches a dead end.
How to read the FAQ for a specific problem
The useful sequence is to read the FAQ backwards from the problem. Start with the symptom: a withdrawal is pending, a document was rejected, a bonus is missing. Find the FAQ entry that names that symptom. Note which document or screen the entry points to. Open that document or screen. Do not stop at the FAQ's description of the process, because the description cannot tell the reader where their item sits in it.
If the FAQ entry for a withdrawal says that withdrawals pass through a verification check and then a processing queue, the reader's next step is not to re-read the entry. It is to open the withdrawal screen and see whether the item shows as pending verification or pending processing. If the FAQ entry for a document rejection says that rejections carry a reason, the reader's next step is to open the rejection notice and read the reason. The FAQ has done its job when it has told the reader which screen to open, not when it has answered the question itself.
When the FAQ does not name a screen for the reader's symptom, that absence is itself information. If the reader cannot find an entry for a payment method they expected to see, the method may not be offered to their region or currency, and the cashier is the screen that settles it. If the reader cannot find an entry for a bonus they expected to receive, the promotion may have ended, or the reader may not have met its qualification, and the promotions page is the screen that settles it. An FAQ that is silent on a point has not failed; it has declined to summarise something that only the live screen can state.
FAQ
Does the Capitaleq FAQ state the current withdrawal time?
No FAQ page can state a current withdrawal time for a specific reader, because that time is a status attached to the reader's account, not a fixed property of the operator. The FAQ may describe the stages a withdrawal passes through, but the only screen that shows which stage this withdrawal has reached is the withdrawal screen in the logged-in account. Any time window read in an FAQ is an estimate of the process, not a promise about this transaction.
Can I rely on the FAQ's list of accepted verification documents?
The FAQ can state which document types the operator accepts in general, and that list is binding as a description of the process. But the list that matters for a specific account is the one shown in the verification portal, because it is filtered by the reader's region, currency and account state. A document type that appears in the FAQ but not in the portal is not accepted for that account at that moment.
Why does the FAQ not answer my question about a missing bonus?
A missing bonus is a fact about the reader's deposit, timing, code entry and the terms in force at that moment. No static page can know those facts. The FAQ can describe the general conditions under which bonuses are credited, but the answer for this reader is on the promotions page for the specific offer, or in the account's bonus history, or in a support response that can see the transaction.
Is the FAQ the same as the terms and conditions?
No. The FAQ is a summary written for speed; the terms are the binding document. Where the two conflict, the terms govern. The FAQ's function is to point the reader to the term that applies, not to replace it. A reader who quotes the FAQ in a dispute is quoting a summary, and support will resolve the dispute against the terms.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Capitaleq, and it states no figure or status for them, so the operator's own FAQ and the documents it links to are the only binding source for any question about their processes.
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.
