A reader opens the Radiocaz FAQ because a transaction has stalled, a document has been requested, or a game rule is unclear. The page feels like the fastest route to an answer, and for process questions it often is. The mistake is to treat every answer on it as final. An FAQ is a general-purpose document: it describes the normal route, not the reader's route. Anything that depends on the reader's own account, the current terms, or a live decision by the operator is answered elsewhere, and the FAQ's real value is in telling the reader where that elsewhere is.
The split between what an FAQ decides and what it only describes
Every operator FAQ is built on a division that most readers never see stated. On one side are questions whose answer is the same for everyone: which documents are accepted for verification, what the deposit methods are, how a game round is settled, what the self-exclusion steps are. On the other side are questions whose answer changes by account: why this withdrawal is pending, whether this document is sufficient, what bonus applies to this deposit, why this account is restricted.
The first group is what an FAQ can answer bindingly, because the answer is a rule or a route, not a judgment. The second group is what it cannot answer, because the answer depends on a file the FAQ does not see. A reader who asks the FAQ an account question gets a general description at best. The binding answer comes from the account itself, the cashier, or a support agent who can open the file.
That split is the single most useful thing to understand about the Radiocaz FAQ before reading any individual answer. It tells the reader which answers can be relied on and which ones are only a map to the place where the real answer is kept.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted deposit methods | Payment routes are added and removed, and availability often depends on the reader's country or account status | The cashier or deposit page, which shows only the methods currently available to that account |
| Withdrawal processing time | Any stated window is a target, not a promise; verification, method, and amount all move the actual time | The withdrawal policy page and the cashier's status display for the specific withdrawal |
| Verification documents required | The list is standard, but whether a particular document is sufficient for a particular account is a case decision | The verification or KYC page states the list; the account's document request states what is needed |
| Bonus wagering requirements | Terms change over time, and different promotions carry different multiples | The specific promotion's terms, not the FAQ, which usually only explains what a wagering requirement is |
| Game rules and payout mechanics | Rules vary by game variant and table, and an FAQ can only describe the general principle | The game's own rules panel or help file, which is the binding ruleset for that game |
| Self-exclusion and limits | The tools themselves are stable, but the exact effect on an account depends on which tool is used and when | The responsible gambling page and the account's own settings |
Process questions: where the FAQ is genuinely binding
For a certain class of question, the FAQ is the right document and its answer is the final one. These are questions about the route, not the outcome. What steps does a withdrawal go through? Which documents are on the standard verification list? How does a player open the responsible gambling tools? What does a wagering requirement mean in mechanical terms?
These answers are binding because they describe a procedure that does not change from one account to the next. The FAQ can say that withdrawals pass through a verification step before release, and that is true for every withdrawal. It can say that a government-issued photo ID is on the standard document list, and that is true for every account that reaches that stage. The reader can act on these answers without a support ticket.
The reader should still check the date. An FAQ is a living document, and process answers are revised when the operator changes a route or a document list. What the FAQ said last month about a deposit method may not be what it says this month. The cashier is always more current than the FAQ, because the cashier is generated from the live system rather than edited by hand.
Account questions: where the FAQ stops and the file begins
The moment a question contains the word "my" or "this" — my withdrawal, this deposit, my bonus, this restriction — the FAQ stops being the binding document. The answer to an account question is not a rule; it is a state. The state lives in the account file, and the FAQ cannot see the file.
This is why readers so often find an FAQ answer that seems to fit their situation but does not resolve it. The FAQ says withdrawals are processed in a certain order, but the reader's withdrawal is still pending. The FAQ lists accepted documents, but the document the reader uploaded was rejected. The FAQ explains wagering requirements, but the reader's bonus still shows as locked. In each case the FAQ has described the general route, and the reader's file has taken a branch the FAQ does not describe.
The binding answer for an account question comes from one of three places: the account's own status display, the specific message attached to the transaction or bonus, or a support agent who can open the file. The FAQ's job at that point is to tell the reader which of those three places to look, and what information to have ready when they do.
What the FAQ cannot do, and what that means for the reader
There are questions an FAQ cannot answer at all, and the reader should recognize them before wasting time on the page. The FAQ cannot tell a reader why their specific account was restricted, because that is a compliance or risk decision attached to the file. It cannot tell a reader whether their specific document will pass, because that is a verification judgment made by a person or a system looking at the actual file. It cannot tell a reader what bonus they will receive, because bonus eligibility is calculated against the account at the moment of deposit.
When the FAQ does not state one of these things, that absence is itself the answer. It means the question is not a process question. The reader should stop reading the FAQ and open the channel that can see the file: the cashier, the account history, or a support ticket.
There is also a class of question the FAQ should never be asked to answer: anything that requires a promise about the future. Will this withdrawal arrive by Friday? Will this document be accepted? Will this bonus be credited? No FAQ can answer those, because no FAQ can bind the operator to a future outcome. The reader who asks the FAQ for a promise is asking the wrong document.
Where the binding answer lives for each question type
The reader who understands the split can route every question to the right place without reading a single FAQ entry. A deposit method question is answered by the cashier, because the cashier shows only what is available to that account right now. A withdrawal status question is answered by the withdrawal's own status line in the account history. A verification question is answered by the document request attached to the account. A bonus question is answered by the promotion's own terms page. A game rule question is answered by the game's rules panel.
The FAQ is the index to these places, not a replacement for them. Its best entries are the ones that say "this is stated on the cashier" or "this is shown in your account history" or "this is in the promotion terms." Those entries are not dodging the question; they are routing it correctly. The reader who follows the route gets a binding answer. The reader who demands the answer from the FAQ itself gets a description.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Radiocaz, and it states no figure or status for that operator, whose own FAQ and account pages are the only binding source.
FAQ
Can the Radiocaz FAQ tell me why my withdrawal is pending?
No. The FAQ can describe the general withdrawal process, but a pending withdrawal is an account state. The reason for the hold is attached to the specific withdrawal in the account history, and if it is not shown there, a support agent must open the file to explain it.
Does the FAQ's list of accepted documents mean my document will pass?
No. The list tells the reader which document types are normally accepted. Whether a particular upload passes is a verification judgment made against the actual file, and the FAQ cannot make that judgment in advance.
Where do I find the wagering requirement for my bonus?
On the specific promotion's terms page, not in the FAQ. The FAQ may explain what a wagering requirement is in general, but the multiple that applies to a particular bonus is stated in that bonus's own terms, and it can differ between promotions.
Why does the FAQ answer seem to fit my situation but not resolve it?
Because the FAQ describes the normal route, not the reader's route. When an account takes a branch the FAQ does not describe — a rejected document, a held withdrawal, a locked bonus — the binding answer is in the account file, and the FAQ can only point to the channel that can open it.
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.
