Online gambling payments

Friendly Fraud at Online Casinos and Sportsbooks: Why "Deposit, Lose, Dispute" Happens and How to Answer It

A player deposits, loses and tells the bank the deposit wasn't theirs. Why it happens, how it reaches you, and how to answer it with records you already keep.

By VyaPayPublished 7 min read

Friendly fraud at an online casino or sportsbook is a dispute filed by the cardholder who made the deposit, after the money has been played and lost. It arrives as a fraud claim or a service complaint, counts against you like any other dispute, and isn't moved off your books by 3-D Secure at US gambling codes. What answers it is evidence you already hold.

Friendly fraud is a card dispute in which the cardholder, or someone in the cardholder's household, made or allowed a legitimate purchase and then asks the issuer to reverse it, for example by claiming they didn't authorize it or didn't receive what they paid for. The merchant did nothing wrong, but the dispute is real and has to be answered.

Why does "deposit, lose, dispute" happen?

Because a deposit is easy to regret once it's gone, and a dispute form doesn't ask about motive. The reasons behind a friendly-fraud claim at a gambling merchant aren't hard to reconstruct, even without numbers on how they split:

  • Regret after a loss. The player made the deposit, lost it, and hopes the bank will reverse it.
  • Someone else in the household. A partner or a child used a saved card, and the cardholder honestly doesn't recognize the charge.
  • A descriptor the cardholder doesn't recognize. A statement line that doesn't match the brand the player knows reads as fraud.
  • Distress. A player losing more than they can afford may dispute as a way out. That one is a responsible-gambling signal as much as a dispute.

The responses differ. The first calls for evidence, the second for account controls and evidence, the third for a fix to how your merchant name appears, and the fourth for your responsible-gambling process alongside the dispute response.

Which dispute conditions does it arrive under?

As fraud, or as a service complaint. Visa's dispute conditions don't include "I lost", so a player who wants a deposit back has to claim one of the conditions that exist. The ones that fit a gambling deposit:

Visa conditionWhat the player tells the issuerWhat answers it
10.4 Other Fraud – Card-AbsentI didn't make this depositVerified identity, device and login history, geolocation at the time of deposit, prior undisputed deposits, play with the funds
13.1 Merchandise/Services Not ReceivedI paid and never got credited, or couldn't playLedger entry crediting the wallet, session logs, bets placed after the deposit
13.3 Not as Described or DefectiveThe game or the bonus wasn't what was promisedThe game rules and bonus terms the player accepted, with timestamps
13.2 Cancelled Recurring TransactionI cancelled and was still charged (only if you bill on a schedule, such as a membership)Cancellation records and the recurring terms the player agreed to

Dispute time limits and evidence formats are set by Visa's rules and your acquirer, and they aren't covered here.

The evidence an operator already holds

A licensed online casino or sportsbook keeps records a retailer doesn't: identity checks, location checks, a ledger of every bet. The task is to have those records joined to the transaction before a dispute arrives.

  1. Identity. The verified name, date of birth and address on the account, and whether they match the cardholder.
  2. Account history. How old the account is, earlier deposits on the same card that weren't disputed, and withdrawals paid to the player's own account or card.
  3. Device and login. The device and IP address used for the deposit, and whether they match the player's usual ones.
  4. Location. The geolocation check at the time of the deposit, which your licensing, and any Regulation GG certification you have given an acquirer, already depend on.
  5. Play. Bets placed with the deposited funds, their outcomes and timestamps, which shows the service was delivered and used.
  6. Terms. The terms, game rules and refund policy the player accepted, and when. Visa's §5.4.2.5 requires a merchant that restricts refunds to disclose that before final checkout with a click-to-accept or similar acknowledgement, so the record should exist.
  7. Contact. Support chats, complaints and any responsible-gambling interactions around the deposit.

A withdrawal paid to the same player's own card weeks before the disputed deposit is a hard fact for a cardholder claiming they never used your site. So is a geolocation record placing them in a licensed state at the time. Whether an issuer accepts the evidence is the issuer's decision, but a file that puts identity, location and play side by side gives it something to decide on.

Why 3-D Secure doesn't settle it here

At a US gambling merchant, authentication doesn't take the fraud claim off the table. Visa's §5.8.4.6 makes 3-D Secure authenticated transactions at MCCs 7801, 7802 and 7995 ineligible for protection from Condition 10.4, and the acquirer has to tell you so. A player who passed a 3DS challenge on the deposit can still file a fraud dispute, and you still have to answer it. What 3DS does and doesn't do at these codes is covered in our piece on 3D Secure and gambling chargebacks.

Stopping disputes before they become chargebacks

Every dispute that ends at the inquiry stage is one fewer chargeback in your history. Four controls work on that stage:

  • Purchase-inquiry data sharing. When the issuer asks about a transaction, your data on the deposit reaches it before a dispute is filed, rather than later in a representment.
  • A recognizable merchant name. Visa's §1.5.1.12 requires the name players know to be used consistently across authorization, clearing and dispute records, and lets the acquirer correct names that confuse cardholders.
  • Clear statement disclosure. A merchant that can't separate gambling from other sales must code everything as gambling and tell cardholders it may appear that way on statements, under §5.8.18.1.
  • Easy support. A player who can reach you in two clicks is less tempted to call the bank.

VyaShield, VyaPay's chargeback automation, handles the first of those and the response afterwards: automated dispute responses, and purchase-inquiry data sharing so more disputes stop before they become chargebacks. It doesn't decide outcomes; the issuer does.

What not to do

Three responses make a dispute problem worse.

  1. Don't pay winnings as a refund. Visa's §5.8.18.3 doesn't allow gambling winnings to be paid to a cardholder as a refund or credit of the deposit. Refunding an unplayed deposit is one thing; using a refund to move winnings is another.
  2. Don't spread disputes across accounts. Splitting volume or disputes so each account stays under a threshold is evasion. §10.4.6.2 lets Visa require direct contracting with a sponsored merchant that takes action to evade responsibility for compliance with the Visa Rules, and §10.4.5.4 lets it disqualify a high-integrity risk merchant that acts to circumvent its programs.
  3. Don't fight genuine fraud. If the card was stolen, the cardholder is right. Accept it, close the hole and keep the representment effort for the claims your records contradict.

Unmanaged dispute levels are one of the ways a gambling merchant loses its account, and a termination for cause can end with a MATCH listing, covered in how gambling merchants end up on the MATCH list.

Where friendly fraud shows up in your monitoring

In the same ratio as every other dispute. Acquirers' and chargeback vendors' descriptions of the Visa Acquirer Monitoring Program put TC40 fraud reports and TC15 disputes together in one numerator, over settled card-not-present transactions, with a 1.5% US merchant "Excessive" threshold since April 1, 2026. A friendly-fraud claim filed as fraud can show up in both parts of that numerator. Separately, Visa's §10.4.5.4 lets it disqualify a high-integrity risk merchant that reaches a critical level of disputes. How the ratio is counted is in our guide to Visa VAMP for gambling merchants.

Because VyaPay runs its own processor and underwrites risk in-house, dispute trends are read by the same risk team that made the underwriting call. If disputes are the part of a licensed program you want to talk through, talk to us about your program.

Frequently asked questions

Can a player charge back a gambling loss?

They can file a dispute, but losing isn't one of Visa's dispute conditions. The player has to claim fraud or a service problem, and the operator's identity, location and play records are what answer either claim.

Should we refund a deposit to avoid a chargeback?

Refunding unplayed funds can be cheaper than a dispute. What you can't do is use a refund of the deposit to pay out winnings; Visa's §5.8.18.3 rules that out.

Does friendly fraud count toward Visa's VAMP ratio?

Yes. As vendors report the formula, the ratio counts fraud reports and disputes, and a friendly-fraud claim arrives as one or both.

Is friendly fraud the same as true fraud with a stolen card?

No. In true fraud the cardholder never dealt with you; in friendly fraud they did. The difference is why evidence of identity, device and play matters: it shows which kind you're facing.

Sources

Talk to the team that underwrites you

Tell us about your licenses, your markets and your volume. You'll be talking to the people who run VyaPay's processor and make its risk decisions.

or call 833-4-VYAPAY

Let’s meet up!

Tell us about your business and someone from our team will reach out.