A player opens btc365.com's FAQ because a deposit has not appeared, a withdrawal is stuck on verification, or a bonus did not credit as expected. The FAQ is the first place they look for an answer, and the first place a wrong assumption gets made. The page is a directory of process, not a contract. It can tell a reader which documents are usually requested and which routes exist; it cannot tell them what will happen to their specific deposit on this specific day.
The FAQ answers the question of how, not whether
An operator FAQ is built to handle the questions support receives most often, and those questions are overwhelmingly about procedure. How a deposit is made. What a wagering requirement means. Which documents unlock a withdrawal. What happens when a session drops mid-game. The answers describe the normal path a request takes through the operator's systems.
What the FAQ does not do is bind the operator to a specific outcome for a specific reader. A FAQ answer about withdrawal times describes the usual sequence, not a promise that a particular withdrawal will clear in that window. A FAQ answer about bonus eligibility describes the general rule, not a decision on whether this reader's account qualifies. The reader who treats the FAQ as a guarantee has misread the page. The reader who treats it as a map of where each decision is made has read it correctly.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted deposit methods | Payment routes are added and removed as processors change; a method listed today may be gone next month | The cashier or deposit page, at the moment of deposit |
| Withdrawal processing sequence | Verification status, payment method and amount all change the path a withdrawal takes | The withdrawal page after the request is submitted; the FAQ describes the typical sequence only |
| Verification documents required | Different account tiers, deposit methods and withdrawal sizes trigger different document lists | The verification request itself, which states what is needed for this account at this time |
| Bonus eligibility and wagering | Promotions change frequently; the wagering multiple attached to one offer is not the multiple on the next | The promotions page and the specific offer terms, not the FAQ |
| Game rule disputes and round results | Each game has its own rules and each round is settled by the game server's record | The game's own rules page and the round history in the player's account |
| Account restriction or closure reasons | Decisions are made case by case and depend on the account's full history | The notification sent to the player, or support directly; the FAQ only lists general categories |
What a FAQ can settle without asking support
Some questions have answers that do not depend on the reader's account. The FAQ is genuinely useful for those. What the minimum deposit amount is, if the operator publishes one, is a fixed number at any given moment. Which currencies are accepted is a fixed list. Whether the operator offers a self-exclusion tool is a fixed yes or no. These are configuration facts, not account decisions, and a FAQ can state them without needing to know who is asking.
The reader should still check the date. A FAQ page that is not maintained can carry a minimum deposit figure that the cashier no longer enforces. The cashier is always more current than the FAQ, because the cashier is the system that processes the deposit. When a FAQ answer and a cashier screen disagree, the cashier screen is the one that will be applied to the reader's money.
What a FAQ cannot settle, and why readers ask it anyway
The most common FAQ questions are often the ones the FAQ is least able to answer bindingly. "Why is my withdrawal still pending?" depends on the reader's verification status, the payment method chosen, the amount, and sometimes on a manual review that has not finished. A FAQ can list those factors; it cannot say which one applies to this reader. "Why was my bonus not credited?" depends on the reader's deposit method, the order in which they clicked, and the specific terms of the offer. A FAQ can describe the common causes; it cannot diagnose this account.
That is not a failure of the FAQ. It is the boundary of the format. A FAQ is written once and read by thousands of people. It cannot know any of them. The moment a question contains the word "my" — my deposit, my withdrawal, my bonus, my account — the answer has moved from the FAQ to the account itself, and the reader needs the channel that can see that account: the support ticket, the live chat, or the notification attached to the specific transaction.
The binding source is always the specific page, not the FAQ
For every category of question, there is a page or screen that carries the binding answer, and the FAQ's job is to point to it. The promotions page carries the wagering multiple for the offer the reader took. The withdrawal page carries the status of the withdrawal the reader made. The verification request carries the document list the reader needs to provide. The game's rules page carries the payout table the reader played against.
A reader who uses the FAQ as the final word on any of these has read the wrong document. A reader who uses the FAQ to find out which document is the final word has used it exactly as intended. The distinction matters most when money is at stake: a bonus dispute settled by reference to the FAQ will lose to a bonus dispute settled by reference to the offer terms, every time.
Where the FAQ stops and the account begins
The cleanest way to read any operator FAQ is to divide its answers into two piles. The first pile is configuration: which methods exist, which currencies are taken, which tools are available, what the general process is. These answers are the same for every reader and the FAQ can state them. The second pile is decision: whether this deposit was accepted, whether this withdrawal was approved, whether this account passed verification, whether this bonus applies. These answers are different for every reader and the FAQ can only list the factors that go into them.
When a reader's question falls in the second pile, the FAQ has not failed them. It has shown them where the question gets answered. The next step is not to read the FAQ again, but to open the specific page, screen or ticket that carries their account's data. That is the only place the answer exists.
FAQ
Can the btc365.com FAQ tell me why my withdrawal is pending?
It can list the common reasons a withdrawal is held — verification incomplete, payment method mismatch, amount above a review threshold — but it cannot tell you which reason applies to your withdrawal. Your withdrawal's status is shown on the withdrawal page in your account, and support can see the specific hold on your request.
Is the deposit method list in the FAQ always current?
Not necessarily. Payment routes change as processors are added and removed, and a FAQ page can lag behind. The deposit page in the cashier is the current list, and the method shown there at the moment of deposit is the one that will be used.
Does the FAQ state the wagering requirement for my bonus?
It may state a general example, but the wagering multiple that applies to your bonus is the one printed in the terms of the specific offer you took. The promotions page and the offer's own terms are the binding sources; a FAQ example is not.
What should I do when the FAQ and my account screen disagree?
Trust the account screen. The FAQ is a general description written once; the account screen is generated from your data at that moment. If the two conflict, the account screen is what the operator's systems will apply, and support will resolve the discrepancy from the account data.
This page is an independent summary of what an operator FAQ page covers and where it stops. It is not published by btc365.com, and it states no figure or status for them; the operator's own FAQ and the specific pages it points to are 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.
