Chargebacks in iGaming: How Card Disputes Work and How to Reduce Them

How does a chargeback work?

Why do online casinos get chargebacks?

For the fraud side in depth, see chargeback fraud.

What are card scheme monitoring programmes?

Card schemes monitor merchants whose ratio of disputes, and for Visa also fraud reports, to transactions is too high. Visa’s Visa Acquirer Monitoring Program (VAMP) replaced its earlier separate fraud and dispute programmes from April 2025; Mastercard runs the Excessive Chargeback Program ^[1]. Merchants above thresholds pay per-dispute fees, follow remediation plans and can lose acceptance.

How can operators reduce chargebacks?

1. Verify before depositUp-front KYC, already required in most regulated markets, removes most stolen-card fraud. See KYC rules by market.
2. Authenticate with 3-D SecureStrong customer authentication shifts fraud liability to the issuer for authenticated transactions in many regions.
3. Match card names to the accountBlock or review cards in another person’s name.
4. Pay withdrawals promptlyA held payout is one of the most common dispute triggers.
5. Send deposit receiptsEmail or in-app confirmations with the descriptor help players recognise charges.
6. Offer bank-based alternativesPay-by-bank and instant rails have no card chargeback; see open banking.
7. Resolve complaints in supportMany disputes start as unanswered complaints; see stopping chargebacks in support on igaming.cx.

What evidence wins a representment?

• KYC record showing the account holder matches the cardholder
• 3-D Secure authentication result for the disputed transaction
• Device ID, IP address and geolocation matching earlier undisputed activity
• Gameplay logs showing the funds were used by the account holder
• Terms and conditions accepted at registration
• Support transcripts in which the player discussed the deposit or play

Support transcripts are often overlooked. Searchable conversation data, for example through tools such as Cevro Scribe, makes evidence packs faster to assemble.

How should support handle a player who threatens a chargeback?

Treat it as a complaint and a possible safer gambling signal. Check whether a withdrawal is stuck or a deposit failed, explain the complaints process and, where relevant, alternative dispute resolution. If the player says they did not authorise the payment, escalate to fraud and restrict the account by policy. If there are signs of distress, follow responsible gambling procedures; see markers of harm.

Which teams handle chargebacks?

How should operators decide whether to fight a chargeback?

What should support say when a player mentions a chargeback?

A calm, specific reply works best: acknowledge the problem, check what triggered it, explain the complaints route and what will happen next. For example: “I can see your withdrawal of £400 is waiting for a document check. Once you upload the bank statement we asked for, we can usually approve it the same day. If you are unhappy with how we have handled this, our complaints process is here, and you can take an unresolved complaint to our independent ADR provider.” Avoid threats, and never discuss fraud suspicions with the player.

Which dispute reason codes do operators see most?

Card schemes group disputes into categories. The labels differ between schemes, but most gambling disputes fall into fraud (the cardholder says they did not authorise the payment) or consumer disputes (the cardholder says they did not get what they paid for).

Simplified. Check your acquirer’s current scheme rules.

How long does a chargeback take?

1. Day 0
   Player deposits by card.
2. Day 45
   Player loses the balance, then contacts the bank claiming the deposit was not authorised.
3. Day 47
   Issuer raises a dispute; the acquirer debits the operator and notifies it.
4. Day 50
   Operator gathers evidence: login IPs, device, 3-D Secure result, verified identity, game history.
5. Day 55
   Operator submits representment through the acquirer.
6. Day 80
   Issuer accepts the evidence; funds return to the operator. The account is reviewed for friendly fraud and safer gambling concerns.

Cardholders can often dispute for up to about 120 days after the transaction for many reason codes, so losses can arrive months later. Timeframes vary by scheme and reason code.

How do you calculate a chargeback ratio?

Track the ratio by method, market, acquirer and acquisition channel. A spike from one affiliate or one market often points to fraud or to a confusing offer.

How does a card dispute move through the system, step by step?

1. The cardholder contacts the issuerThe player tells their bank that a payment was unauthorised, not delivered or wrong. The issuer decides whether the claim fits a scheme reason code.
2. The issuer raises the disputeThe issuer files the dispute through the card scheme. The disputed amount is usually taken back from the merchant straight away.
3. The acquirer notifies the operatorThe operator’s acquirer or PSP passes on the dispute with a reason code and a deadline to respond.
4. The operator decides: accept or fightAccepting closes the case. Fighting means a representment with evidence that matches the reason code.
5. The issuer reviews the evidenceIf the issuer accepts the evidence, the funds return to the operator. If not, the case can move to a second stage.
6. Pre-arbitration and arbitrationEither side can escalate. At arbitration the card scheme decides, and the losing side usually pays a fee, so operators escalate only strong cases.
7. Close the loop on the accountWhatever the outcome, review the player account: fraud signals, safer gambling concerns, and whether to restrict further card deposits.

Which regulators shape chargeback risk in each market?

Card schemes, not gambling regulators, run the dispute process. But gambling rules decide which cards and accounts can be used at all, which changes the kinds of disputes operators see.

What does a good chargeback programme look like?

Strong programmes treat chargebacks as a symptom to fix, not only a cost to fight. They combine prevention at deposit, fast evidence at dispute, and learning afterwards.

igaming.cx explains stopping chargebacks in support.

Worked example 2: a true fraud dispute

1. Day 0, 02:10
   A new account deposits five times in 20 minutes using three different cards. Two attempts are declined.
2. Day 0, 02:12
   Velocity rules flag the account; deposits are paused and the account is sent for fraud review.
3. Day 0, 09:00
   The analyst sees a device linked to other new accounts and a name mismatch on one card. The account is closed and the balance frozen pending review.
4. Day 12
   A chargeback arrives on one of the cards with a fraud reason code.
5. Day 13
   The operator accepts the chargeback rather than fighting it, because the evidence supports true fraud, and refunds the other cardholders proactively.
6. Day 14
   Linked device and identity data are added to blocking rules; the case is reviewed for suspicious activity reporting.

Fighting a true fraud case wastes fees and harms the operator’s standing with its acquirer. Accepting quickly and refunding other affected cardholders reduces further disputes.

How do chargeback risks differ by market?

Worked example: a friendly fraud dispute

What mistakes do operators commonly make?

Checklist

• KYC complete before first card deposit.
• 3-D Secure on card deposits.
• Card name matched to the account.
• Billing descriptor matches the brand.
• Deposit receipts sent.
• Evidence pack template ready, including support transcripts.
• Dispute ratio tracked by acquirer monthly.
• Chargeback threats routed to fraud and safer gambling checks.
• Represent-or-accept matrix agreed.
• Support script for chargeback threats.
• Harm review for distress disputes.
• Chargeback ratio by acquirer, market and affiliate.
• Evidence pack template per reason category.

Frequently asked questions

Sources

More guides