The decision an FAQ page settles
A player lands on an operator's FAQ page because something is stuck: a deposit has not appeared, a document was rejected, a withdrawal is sitting in a pending state, or a bonus has not credited. The first question the reader should ask is not "what does the answer say" but "which answers on this page can I rely on when money is involved." An FAQ page is a collection of general explanations about how the site's processes normally work. It is not a contract, it is not an account statement, and it is not a ruling on the reader's specific situation. That distinction decides what the page is for.
Proper publishes its FAQ as one of the standard support pages, and like any operator's FAQ it has a particular job: to reduce the number of routine questions that would otherwise go to a support team. That means it covers the questions that have the same answer for nearly every player — where to find the cashier, what documents are commonly requested, what a wagering requirement is in general. It does not, and structurally cannot, cover the questions whose answer changes from account to account. The reader who treats the FAQ as the final word on their own case will sometimes be right and sometimes badly wrong, and the page itself gives no way to tell which is which.
The useful move is to read the FAQ as a map of where the binding answer lives. A good FAQ entry does not just say "you need to verify your identity"; it points to the verification page, names the document types that page commonly asks for, and explains what happens after upload. The reader's job is to notice what the entry does not say: it does not say that their specific document will be accepted, that their specific withdrawal will clear, or that their specific bonus will be released. Those outcomes are decided by the operator's systems and by the terms that govern the account, not by the FAQ paragraph.
Where an FAQ answer is binding, and where it is not
The first split to make is between process and outcome. Process questions are the ones an FAQ can answer usefully: how to open the cashier, how to find a transaction history, how to start a withdrawal, how to upload a document, how to contact support. These steps are the same for every account, so a general answer is accurate for every reader. Outcome questions are different: whether a withdrawal will be approved, whether a bonus will be credited, whether an account will be closed, whether a document will pass review. Those depend on the reader's own history, balance, verification state and the current terms, and no general page can answer them. A reader who asks the FAQ "why is my withdrawal pending" and reads the answer as a promise is making a category error.
There is a second split, between what the FAQ states and what it merely refers to. Some entries summarise a rule: "bonuses are subject to wagering requirements." That statement is true but useless for deciding anything, because the number that matters — the multiple, the time limit, the game weighting — lives in the promotions terms, not in the FAQ. Other entries point outward: "see the withdrawal policy for processing times." That is the honest form of an FAQ answer, because it does not pretend to contain the figure. The reader should treat any FAQ sentence that mentions a rule without stating the figure as a signpost, not as the rule itself.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit routes available | Payment methods are added and removed by the operator without notice to existing players | The cashier page, shown after login, is the only current list |
| Withdrawal processing time | Depends on the method, the verification state of the account, and the operator's current queue | The withdrawal policy page, not the FAQ summary |
| Document types required for KYC | The list can differ by jurisdiction, account tier, and the operator's current rules | The verification or KYC page, and any request message sent to the account |
| Wagering multiple on a bonus | Each promotion carries its own terms, and they are revised between campaigns | The specific promotion's terms page, not the general FAQ |
| Fees on a withdrawal | Fees vary by method, amount and the operator's current schedule | The cashier or withdrawal page, shown at the moment of the request |
| Account closure and self-exclusion | The available options and their consequences are set by policy and by regulation | The responsible gaming page and the account settings area |
The table above is the reading discipline for any FAQ page, including Proper's. For each item that matters, there is a place where the answer is stated in a form the reader can act on, and that place is almost never the FAQ entry itself. The FAQ is the index, not the text.
What a reader can and cannot hold the operator to
There is a practical question underneath all of this: if the FAQ says one thing and the operator's system does another, what can the reader do? The answer depends on what kind of statement is in dispute. If the FAQ describes a process — "click Withdraw, choose a method, enter an amount" — and the reader follows it and the system behaves differently, the reader has a reasonable complaint, because the operator published a description of its own interface. If the FAQ states a figure — a processing time, a fee, a limit — and the figure turns out to be wrong, the reader's position is weaker, because the FAQ is not the document that binds the operator to a number. The terms and conditions, the withdrawal policy, and the promotion terms are the documents that carry the numbers, and they are the ones that matter in a dispute.
This is not a point about fairness; it is a point about document hierarchy. An operator's FAQ is a support document. Its purpose is to reduce contact volume, not to create obligations. The pages that create obligations are the ones written as policies or terms, and the operator's own systems are the final arbiter of what happens to an account. A reader who wants to hold the operator to something should be able to point to the policy page that states it, not to the FAQ paragraph that summarised it. If the FAQ is the only place a rule appears, the rule is not reliably enforceable, because the operator can revise a support page without notice and without creating a contract.
The same logic applies in reverse. A reader who relies on the FAQ to learn what they are allowed to do — how many accounts they may hold, whether they may use a VPN, what happens if a bonus is abused — is reading the wrong document. Those rules are in the terms, and the terms are the document the operator will cite when it acts. The FAQ may mention the rule, but the mention is not the rule. The reader's protection is to read the governing document before acting, and to treat the FAQ as a pointer to it.
Which questions the FAQ cannot answer at all
Some questions are structurally outside the reach of any FAQ page, and a reader who asks them there will get either silence or a generic answer that does not apply to them. The clearest class is account-specific questions: "why is my withdrawal pending", "why was my document rejected", "why did my bonus not credit". These have answers, but the answers live in the account's own transaction history, verification state and bonus ledger, not in a public support page. The FAQ can say what the possible reasons are; it cannot say which reason applies to this reader. The only place to get that answer is the account itself, or a support channel that can see the account.
A second class is current-figures questions. "What is the minimum deposit", "how long do withdrawals take", "what is the wagering requirement on the welcome bonus". These have answers that change over time, and an FAQ page is a snapshot that may be out of date the day after it is published. The reader who needs the current figure must read the page that states it at the moment of the transaction: the cashier for deposit limits, the withdrawal page for processing times, the promotion terms for wagering. An FAQ entry that states a figure is a convenience, not a commitment, and the reader should verify it against the live page before acting on it.
A third class is legal-status questions. "Is this site licensed", "is it safe", "is it audited". An FAQ page may carry a statement about these things, but the statement is marketing unless it names the regulator, the licence number, and the place where the reader can verify it. A reader who wants to know the operator's status should look for the licence information on the operator's own site and then verify it against the regulator's public register. The FAQ is not the place where that verification happens. The absence of a named regulator from the FAQ is not itself evidence of anything, but it does mean the FAQ has not answered the question.
The three questions every FAQ reader should ask
Before acting on anything read in an FAQ, a reader can run three checks. First, is this a process or an outcome? If it is a process, the FAQ is probably accurate. If it is an outcome, the FAQ is at best a description of what usually happens, and the reader's own case may differ. Second, does this entry state a figure, or does it point to a page that states the figure? If it points, follow the pointer and read the figure there. If it states a figure, treat the figure as a summary and verify it against the governing page before relying on it. Third, is there a document that binds the operator to this statement? If the only source is the FAQ, the statement is weak. If there is a policy or terms page, that page is the one that matters.
These checks do not make the FAQ useless. They make it usable. An FAQ is a genuinely useful thing when it is read as an orientation document: it tells the reader what exists, where to find it, and what the operator's own vocabulary means. The reader who uses it that way will find the cashier faster, understand the verification flow better, and know which page carries the number they need. The reader who uses it as a contract will occasionally be fine and occasionally be surprised, and the surprise will usually be expensive.
FAQ
Can I rely on the Proper FAQ for withdrawal times?
The FAQ may summarise typical processing times, but the binding figure is on the withdrawal policy page and in the cashier at the moment of the request. Processing time depends on the method, the account's verification state and the operator's current queue, so a general answer cannot be accurate for every reader. Read the withdrawal page before requesting a withdrawal.
Why does the FAQ not tell me why my withdrawal is pending?
Because that answer depends on the reader's own account: the method used, the verification state, the amount, and any review flags. The FAQ can list possible reasons, but it cannot see the account. The answer is in the account's transaction history and any message the operator has sent, or from a support channel that can access the account.
Where do I find the wagering requirement for a bonus?
Not in the FAQ, except as a general statement that wagering applies. The specific multiple, time limit and game weighting are in the terms of the specific promotion, and they change between campaigns. Read the promotion's own terms page before claiming the bonus.
Does the FAQ tell me which documents I need for verification?
It may list the document types commonly requested, but the exact list for a given account depends on the operator's current rules and the account's jurisdiction and tier. The verification page and any request message sent to the account are the authoritative sources.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Proper, and it states no figure or status for them. Proper's own FAQ page and the policy pages it links to are the only binding sources for the answers a reader needs.
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.
