The question a player brings to an FAQ
A player opens LEP's FAQ page with a specific problem already in hand: a deposit that has not appeared, a withdrawal that is still pending, a document the site is asking for, or a game that will not load. The FAQ is the first place they look because it promises an answer without waiting for a support reply. What matters is not whether the FAQ is well written, but which of those questions it can settle on its own and which ones it simply cannot, because the answer depends on the player's own account or on terms that change.
An operator FAQ is a collection of short answers to recurring questions. It is written once and read many times. That is its strength and its limit. Anything that is the same for every player can be answered there: what documents are accepted, which deposit methods appear in the cashier, how to find a game's rules, what to do when a page does not load. Anything that differs from one account to the next cannot be answered there, because the FAQ has no access to the reader's balance, verification state, or pending transactions. The reader who expects the FAQ to tell them why their own withdrawal is delayed has asked the wrong page the right question.
What an FAQ can answer bindingly
The binding part of an FAQ is the part that describes a route or a list. A route is a sequence of screens: where the cashier is, how to open the verification section, where the responsible gaming tools sit, how to reach transaction history. A list is a set of items that do not depend on the reader: accepted document types, available deposit methods, supported browsers, the steps for closing an account. These answers are binding because they are the same for every player who reads them, and because the reader can check them immediately against the screens the FAQ names.
For example, if the FAQ says a passport or a national ID card is accepted for verification, that is a list item. The reader can gather the document and submit it. If the FAQ says withdrawals are processed through the cashier's withdrawal tab, that is a route. The reader can follow it and see their own options. Neither answer depends on who is reading. That is the test: a question whose answer would be identical for any account is one the FAQ can answer.
Process questions are the same. How to reset a password, how to set a deposit limit, how to find a game's paytable, how to contact support: these are fixed procedures. The FAQ can state them, and the reader can follow them. The answer is binding in the sense that the procedure will not vary from one account to the next, even though the outcome of following it will.
Where the FAQ stops: account-specific and time-sensitive answers
The FAQ cannot answer a question whose answer is a fact about the reader's own account. Why is my withdrawal pending? Why was my deposit declined? Why is my account restricted? Why do I not see a bonus I expected? None of these has a single answer that is true for every reader. The withdrawal may be pending because verification is incomplete, because the amount is above a review threshold, because the method has a processing window, or because the operator's payment team has not yet released it. The FAQ cannot know which applies to the reader who is asking.
The same is true of anything that depends on current terms. Bonus percentages, wagering requirements, minimum deposits, withdrawal limits, processing times: these are figures that operators change. A number printed in an FAQ is a snapshot, not a promise. The reader who reads a wagering multiple in an FAQ and relies on it later may find the promotion page now states a different one. The promotion page is the binding source, because it is the document that governs that offer, and it is updated when the offer changes. The FAQ is a convenience, not a contract.
This is not a defect of LEP's FAQ. It is the nature of the page type. An FAQ is a secondary document. It summarises what the primary documents say. When a primary document changes, the FAQ may lag behind it, and the reader has no way to know whether the FAQ they are reading is current. The primary document is always current, because it is the thing that was changed. That is why the reader who needs a figure should read it off the primary page, not off the FAQ.
The items a reader should confirm on the operator's own pages
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit methods available | Payment routes are added and removed as provider agreements change | The cashier's deposit screen, not the FAQ |
| Withdrawal processing time | Processing windows are adjusted operationally and by method | The withdrawal policy page or the cashier's withdrawal tab |
| Wagering requirement on a bonus | Each promotion carries its own multiple, and promotions are revised | The specific promotion's terms, linked from the offer itself |
| Documents accepted for verification | The accepted list is generally stable but can be amended | The verification or KYC page, and the upload screen itself |
| Deposit and withdrawal limits | Limits are set per method, per account tier, and can be changed | The payment or banking page, or the cashier for the reader's own limits |
| Self-exclusion and cooling-off options | The tools and their durations are defined in the responsible gaming policy | The responsible gaming page and the account's own settings |
| Bonus eligibility rules | Eligibility depends on account state, geography, and the offer's own terms | The promotion's terms and conditions |
The table's third column is the point. The FAQ may mention all of these items, but the FAQ is not where the reader confirms them. The reader confirms a deposit method by opening the cashier and seeing it listed. They confirm a processing time by reading the withdrawal policy. They confirm a wagering requirement by opening the promotion's own terms. The FAQ's value is that it tells the reader where to look; its limit is that it is not the place where the looking ends.
What it means when the FAQ does not state an item
Absence on an FAQ page is information. If the FAQ does not name the accepted document types, the reader cannot assume a particular document will pass verification. If it does not state a withdrawal processing window, the reader cannot assume a timeframe. If it does not list deposit methods, the reader cannot assume a method is available. The absence is not a statement that the item does not exist; it is a statement that the FAQ is not the place where the item is defined.
This cuts both ways. An FAQ that is silent on a subject is not hiding anything. It is simply not the governing document. The governing document is the one that was written to define that item: the terms and conditions for account rules, the privacy policy for data handling, the payment page for methods and limits, the promotion page for bonus terms. The reader who treats the FAQ as the final word on any of those has read a summary and mistaken it for the source.
Where the FAQ is silent, the reader's next step is the same in every case: open the primary page and read the item there. If the primary page is also silent, then the item is genuinely undefined for the reader, and the only channel that can settle it is the operator's support team, because only they can see the reader's account and apply the current rules to it.
How to use the FAQ without being misled by it
The correct use of an FAQ is as an index, not as an authority. The reader should read it to learn which page governs the question they have, then open that page and read the answer there. For a question about a bonus, the FAQ may say that wagering requirements apply; the promotion's terms state the multiple. For a question about verification, the FAQ may say documents are required; the verification page states which ones. For a question about withdrawals, the FAQ may say processing takes time; the withdrawal policy states the window.
The reader should also note the date on any FAQ answer, if one is shown. An FAQ answer that is months old may describe a process that has since changed. The primary page it points to will reflect the change. Where no date is shown, the reader has no way to know how old the answer is, which is one more reason to treat the FAQ as a pointer rather than a source.
Finally, the reader should distinguish between a question the FAQ answers and a question the FAQ cannot answer. A question about how to do something is answerable: how to deposit, how to verify, how to set a limit. A question about why something happened to the reader's own account is not: why a deposit failed, why a withdrawal is pending, why a bonus is missing. The first kind of question has a fixed answer. The second kind has an answer that only the reader's account can supply, and the FAQ has no access to it. The reader who understands that distinction will not waste time searching an FAQ for an answer that cannot be there.
LEP FAQ
This article is an independent summary of what an operator FAQ page covers and where it stops. It is not published by LEP, and it states no figure or status for that operator. LEP's own FAQ page, and the primary pages it points to, are the only binding sources for the answers a reader needs.
FAQ
Can the LEP FAQ tell me why my withdrawal is pending?
No. A pending withdrawal is a fact about your account: it depends on your verification state, the amount, the method, and the operator's review queue. The FAQ can describe the general process, but only the withdrawal page on your account, or support, can tell you why yours is pending.
Where should I read the wagering requirement for a bonus?
On the promotion's own terms page, linked from the offer itself. The FAQ may mention that wagering applies, but the multiple is set per promotion and can change. The promotion page is the binding source.
Does the FAQ list which documents are accepted for verification?
It may list them, but the list that matters is the one on the verification or KYC page, and the upload screen itself. If the FAQ is silent, that does not mean no documents are required; it means the FAQ is not the governing page for that list.
What should I do if the FAQ's answer conflicts with a primary page?
Trust the primary page. The FAQ is a summary and may lag behind a change. If the conflict affects your money or your account, read the primary page carefully, and if the conflict remains, ask support to confirm which version applies.
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.
