The situation a reader brings to an FAQ
A player opens an operator's FAQ with a specific interruption in front of them: a deposit that has not appeared, a withdrawal that is stuck at a status screen, a bonus that will not activate, or a verification request that arrived without explanation. The FAQ is the first place the operator offers an answer, and the reader wants that answer to be final. It rarely is. What an FAQ can do is tell the reader which process applies, which documents the operator will ask for, and which route a request takes. What it cannot do is tell the reader what will happen to their particular deposit, withdrawal, or account, because that depends on facts the FAQ does not hold. BombsGG publishes its FAQ as the entry point to those processes, and the page is useful exactly to the extent that the reader treats it as a map rather than a verdict.
Which questions an FAQ can answer bindingly
An operator FAQ can state the mechanics of a process without needing any information about the reader. Those are the questions it answers well. The list of documents accepted for identity verification is one: a passport, a driving licence, or a utility bill are named because the list is the same for every account. The sequence of a withdrawal is another: the request is created, it enters a queue, it is reviewed, and it is released. The FAQ can say that sequence exists and in what order the steps run. It can also state which features are available at all: whether a self-exclusion tool exists, whether deposit limits can be set, whether a particular game category is offered. None of those statements depends on the reader's balance, history, or location, so the FAQ can make them without qualification.
What the FAQ cannot do is apply those mechanics to the reader's case. It cannot say why a specific deposit is missing, because the answer sits in the payment provider's records and the operator's transaction log. It cannot say when a specific withdrawal will clear, because that depends on the method, the amount, the verification state of the account, and the queue at the moment of the request. It cannot say whether a bonus will be credited, because eligibility is decided by the promotion terms and the reader's history against those terms. The reader who asks the FAQ for those answers will get a process description and a pointer to the team that holds the actual file. That is not evasion; it is the correct division of labour.
The table of what to confirm on an FAQ page
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Operators revise the list when regulations or fraud patterns change; a document accepted last year may not be accepted today | The verification or KYC section of the FAQ, and the document request itself when the account is flagged |
| Withdrawal processing sequence | The number of review steps and the queue order can change with volume, risk rules, or method | The withdrawal section of the FAQ; the status screen on the reader's own withdrawal shows the current step |
| Deposit methods and minimums | Payment routes are added and removed, and minimums are adjusted, without notice to existing players | The cashier or payments page on the operator's site, not the FAQ, is the live list |
| Bonus eligibility conditions | Promotion terms are rewritten between campaigns; what applied to one bonus does not carry to the next | The promotions terms page for the specific bonus, not the FAQ's general explanation |
| Self-exclusion and limit tools | The tools themselves are stable, but their scope and the request procedure can be amended | The responsible gaming section of the FAQ and the account settings page |
| Game rules and payout structures | Rules vary by table and title; a general FAQ answer cannot cover every variant | The rules panel inside the specific game, which is the binding source for that title |
Where the binding answer lives
For any question that touches money, the binding source is never the FAQ. It is the record that the operator generates at the moment of the transaction. A deposit's binding facts are the amount, the method, the reference number, and the time of receipt, all of which appear on the payment provider's confirmation and in the operator's transaction history. A withdrawal's binding facts are the request time, the method chosen, the verification state of the account, and the status that the cashier displays. A bonus's binding facts are the terms that were in force when the reader opted in, not the terms displayed today. The FAQ can tell the reader where each of those records lives and what each field means. It cannot substitute for the record itself.
For questions about rules, the binding source is the rules text inside the game. A slot's paytable, a table game's rule panel, and a live dealer game's help screen all state the mechanics that govern that specific title. The FAQ may summarise the general structure of a game category, but a summary is not a rule. Where the two conflict, the in-game text wins, because it is the version the game engine executes. The reader who wants certainty about a rule should read the in-game text, not the FAQ.
What it means when the FAQ does not state an item
An FAQ that does not name the accepted verification documents leaves the reader unable to prepare for a request. That absence is itself information: the reader will learn the list only when the operator asks, and the request may arrive with a deadline. An FAQ that does not state the withdrawal sequence means the reader cannot distinguish a normal queue from a problem; the status screen becomes the only guide, and a status that does not change for an unusually long time is the signal to contact support. An FAQ that does not list deposit methods means the cashier is the only live source, and a method shown there may still fail for a specific reader because of geography or provider rules. None of these absences is a defect in the FAQ; each one tells the reader which other page carries the answer.
The most consequential absence is the one around bonus terms. An FAQ that explains bonuses in general but does not link to the promotion terms for each campaign leaves the reader with a description and no numbers. The wagering multiple, the game weighting, the maximum bet during wagering, and the expiry window are all on the terms page, and they are all subject to change between campaigns. A reader who relies on the FAQ's general explanation and then fails a wagering condition has not been misled by the FAQ; they have read the wrong page. The correct sequence is to read the FAQ for the shape of the process, then read the terms page for the numbers that bind the current offer.
The support channel is a continuation of the FAQ, not a replacement
When the FAQ does not answer a question, the reader's next step is the operator's support channel. That channel has access to the account file, and it is the only place where an account-specific answer can be given. The FAQ can tell the reader which channel exists and what information to have ready: the account identifier, the transaction reference, the date and amount, and the exact error message if one appeared. A support answer is still not a binding document, but it is the operator's reading of the reader's file, and it is the fastest way to resolve a discrepancy between what the FAQ describes and what the account shows.
The reader should treat a support answer as a statement of the operator's position at that moment. If the answer conflicts with the written terms, the written terms govern, and the reader should ask support to point to the clause. If the answer conflicts with the transaction record, the reader should ask for the transaction reference and the status on the operator's side. The FAQ is the map; support is the person who can look at the reader's file; the written terms and the transaction records are the documents that bind. Keeping those three roles separate is the whole skill of reading an FAQ.
FAQ
Can the BombsGG FAQ tell me why my withdrawal is delayed?
No. The FAQ can describe the withdrawal sequence and the typical review steps, but the reason a specific withdrawal is delayed sits in the account file: the method chosen, the verification state, and the queue at the time of the request. The status screen on the withdrawal itself and the support channel are the places that carry that information.
Does the FAQ list the documents I need for verification?
It may list the accepted document types, because that list is the same for every account. Whether your specific document will be accepted depends on its validity, the name matching the account, and the operator's current rules. The request you receive will state exactly what is needed.
Where do I find the wagering requirement for a bonus?
In the promotion terms for that specific bonus, not in the FAQ. The FAQ can explain what a wagering requirement is and how it works in general, but the multiple, the game weighting, and the expiry are stated on the terms page that was in force when you opted in.
If the FAQ and the game rules disagree, which one applies?
The game rules inside the specific title apply, because that is the text the game engine executes. The FAQ is a summary and may be outdated or simplified. For any rule that affects a bet or a payout, read the in-game rules panel.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by BombsGG, and it states no figures or statuses for that operator, whose own FAQ and terms pages 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.
