FanDuel Casino Evidence Dossier: Host, Licence and Bonus Dispute File

The bonus terms version that decides a dispute

Almost every disputed promotion at FanDuel Casino turns on a single artifact: the wording of the offer conditions in force at the second the opt-in was recorded. The accepted file for casino.fanduel.com holds no dated copy of any promotional document, no version marker and no wagering figure, so nothing in the current record can decide what one specific offer demanded. Treat that absence as the starting point of a dispute file rather than a footnote. Promotional conditions in United States casino products are state-scoped and can be edited between sessions, so a capture taken after a balance disappears carries far less weight than one taken at opt-in. Before entering any offer, save the full conditions view with the address bar visible, the device clock in frame where possible, and the passages covering wagering multiple, eligible games and their weighting, maximum stake while a bonus balance is live, the expiry window, and any state-specific carve-out. Save the confirmation message separately, because it often carries a timestamp the conditions view does not.

Host and entity match: casino.fanduel.com

A safety read is worthless until three strings line up: the address in the browser, the brand shown on the account, and the licensed company standing behind both. In the accepted record the address is casino.fanduel.com, the operating company is Betfair Interactive US LLC d/b/a FanDuel under Valley Forge Casino Resort, and the authorization covers slots and table games in Pennsylvania with play commencing January 24, 2020. The land-based partner is part of the identity rather than decoration, because Pennsylvania interactive authorizations attach to a licensed facility. Confirm the company name in the footer, the terms of use and the cashier's transaction descriptor instead of the homepage banner, since a brand name can be printed on pages the licensed company does not control. Where the footer company, the app publisher and the register entry disagree, stop at the mismatch and treat the account as unresolved until one of the three is corrected.

What the Pennsylvania register actually shows

The primary support in the file is the Pennsylvania Gaming Control Board listing of interactive gaming operators, read on August 21, 2026, where 24 named brands are presented as currently regulated interactive operators for the state: gamingcontrolboard.pa.gov/interactive-gaming-operators. A register entry is a strong but narrow fact. It shows that a named brand appears in a state's current presentation of authorized interactive gaming, and it does nothing more. It does not bless a promotion, guarantee a payout window, reopen a closed account, or supply an end date; no expiry sits in the file, so standing has to be re-read from the register rather than assumed to run for a fixed term. Read the register yourself instead of trusting a badge reproduced elsewhere, compare both the brand string and the operating company, and note the date of your own reading beside the result.

Legal or not: reading each state register

Pennsylvania standing says nothing about Michigan, New Jersey or anywhere else. Two state frameworks in the file show how to read an absence. Michigan separates its authorized provider list from operators that have received cease-and-desist letters, so the same agency can describe two brands in two very different ways: michigan.gov/mgcb/resources/legal-vs-illegal-gaming. New Jersey is blunter, stating that sites absent from its approved list are not approved to offer internet gaming in the state: njoag.gov internet gaming sites. Applied to casino.fanduel.com the working rule is simple: an account is authorized only in the state whose register currently shows it, and a geolocation prompt inside an app is not a substitute for that register. If a state list does not show the brand, treat wagering from that state as unauthorized rather than as a technicality, because an unauthorized wager is the weakest possible position from which to argue about a withheld balance. The routine we follow is set out in state licence checks.

Scam or legit on the current evidence

The green reading in our file applies to FanDuel Casino at casino.fanduel.com as read on August 21, 2026, and to nothing wider. It rests on a current primary register entry plus a matched company and facility string. No official adverse record sits in the file, and no corroborated documented adverse evidence sits in it either, which is why nothing here supports a scam finding. The counterweight is equally plain: a green reading is a dated snapshot of licensing status, not a promise about a specific bonus decision, a hold on a cashout, or the quality of a support reply. The dated search surface for user-review profiles held in the file is contextual only. Volume of unhappy posts is a reason to look harder at documentation, never a substitute for a competent record, and an individual post cannot establish that a term was misapplied.

See the regulated play route

Building the bonus dispute chronology

A bonus argument is won or lost on sequence. Support staff work from account logs; a player who cannot show the same order of events is left describing a feeling. Build the chronology as a flat log, one row per event, with the clock reading and the screen capture filename beside it. The rows that matter most are the opt-in, the qualifying deposit, the first wager after the bonus balance became active, any stake that could be read as exceeding a maximum-bet condition, the moment a balance changed without an obvious cause, and the first message sent to support. Note the state you were physically in for each session, because a state-scoped condition can change the answer. Keep captures unedited and store them with their original timestamps rather than pasting them into a document that rewrites the metadata.

Deposit records worth keeping

The accepted record contains no cashier inventory for the operator, so nothing here can state which deposit or payout methods are available, what minimums apply, or whether a method is restricted by state. Read the method list while logged in and capture it with the address bar visible; that capture becomes your dated fact. Beyond the list, keep the descriptor that appears on the card or bank statement, because a descriptor that does not resemble the licensed company is worth a question before it becomes a chargeback. Record declined attempts as carefully as successful ones, since a decline followed by a retry is the most common way a qualifying deposit misses an offer window. Where a bank imposes its own block on gambling transactions, note that the block sits with the bank rather than the operator. Our approach to documenting payment flows is described in payment checks.

Withdrawal holds and identity verification

No dated withdrawal test exists in the file for this operator, and no verification turnaround data does either, so any number quoted for payout speed would be invented. What survives a dispute is your own timing record. Log the request time, the amount, the method chosen, every status change with its clock reading, and the exact wording of any request for documents. Identity verification is a legal obligation in regulated United States markets, and a hold that arrives with a specific, itemized document request behaves differently from silence; both should be logged, only one is a red flag. Send documents through the in-product upload rather than ordinary email, redact everything not required, and screenshot the upload confirmation. If a payout is reversed back into a playable balance, capture the balance before and after, because a reversal that gets wagered away removes the disputed amount from the argument entirely.

Complaint route and escalation order

Order matters more than tone. Start with the operator's support channel and get a ticket reference in writing; a reference number turns a conversation into a record. If the reply does not address the specific condition at issue, restate the sequence in one message, attach the chronology, and ask for a written final position. Only after that does a regulator escalation make sense, and it goes to the agency for the state where the account is registered, which for a Pennsylvania account is the Gaming Control Board. Keep the language of an allegation until a dated competent record says otherwise: a disputed bonus is a dispute, not a proven withheld payment, and overstating it weakens an otherwise strong file. Patterns we already hold are indexed under complaints and scam warnings, and corrections to our own record go through contact and corrections.

Look-alike addresses, apps and email links

The only address in the accepted record is casino.fanduel.com, and clone risk in this market usually attacks the address rather than the interface. Type the address yourself, then read it right to left: the registrable domain and its suffix decide who you are talking to, not the words in front of them, and a convincing prefix or a hyphenated variant is the cheapest trick available. Treat search advertisements and promotional emails as untrusted routes into a cashier, especially when they arrive after a payout request. On mobile, check the publisher name on the app listing against the licensed company in the file, and be wary of a build offered outside the official store. A page that asks for card details without the licensed company appearing anywhere in the footer or terms of use is not a page to complete. Comparable address-and-company checks are recorded across our review index, including the DraftKings Casino dossier.

Open questions, method and corrections

What is missing is stated rather than smoothed over: no authorization end date, no dated promotional conditions or version marker, no cashier method inventory, no dated payout test, no verification turnaround figure, and no complaint record from a competent source. Those gaps return to research and are never estimated. The method behind the reading is narrow by design: state registers first, each read on a named date and captured; company and facility strings matched against the address; operator statements labelled as statements; user posts treated as context that directs attention rather than settles it. A green reading decays, so it is re-read on schedule and downgraded the moment a register no longer supports the exact address. The full routine sits in methodology and editorial policy. If you hold a dated document that contradicts anything recorded above, send it and the record changes. Support with a gambling problem is signposted at responsible gambling and urgent help.

Frequently asked questions

National Council on Problem Gambling