The situation a reader is in when they open an FAQ
A player lands on Mega Medusa's FAQ page because something has already gone slightly wrong, or because they are trying to stop it going wrong. A deposit has not appeared. A withdrawal is sitting in a pending state. A document was rejected. The reader is not browsing; they are looking for the one sentence that tells them what happens next. That is exactly what an operator FAQ is built for, and it is also the thing that limits it. An FAQ answers questions about processes, routes and document lists. It does not answer questions about this reader's account, because no static page can know which rule applies to a specific balance, a specific payment method, or a specific verification file.
So the useful move is not to read the FAQ hoping for a personalised answer. It is to read it as a map of where each kind of answer lives. Some answers are on the FAQ itself and are binding because they describe a fixed process. Others are only binding when they appear in the terms, the cashier, or the account screen, because they depend on data the FAQ cannot hold. The rest of this page explains that split, item by item.
What an operator FAQ can answer bindingly
An FAQ is strongest when the answer does not change from one account to another. That covers three broad areas. The first is process sequence: what happens after a withdrawal request is submitted, in what order, and which states it passes through. The second is route availability: which deposit methods the cashier generally lists, which withdrawal methods exist as categories, and what happens when a deposit method has no matching withdrawal route. The third is document requirements: what kinds of files verification typically asks for, and what makes a file acceptable or rejectable.
These are binding because they are properties of the operator's system, not of the reader. A process sequence is the same for every account that triggers it. A route list is the same for every player in a given region or currency. A document checklist is the same for every verification attempt. When Mega Medusa's FAQ states one of these, the reader can rely on it in the same way they rely on a printed timetable: it describes the machine, not the passenger.
That does not mean the FAQ is a contract. The terms page remains the legal source, and the cashier remains the operational source. But for the narrow question of what happens next, a process answer on an FAQ is usually accurate and complete.
What an operator FAQ cannot answer
The moment a question depends on the reader's account, the FAQ stops being a source of truth. It cannot say why this deposit is delayed, because the reason sits in the payment provider's logs, the fraud queue, or the reader's own bank. It cannot say whether this withdrawal will clear today, because the remaining verification steps are account-specific. It cannot say whether this bonus is active, because wagering progress is stored against the player ID, not on a public page.
There is a second category the FAQ cannot settle: anything that changes with the current terms. A wagering multiple printed in an FAQ is a snapshot. If the promotions page is updated tomorrow, the FAQ may lag behind it. The same applies to minimum deposits, maximum withdrawal amounts, and fee schedules. The FAQ may repeat them for convenience, but the binding version is always the one on the page that governs that item. A reader who finds a figure in the FAQ and a different figure in the terms should treat the terms as the live one, and should not assume the FAQ was ever intended to override it.
Finally, an FAQ cannot diagnose. It can list the common reasons a document is rejected, but it cannot say which reason applies to this reader's file. It can list the common reasons a withdrawal is held, but it cannot say which hold is active. Diagnosis requires the account screen, the support ticket, or the email the operator sent. The FAQ's job is to tell the reader where to look, not to look for them.
The three questions every FAQ reader should ask
Before trusting any FAQ answer, a reader can filter it through three tests. The first test is the account test: does the answer change if the reader's balance, method or verification status changes? If yes, the FAQ answer is a generalisation, not a ruling. The second test is the terms test: is there another page on the site that governs the same item, and does the FAQ match it? If they differ, the governing page wins. The third test is the timestamp test: does the answer concern a figure that promotions or payment teams change regularly? If yes, the reader should confirm it on the live page before acting on it.
These tests do not make the FAQ useless. They make it usable. A process answer passes all three tests. A figure answer fails at least one. A route answer passes the account test but may fail the timestamp test if the operator adds or removes methods. The reader's job is to know which kind of answer they are looking at.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Withdrawal processing sequence | Fixed by system design; rarely changes | FAQ or withdrawal policy page |
| Available deposit methods | Payment providers change; regional availability varies | Cashier, not the FAQ |
| Verification document list | Can change with compliance requirements | Verification page or account prompts |
| Wagering multiple on a bonus | Promotions team updates it per offer | Promotions terms, not the FAQ |
| Minimum deposit amount | Changes with payment method and currency | Cashier or deposit page |
| Withdrawal hold reasons | Account-specific; cannot be listed exhaustively | Account screen or support ticket |
| Fee schedule | Changes with method and operator policy | Payment terms page |
Where the binding answer lives instead
For every question the FAQ cannot settle, there is a page that can. The pattern is consistent across operators. Deposit questions are settled by the cashier, because the cashier shows the methods available to this account in this region, with the current minimums and fees. Withdrawal questions are settled by the withdrawal policy and the account's pending transaction screen, because those show the current state and the remaining steps. Bonus questions are settled by the promotions terms for that specific offer, because the wagering multiple, game weighting and expiry are defined per offer, not per site. Verification questions are settled by the document request the operator sends, because that request names the exact files and formats required for this account at this time.
Mega Medusa's FAQ is best understood as an index to these pages. It tells the reader that a withdrawal has a processing queue, but the queue position is on the account screen. It tells the reader that verification asks for identity and address documents, but the exact list is in the request. It tells the reader that bonuses carry wagering requirements, but the multiple is in the offer terms. A reader who treats the FAQ as the final answer will sometimes be right, and will sometimes act on a figure that was already stale. A reader who treats it as a map will always know where to look next.
What it means when the FAQ does not state an item
Absence on an FAQ is itself information. If the FAQ does not state a withdrawal timeframe, the reader cannot assume one exists as a promise. The operator may clear withdrawals quickly or slowly, but the FAQ not naming a window means the reader should look to the withdrawal policy, and if that page also names no window, then no binding window exists. The reader's expectation should be built on what is stated, not on what is common elsewhere.
The same applies to fees. If the FAQ is silent on withdrawal fees, the reader should check the payment terms and the cashier before requesting a withdrawal. If those pages are also silent, the reader should ask support before committing funds, because a fee discovered after the fact is harder to dispute than one confirmed in advance. Absence is not a guarantee that no fee exists; it is a guarantee that the FAQ does not answer the question.
For verification, absence is more serious. If the FAQ does not list the documents required, the reader should not guess. A guessed document that is rejected can delay a withdrawal by days. The correct move is to wait for the operator's request, or to ask support for the list before uploading anything. An FAQ that is silent on verification is not broken; it is simply pointing the reader to the account-specific channel where the real list lives.
Reading the FAQ without mistaking it for the terms
The most common misreading is to treat an FAQ answer as a promise. A sentence like "withdrawals are processed within a certain window" is a description of a typical process, not a contractual commitment, unless the terms page repeats it with the same wording. A sentence like "we accept the following methods" is a list of what the cashier generally shows, not a guarantee that every method is available to every reader. The FAQ is written for speed and clarity, and speed and clarity sometimes flatten the details that matter.
The reader's protection is the hierarchy of pages. Terms and conditions sit at the top for anything contractual. The cashier and account screens sit at the top for anything operational. The FAQ sits below both, useful for orientation and dangerous as a substitute. A reader who keeps that hierarchy in mind can use the FAQ exactly as intended: as the fastest way to find out which page answers the question.
FAQ
Can I rely on the Mega Medusa FAQ for withdrawal times?
Only for the process sequence, not for a specific timeframe. The FAQ may describe the states a withdrawal passes through, but the time each state takes depends on the account, the method and the verification status. The live answer is on the withdrawal policy page and the pending transaction screen.
Why does the FAQ not tell me why my deposit failed?
Because the reason is account-specific and sits in the payment provider's response, the operator's fraud checks, or the reader's bank. The FAQ can list common causes, but the actual cause for this deposit is only visible in the account history or a support ticket.
If the FAQ lists a bonus wagering multiple, is that binding?
Not unless it matches the promotions terms for the specific offer. Wagering multiples are set per offer and can change when a new promotion replaces an old one. The binding figure is always on the offer's own terms page, not in a general FAQ.
What should I do if the FAQ does not mention a document I was asked for?
Follow the operator's request, not the FAQ. The request is generated for the reader's account and reflects current compliance requirements. The FAQ may be a general list that lags behind the live requirement, and uploading the wrong document delays the process.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Mega Medusa, and it states no figure or status for them, so the operator's own FAQ and governing pages 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.
