The question a FAQ page settles
A player arrives at Pmdice's FAQ page usually holding a specific problem: a deposit that has not appeared, a withdrawal that is stuck on a status word, a document the verification team keeps rejecting, or a rule the player only half-remembers from the terms. The FAQ is the first place a reader looks because it is the fastest page to search. But the important thing to understand before reading any FAQ is what kind of authority the page has. A FAQ answers process questions: which button to press, which document format is accepted, which route a withdrawal follows, which department handles a dispute. It does not answer account questions. It cannot tell a specific player why their deposit failed, when their withdrawal will clear, or whether their bonus is active. Those answers depend on data that lives in the player's account, not in a static help page.
So the right way to read a Pmdice FAQ is as a map of processes, not as a ruling on a particular case. When the FAQ says what a verification team normally asks for, that is a general description. When the reader's own account shows a different request, the account is the more specific and more current source. The FAQ tells the reader where to look and what the common paths are; it does not override the cashier, the terms, or a message from support.
What a FAQ can state bindingly
Some things on a FAQ page are stable enough that the page can state them without needing a time stamp. These are the structural facts about how the site works: the sequence of steps in a deposit, the order in which a withdrawal passes through review, the list of documents that belong to a standard verification, the difference between a pending and a completed transaction, the place where a self-exclusion request is submitted. These items are binding in the sense that they describe the operator's own procedure, and the procedure changes rarely.
But even here the reader should notice the difference between a description of a process and a promise about an outcome. A FAQ can say that a withdrawal passes through a review stage before it is released. That is process. It cannot say that a particular withdrawal will pass review, or that review will finish by a certain date. The moment a sentence on the page starts to look like a guarantee about a specific player's money, the reader is reading beyond what the page can carry. The binding place for that is the withdrawal policy, the terms, or a written reply from support that references the player's account.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted document formats for verification | Compliance requirements shift; a format accepted last year may be rejected this year | The verification or KYC section of the FAQ, and any message the verification team sends to the player's account |
| Deposit methods shown to a player | Availability depends on the player's country, currency and account status, all of which change | The cashier page inside the player's account, not the FAQ's general list |
| Withdrawal route for a deposit method | Routes are rebalanced; a method that previously allowed withdrawals may become deposit-only | The withdrawal page of the cashier, and the withdrawal policy |
| Minimum or maximum transaction amount | Limits are adjusted by currency, method and account tier, and are repriced periodically | The deposit or withdrawal screen for the chosen method, and the terms |
| Bonus eligibility and wagering multiple | Promotions are replaced frequently; the multiple attached to one offer does not carry to the next | The promotions terms page for the specific offer, not the FAQ |
| Self-exclusion and cooling-off controls | The available durations and the effect on pending withdrawals are set by policy and can be revised | The responsible gaming page and the account settings, with support confirmation |
Where the FAQ stops and the account begins
The boundary every reader needs is the one between a general rule and an account-specific fact. A FAQ can say that a deposit must be confirmed on the blockchain or by the payment provider before it is credited. That is true for every player. It cannot say whether the reader's deposit has been confirmed, whether the amount the reader sent matches the amount the cashier expects, or whether the reader's account is under review. Those are facts about one account, and they are only visible inside that account or in a support conversation about it.
This boundary matters most when money is stuck. A player who reads the FAQ, sees that deposits are normally credited after confirmation, and concludes that their own deposit must therefore be about to arrive is making an inference the FAQ does not support. The correct move is to check the transaction in the account's deposit history, confirm the status shown there, and if the status is unclear, open a support request that includes the transaction reference. The FAQ can tell the player which reference number to copy and where to paste it; it cannot tell the player what the outcome will be.
The same applies to verification. A FAQ often lists the documents a player may be asked to provide: proof of identity, proof of address, proof of payment method. But whether a particular player is asked for one, two or all three, and whether a particular document is accepted, depends on the player's profile, the amounts involved, and the compliance team's assessment. The FAQ's list is a preparation guide, not a ruling. The reader should treat any document request that appears in the account or in an email as the operative one, and should not assume the FAQ's shorter list means the request is a mistake.
What changes and how to read around it
Every FAQ page has a shelf life, and the reader should read it with that in mind. The items most likely to change are the ones tied to money: limits, fees, processing windows, available methods, and bonus conditions. These are not fixed properties of the operator; they are commercial settings that the operator adjusts. A FAQ written when a method was available in a certain country may still describe that method in general terms after the method has been withdrawn for that country. A FAQ that mentions a processing window may be describing a target that the operator no longer commits to. The page itself does not always carry a revision date, so the reader cannot assume the text reflects today's settings.
The way to read around this is to treat the FAQ as a directory, not as a source of figures. When the FAQ mentions a limit, the reader should not copy the number from the FAQ; they should go to the cashier, select the method, and read the limit shown there. When the FAQ mentions a processing time, the reader should look at the withdrawal policy or the confirmation message on a specific withdrawal. When the FAQ mentions a bonus, the reader should open the promotions page and read the terms attached to the offer they are considering. The FAQ's job is to point to the place where the current figure lives, not to carry the figure itself.
There is one exception to this directory principle. When the FAQ describes a structural rule that does not change with market conditions — for example, that a withdrawal can only be sent to a method previously used for deposit, or that a self-exclusion cannot be reversed on request — that rule is likely stated in the same form in the terms. Even then, the terms are the binding document, and the FAQ is a summary. If the FAQ and the terms appear to conflict, the terms govern, because they are the document the player accepted.
Questions the FAQ cannot answer at all
Some questions are outside the reach of any FAQ, and the reader should not waste time looking for them. The first is any question about the reader's own money: where a specific deposit is, why a specific withdrawal is pending, whether a specific bonus has been credited. The FAQ cannot see the reader's account. The answer lives in the account's transaction history, the cashier's status column, or a support ticket.
The second is any question about the operator's current commercial terms: the exact wagering multiple on today's welcome offer, the exact fee on a particular withdrawal method, the exact minimum deposit for a particular currency. These are stated on the pages that sell or process those things, and they change too often for a static FAQ to be reliable. The reader who needs a figure should read it off the screen where the transaction is made, not off a help page.
The third is any question about the operator's regulatory or corporate status. A FAQ may describe the operator's procedures, but it is not the place where a licence, a certificate or an audit is evidenced. A reader who wants to confirm a licence should look for the regulator's own register or the operator's licensing page, and should not treat a FAQ sentence as proof. The absence of such a sentence from the FAQ proves nothing either; the FAQ is not the operator's compliance filing.
How to use the FAQ without being misled
The practical method is to read the FAQ twice with two different questions. First, read it to learn the shape of the process: what are the steps, what are the stages, what are the documents, what are the routes. That reading is safe, because the shape of a process changes slowly. Second, read it to collect pointers: for each item that matters to the reader's situation, note which page or screen the FAQ says carries the current value. That reading is what turns the FAQ from a source of answers into a map of sources.
When the FAQ does not state an item the reader expected to find, that absence is itself information. If the FAQ says nothing about a minimum withdrawal, the reader should not assume there is none; they should check the cashier. If the FAQ says nothing about a particular payment method, the reader should not assume the method is unavailable; they should check the deposit screen. If the FAQ says nothing about a bonus's wagering multiple, the reader should not assume the bonus is wager-free; they should read the promotion's own terms. A silent FAQ is not a guarantee; it is a gap, and the gap is filled by the page that carries the item.
The single most important habit is to prefer the account and the transaction screen over the FAQ whenever the two disagree. The FAQ is a general description written for an average reader at an earlier time. The account is the operator's current statement about this specific player. When a player's deposit screen shows a method the FAQ does not list, the deposit screen is right. When a withdrawal status says something different from the FAQ's description of the status word, the account is right. The FAQ is a starting point, never the final word.
FAQ
Can the Pmdice FAQ tell me where my deposit is?
No. The FAQ describes the deposit process in general, but it cannot see your account or your transaction. The place to check is your account's deposit history, which shows the status of each transaction. If the status is unclear, a support request with the transaction reference is the next step.
Does the FAQ's list of accepted documents mean my documents will pass?
No. The FAQ lists the types of documents a verification team commonly asks for, but acceptance depends on the specific document's quality, expiry and match with your account details. The verification team's request in your account is the operative one, and only their review decides acceptance.
If the FAQ mentions a processing time, is that a promise?
No. Processing times on a FAQ are general descriptions of how the process works, not commitments about a specific withdrawal. The withdrawal policy and the status shown on your withdrawal are the binding sources. A FAQ's time frame can also be out of date, so check the policy rather than relying on the help page.
What should I do if the FAQ and the terms seem to conflict?
Follow the terms. The terms are the document you accepted when you opened the account, and they are updated more carefully than a help page. If the conflict affects money, take a note of both texts and raise it with support, but treat the terms as the governing document until support says otherwise.
This page is an independent summary of what an operator FAQ page covers and where it stops; it is not published by Pmdice, and it states no figure or status for the operator, whose own FAQ and terms remain 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.
