A disputed deposit is one of the few gambling complaints where the paperwork usually decides the outcome before anyone weighs the merits. The popular assumption is that a chargeback is a straightforward consumer right: you say the payment was not yours, the bank reverses it, the casino absorbs the loss. That assumption collapses the moment a player claims the deposit was made by a child. In one case I reviewed, the casino pulled its identity verification logs and IP addresses, showed the account holder had made the payment personally, and the chargeback was rejected. The account was then closed. Here is what that case reveals about how these disputes are actually settled.
The child deposit defence and why it fails on the evidence trail
The child defence sounds unanswerable. If a minor used a parent’s card, the deposit was not authorised by the account holder, so the transaction should be reversed. That is the theory. In practice, a casino with a UK Gambling Commission licence has to keep records that make this claim testable rather than taken on trust. When the dispute landed, the operator compared the time-stamped identity verification record against the deposit timestamp and the login session that preceded it. The verification had been completed by the account holder, from the same device and the same IP address, minutes before the deposit was made.
The IP trail went further. The deposit, the session that triggered it, and the earlier verification all resolved to one address tied to the account holder’s usual location. There was no second device, no separate login, and no gap in the session that would suggest someone else had picked up the phone or laptop. A child making a deposit would normally leave a different fingerprint: a new device, a different IP, a session that began without the account holder’s credentials. None of that appeared. The bank’s chargeback was refused because the evidence pointed at the account holder, not a minor.
What the operator actually checks before accepting a deposit
This is where the myth about anonymous play does real damage. A licensed operator like Lady Luckmore, which is operated by Grace Media (Gibraltar) Limited and holds UK Gambling Commission licence 057869-R-334655-008, has to verify identity before a player can withdraw, and increasingly before play. That verification leaves a dated record. The IP address attached to each session is logged too. When a chargeback arrives, those two datasets are the first thing pulled, because they answer the only question that matters: who was actually at the keyboard.
The 25 percent max bet rule applies to bonus play, and that is a separate trap, but the point here is narrower. The player in this case had not been hacked and had not been defrauded by a stranger. They had made the deposit and then tried to reverse it through the bank by blaming a child. The logs made that story impossible to sustain. The chargeback failed, and the operator closed the account for what it treated as attempted fraud.
Skeptics should note the flip side. The same logs that defeat a false child claim also protect a genuine victim. If a card really had been used by a minor, the IP and device records would show a session the account holder never started. The evidence cuts both ways, which is why operators keep it, as set out at https://ladyluckmore-casino.uk/promotions/, rather than relying on a player’s word.
Why chargebacks are the wrong tool for most gambling disputes
The chargeback mechanism was built for unauthorised card use and faulty goods, not for buyer’s remorse about a losing session. A player who deposits, loses, and then disputes the payment as “not authorised” is making a factual claim that the bank will test against the operator’s records. If those records show the player made the deposit, the claim fails and the bank may flag the account. The case above is the textbook version: the child story was checkable, and it did not check out.
Where chargebacks do get complicated is bonus disputes. A player might deposit to claim weekly rewards spins, then find the wagering requirements harder to clear than expected. Weekly Rewards awards 10 free spins for a £25 deposit and wager, or 20 free spins for a £50 deposit and wager, with the spins credited by 17:00 every Monday. A promo code such as MEGA grants 10 spins for a £10 slots wager. None of that is grounds for a chargeback. It is a bonus terms disagreement, and the route is the operator’s complaints procedure, then an alternative dispute resolution provider, not the card issuer.
The same applies to promotional mechanics. Sweetest Slots offers prize drops on selected slots, and seasonal codes like BOOST50 or SANTA come with their own conditions. A player who misreads a prize drop or a reload bonus and loses their stake cannot retrospectively call the deposit unauthorised. The bank will ask for the operator’s evidence, and the operator will supply session logs, bonus acceptance records, and the terms the player agreed to at deposit. The chargeback dies there.
There is a further wrinkle that catches people out: the welcome package. Lady Luckmore hides the welcome package until registration, which means a player cannot see the full terms before signing up. That is a legitimate criticism, and it is the kind of thing a regulator might look at. It is still not a chargeback issue. A hidden bonus term is a transparency complaint, not proof that a payment was unauthorised. Conflating the two is how players end up with a failed dispute and a closed account.
Withdrawals add another layer. A withdrawal cap and identity verification requirements mean that even a winning player has to clear checks before funds move. If a player disputes a deposit while a withdrawal is pending, the operator will usually freeze the account and review both. Payment methods like PayPal and Google Pay leave their own audit trails, which makes a false unauthorised claim even easier to disprove.
For anyone tempted to dispute a deposit they actually made, the practical steps are simple. Read the bonus terms before you deposit, not after. If you have a genuine dispute about a promotion, use the operator’s complaints process and keep your session records. If gambling has become a problem, use GamStop, GamCare, BeGambleAware, or Gamblers Anonymous rather than reaching for the chargeback button. And if a child genuinely has access to your payment details, fix that directly: remove saved cards, enable device controls, and tell the operator. The IP logs will show what happened either way, so the only sensible strategy is to make sure the truth is on your side before the bank starts asking.