Chargeback
A chargeback is when a player's bank forcibly reverses a card deposit and pulls the money back from the operator, usually after the cardholder disputes the transaction.
Definition
A chargeback is a payment reversal initiated through the card scheme (Visa, Mastercard, etc.) by the cardholder's issuing bank, rather than a refund voluntarily given by the merchant. The cardholder claims a reason code — commonly fraud/unauthorised use ("I didn't make this transaction"), a processing error, or a "goods/services not as described" dispute — and the issuer credits them while debiting the operator's acquirer. The operator can contest it by submitting evidence (representment), which the issuer either accepts or escalates to arbitration under scheme rules. Beyond losing the deposited funds, the operator typically pays a per-case chargeback fee and, if its ratio climbs too high, risks costly monitoring programs or loss of card acceptance.
Worked example
A player deposits GBP 200 by Visa card and loses it in play. Two weeks later they tell their bank they didn't authorise the transaction and the issuer raises a fraud chargeback. The bank credits the player GBP 200 and debits the operator's acquirer, who also charges a roughly GBP 15-25 chargeback fee, so the operator is now out GBP 200 in wagered funds plus the fee. If the operator can prove the deposit was legitimate — device and IP data, KYC-verified identity, login history, and a record that funds were knowingly wagered — it may win the dispute through representment; if not, the loss stands. Card schemes also watch the operator's chargeback ratio (disputes divided by transactions): sustained breaches of thresholds such as Visa's ~0.9% or ~1% can trigger a scheme monitoring program with additional fines.
Why it matters
Chargebacks sit at the intersection of payments, fraud, and player-protection risk, so they matter to almost every commercial and compliance role. High chargeback rates directly erode net revenue and can jeopardise an operator's ability to accept cards at all, making them a core payments-health KPI. They also surface abuse patterns worth understanding — genuine card theft, "friendly fraud" where a real player disputes their own losses, and problem-gambling signals — which is why robust KYC, transaction monitoring, and clear deposit records are the standard defences a professional is expected to know.
Related
Note: The general mechanism is a stable definition, but specifics vary and should be verified against current sources. Reason codes, dispute time limits (often up to ~120 days but scheme- and reason-dependent), representment/arbitration steps, per-case fees, and monitoring-program thresholds are set by each card scheme (Visa, Mastercard, etc.) and change over time — the ratio figures cited are illustrative, not fixed. Exact rights and processes also differ by jurisdiction and by non-card rails (e-wallets, bank transfers, and open banking have their own dispute regimes).