The page a reader opens after something already went wrong
A casino FAQ is usually read backwards. The player does not browse it to learn how the site works; they open it because a deposit did not arrive, a withdrawal is held, a document was rejected, or a bonus did not credit. By the time the FAQ is on screen, the reader is already inside a process and wants to know which step they are on. That changes what the page can do. It can list the documents an account verification normally requires. It can describe the route a withdrawal takes. It can say which conditions apply to a bonus in general. What it cannot do is tell the reader what is happening to their own account right now, because that answer depends on data the FAQ does not hold.
For 1cashup, the FAQ is the operator's own page, published on its own site. It is the place where the operator states its standard process answers. A reader who treats it as a live account status page will be misled. A reader who treats it as a map of the operator's fixed procedures will get most of what they came for.
Which questions the format can answer bindingly
An FAQ is a list of questions the operator has chosen to answer in advance. That gives it a specific authority. When the page states which documents are accepted for identity verification, that list is the operator's published requirement. When it states that withdrawals return to the deposit method before any other route is offered, that is the operator's stated order of operations. When it states that a wagering requirement must be met before a bonus balance becomes withdrawable, that is the operator's condition, and the reader can hold the operator to it.
The binding force comes from publication. A statement on the operator's own FAQ page is a representation the operator makes to every reader. If the cashier later behaves differently, the reader has something to point to. That is not true of what a support agent says in chat, which may be a paraphrase, a mistake, or a statement about a different account state. The FAQ is written once and applies to everyone; that is exactly what makes it useful and exactly what limits it.
What the page cannot settle, and why
The same fixedness that makes an FAQ binding also makes it blind. It cannot see the reader's account. It cannot know whether a deposit was rejected by the payment provider or by the operator's risk rules. It cannot know whether a document was rejected because it was illegible, expired, or already on file under a different name. It cannot know whether a bonus was not credited because the reader opted out, because the deposit method was excluded, or because the promotion had ended before the deposit settled.
Those answers depend on the reader's own data, and the FAQ has none. A question like "why is my withdrawal still pending" is not answerable by a static page. The page can list the common reasons a withdrawal is held. It cannot rank those reasons for this reader. The reader who needs the account-specific answer has to move from the FAQ to the channel that can see the account: the cashier's transaction history, the verification status screen, or a logged-in support request.
Where each kind of answer lives
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted identity documents | Regulatory or risk requirements may add or remove document types | FAQ verification section, and the upload screen's accepted-file list |
| Withdrawal method order | Payment routes are added or closed, and the order may depend on deposit history | FAQ withdrawal section, and the cashier's method list for the specific withdrawal |
| Bonus wagering multiple | Promotions change, and different bonuses carry different multiples | FAQ promotions section, and the specific promotion's own terms page |
| Deposit processing time | Payment provider delays and operator review rules both vary | FAQ deposits section, and the transaction's own status line in the cashier |
| Verification review window | Volume and document quality change the operator's queue | FAQ account section, and the verification status screen after upload |
| Self-exclusion or cooling-off options | Responsible-gaming tools are updated and may have different scopes | FAQ responsible-gaming section, and the account settings or support request |
The table shows the split. The left column is what the FAQ is good at: naming the items that exist and the standard rule. The right column is what the FAQ cannot do: tell the reader which of those standard rules applies to their specific transaction at this moment. A reader who reads the FAQ and still has a question has not failed to read carefully; they have reached the edge of what a static page can say.
The FAQ as a map of where the operator keeps its binding documents
One underused function of an FAQ is navigation. The page does not just answer questions; it points to the documents that answer questions the FAQ itself cannot. A good FAQ entry on withdrawals will not restate the entire withdrawal policy. It will state the common case and link to the policy page, where the full conditions live. An entry on bonuses will state the headline rule and link to the promotion terms, where the wagering multiple and game-weighting table are printed. An entry on verification will state the document list and link to the privacy policy, where the retention period for those documents is described.
For 1cashup, the reader should treat the FAQ as an index. The entry that seems too short is often short because the operator has put the full rule on a different page and expects the reader to follow the link. The binding answer is on the linked page, not in the FAQ's summary of it. If the FAQ and the linked page conflict, the linked page is the more specific document and the one the reader should rely on.
What changes, and what the reader should re-read
An FAQ is not a contract, but parts of it function like one. The parts that function like a contract are the parts that state conditions: which documents are accepted, which methods are available, which wagering multiple applies, which countries are served. Those parts change when the operator changes its rules. A reader who read the FAQ six months ago and returns today may find that the accepted document list has grown, or that a payment method has been removed, or that the self-exclusion tool now has a different minimum period.
The parts that do not change are the process descriptions. A withdrawal still moves from request to review to release. A verification still moves from upload to review to approval or rejection. A bonus still moves from credit to wagering to withdrawable balance. The mechanics are stable; the parameters around them are not. The reader who needs a parameter should read it on the day they act on it, not rely on a memory of the FAQ from an earlier visit.
The practical rule is simple. Before a deposit, read the deposit section for the method list and any minimum. Before a withdrawal, read the withdrawal section for the method order and any hold conditions. Before claiming a bonus, read the promotion's own terms, not just the FAQ's summary of them. The FAQ is the map; the specific page is the ground.
When the FAQ is not enough
There is a class of question the FAQ cannot answer even in principle: anything that depends on the reader's own history. Whether a document was rejected because of a name mismatch. Whether a withdrawal is held because the deposit method is closed. Whether a bonus was not credited because the reader had already claimed a different bonus in the same period. These are account-state questions. The FAQ can list the possible causes; it cannot identify the actual cause.
When the reader reaches that point, the FAQ has done its job. It has told them which documents exist, which rules apply, and which channel to use next. The next step is the logged-in support request, the cashier's transaction detail, or the verification screen. The reader should bring the FAQ's stated rule with them, because that is the standard against which their account state will be measured. If the FAQ says a withdrawal returns to the deposit method first, and the cashier offers a different route, the reader has a specific, answerable question to put to support.
FAQ
Can the 1cashup FAQ tell me why my withdrawal is still pending?
No. The FAQ can list the common reasons a withdrawal is held, but it cannot see your account or your specific transaction. The answer that applies to you is in the cashier's transaction detail or a logged-in support response.
If the FAQ and the withdrawal policy page disagree, which one applies?
The policy page. The FAQ is a summary, and the specific policy page is the fuller statement of the operator's conditions. Where they conflict, the more specific document governs.
Do I need to re-read the FAQ before every deposit or withdrawal?
For the parts that state parameters — method lists, minimums, document types, wagering multiples — yes. Those parameters change, and the version you read months ago may no longer be current. The process descriptions are stable, but the numbers and lists around them are not.
What should I do if my situation is not covered by any FAQ entry?
Use the logged-in support channel. The FAQ is a fixed page; your situation depends on data it does not hold. Bring the closest FAQ entry with you, because it states the standard rule your case will be measured against.
This page is an independent summary of what a casino FAQ covers and where it stops; it is not published by 1cashup, and it states no figure or status for that operator, whose own FAQ and linked policy pages are the only binding source for its rules.
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.
