What Is Chargeback Fraud? Types, Warning Signs and How to Stop It
What Is Chargeback Fraud? Types, Warning Signs and How to Stop It
Global Payments

Published on 20/11/2026

What Is Chargeback Fraud? Types, Warning Signs and How to Stop It

Collect from Indian customers with fewer fraud disputes

Talk to Xflow about UPI, RuPay and netbanking alongside cards, settled to you abroad.

Chargeback fraud, also called friendly fraud or first-party fraud, is when a cardholder disputes a card payment they really made and gets their money back from their bank. The merchant loses the payment and the goods, and usually pays a dispute fee too.


The same fraud-coded dispute also follows stolen-card fraud, where a criminal pays with someone else's card details and the real owner rightly reverses the charge. The dispute alone rarely tells you which one you face, and the defence for each is different.


Your best protection sits before the sale: checks at checkout, a short list of warning signs and good records. After a dispute arrives, the result depends on evidence you already hold, and whether a dispute is a crime depends on who lied and where.


What chargeback fraud means and how a fraud-coded dispute works

A chargeback is a forced reversal of a card payment, raised by the cardholder through their bank. You can read how the whole process works in the guide to what is a chargeback. The fraud version starts when someone tells the bank, or issuer, that they did not authorise a payment.


Fraud is a hard dispute type to win, because in many cases the claim is correct. A fraud-coded dispute usually follows four steps:


  • The cardholder reports the charge - they tell their issuer they do not recognise the payment or did not make it, often after an early fraud warning has already reached your processor.
  • The issuer files a dispute - the bank raises a chargeback under a fraud reason code, such as Visa 10.4 for card-not-present fraud or Mastercard 4837 for no cardholder authorisation.
  • Your account is debited - the acquirer, the bank that processes your card sales, takes the funds back and tells you, so you can accept the loss or send evidence.
  • The issuer decides - the cardholder's bank, not your processor, reviews any evidence and makes the final call, which can take around two months after you respond.

Three types of chargeback abuse merchants run into

Chargeback abuse covers three quite different sources of fraud-coded disputes: criminals using stolen cards or accounts, real customers disputing their own purchases, and seller mistakes the customer reads as fraud.


Each one needs a different fix, so it helps to know which one you are dealing with before you change checkout rules or start answering disputes. Only the first is fraud in the criminal sense, while the other two start with a real customer who has a reason, good or bad, to contact their bank.


Criminal fraud with stolen cards or account takeover


True third-party fraud starts with a criminal who buys using card details taken in a data breach, a phishing scam or a stolen card, then the real owner disputes the charge. Card details stolen online are more common than stolen plastic, because the buyer never needs the physical card.


Account takeover is the second route. A criminal logs into a real customer's account with a stolen password and uses the saved card, so the order looks like it came from a trusted buyer. Card testing, where scripts run many small payments to see which stolen numbers still work, often comes before both.


Friendly fraud by the real cardholder


With friendly fraud, the person disputing really did make the purchase. They may not recognise the billing name, forget a renewal, or keep the goods and claim the payment was not theirs. Visa also calls this first-party misuse.


Because the buyer is genuine, checkout checks such as CVV and 3-D Secure usually pass, so the fix sits in clear billing, easy refunds and saved proof of each order. Causes, prevention and evidence are covered in the guide to friendly fraud.


Merchant errors that get coded as fraud


Some fraud-coded disputes start with the seller. A billing name the customer cannot place, a double charge, a refund that never went through or an order that never arrived can all push a customer to tell the bank "this was not me". An unrecognised charge is treated much like a fraud claim.


A clear statement descriptor, quick refunds and visible contact details remove most of these. Merchant-side fraud, where a seller takes payments and sends nothing, is a separate problem that acquirers police, and it rarely appears on your own dispute list.


Stolen-card fraud vs friendly fraud vs merchant error, side by side

Stolen-card fraud, friendly fraud and merchant error can all arrive under the same fraud reason code, so the code alone will not tell you which one hit you. Use the purchase history and your own records to place each dispute in the right column before you choose a response.

Stolen-card fraudFriendly fraudMerchant error
Who made the purchaseA criminal using someone else's card or accountThe real cardholder or someone in their homeThe real cardholder
Who losesYou, after the real cardholder is refundedYou, while the customer keeps the goodsYou, often for a problem that a refund would have fixed
Usual reason codeVisa 10.4, Mastercard 4837Fraud codes or "not received" codes"Not received" or "not as described" codes, or fraud codes if the charge is unrecognised
What helps most3-D Secure, address and CVV checks, fraud rulesClear billing, easy refunds, order and usage recordsClear billing name, fast refunds, reachable support

Is chargeback fraud illegal, and do banks or police investigate?

Using a stolen card is a crime in most countries. A cardholder who knowingly lies to their bank to get money back may also be breaking the law. In England and Wales, a dishonest false claim made for gain could fall under fraud by false representation in section 2 of the Fraud Act 2006, though whether anyone is prosecuted is a separate matter.


In practice, the issuer decides the dispute and does not usually pursue the customer. A bank may close an account it sees abusing disputes, and you can refuse future orders. For a single false dispute, your realistic options are your evidence and blocking repeat disputers, not a police case.


Criminal schemes are different, especially when stolen cards or card testing hit you at scale. You can report them through these routes:


  • Your acquirer or payment processor first - they can flag the cards involved, help you send fraud reports to the networks and tighten your fraud rules before more orders go through.
  • Report Fraud (formerly Action Fraud) in the UK - the national reporting service run by the City of London Police, which replaced Action Fraud on 4 December 2025 for reporting fraud and cyber crime.
  • The FBI's IC3 in the US - the FBI's online crime complaint service collects reports about internet crime, though it says it does not investigate them itself and may not contact you.

Warning signs of credit card chargeback fraud before you ship

Credit card chargeback fraud is easiest to stop before the goods leave. One sign alone does not prove fraud, but several together should send the order for manual review. These are the patterns worth checking on any order that looks unusual.


  • Mismatched details - the AVS check returns an address mismatch, the CVV fails, or the shipping country differs from the country where the card was issued.
  • Odd contact details - the email looks random, the phone number does not work, or the same email appears on orders under several different names.
  • Unusual order size - a first-time buyer orders far more than your average basket, or picks only your most expensive items with little interest in the price.
  • Many cards, one address - several cards ship to one address, one card ships to many addresses, or the buyer asks to split a large order across cards.
  • Rush and redirect requests - the buyer pays for the fastest shipping, changes the address after ordering, ships to a freight forwarder or asks to use their own shipper.
  • Card-testing patterns - a run of declines with different cards, many tiny payments, or nonsense names on checkout.


For digital goods, look for many purchases in a short window, accounts with similar email addresses and paid accounts that are never used.


Which businesses get hit by chargeback scams and what they lose

Chargeback scams cluster where goods are easy to resell or deliver instantly. Digital goods are more likely to attract stolen cards, and card testing mostly targets sites with an open amount field, such as donation pages. Travel and event bookings can also see disputes arrive long after the payment, because the dispute window can start on the event date. Sellers taking orders from abroad face extra cross-border payment fraud checks too.


On a stolen-card dispute you lose more than the sale. You lose the payment, the goods or service already delivered, the dispute fee and the staff time to review it. Card-testing bursts add extra fees and a higher decline rate, which can make issuers more cautious with your genuine customers.


The larger risk is your dispute ratio. Card networks watch disputes and fraud reports against your card sales, and a high ratio can lead to fines, higher processing costs or the loss of your merchant account. That is why a cluster of stolen-card orders matters even when each one is small.


How to prevent fraudulent chargebacks from stolen cards

Fraudulent chargebacks from stolen cards are the one type you can block at checkout, because the buyer is not the cardholder. Chargeback fraud prevention works best in layers, since each check catches something the others miss and any single check also stops some good customers.


Start with simple checks on every order, then add stronger ones for riskier orders. The five layers below run from the card checks at checkout to the records you keep once the order has shipped.


Address and CVV rules at checkout


Most merchants ask for the CVV on every new card. Merchants are not allowed to store it, so it is rarely exposed in data breaches. Then decide what happens on a mismatch: block a failed CVV, and send a failed address check for review rather than an automatic decline, since genuine buyers mistype postcodes or have recently moved.


Address checks work best on cards from the US, Canada and the UK, where most issuers support them. Elsewhere, an empty result is common and means nothing either way. Neither check helps if a criminal has the physical card, so treat both as one layer, not the whole defence.


3-D Secure and the liability shift


3-D Secure adds a step where the cardholder confirms the payment with their bank, often through an app or a one-time code.


If an authenticated payment is later disputed as fraud, the liability shift typically moves the loss from you to the issuer. It covers fraud claims only, not "item not received" disputes.


The shift also has limits you should check before you rely on it:


  • Fraud programmes - the shift may not apply if your account is already in a card network fraud monitoring programme for high dispute or fraud levels.
  • Unanswered enquiries - if the issuer asks about an authenticated payment and you do not reply, the dispute that follows can lose the protection.
  • Lost sales - extra steps can make some buyers give up, so many merchants apply 3-D Secure to riskier orders only, where local rules allow.


Velocity checks and fraud scoring


Velocity limits cap how often something can happen in a set time. They stop card testing and stolen-card bursts before most of the orders go through. Common rules worth setting include:


  • Cards per account or device - limit how many different cards one account, device or IP address can try in a day, then block or review the rest.
  • Attempts per IP address - slow down or add a CAPTCHA once one address passes a set number of payment attempts in a short period.
  • Login before payment - require an account on high-value or high-risk products, so a criminal has to get through one more step first.


Pair these rules with the risk score your payment provider gives each payment, and review the middle band by hand. Authorising first and capturing later gives you time to check, since a payment you never capture cannot be disputed.


Fraud tools and chargeback guarantees


Dedicated fraud tools score orders with data from many merchants, which catches patterns your own rules cannot see. A chargeback guarantee goes further: the provider screens each order and pays you back if an approved order later comes back as a fraud chargeback.


The cover needs a close read before you sign. Base plans of a chargeback guarantee usually cover fraud-coded disputes only, on orders the provider approved, and may leave out friendly fraud, declined orders and some regions. Pre-dispute alerts from the card networks can also let you refund before a dispute is filed, as explained in the friendly fraud guide.


Delivery and transaction records you will need later


Every order should leave a record you can send if a dispute arrives. For a fraud claim, the details that matter most are the ones that tie the cardholder to the purchase:

RecordWhy it helps against a fraud claim
IP address and device IDShows the order came from a device the cardholder used before
AVS, CVV and 3-D Secure resultsShows the payment passed the checks the issuer relies on
Tracking and delivery proofShows goods reached the cardholder's own address
Signature on deliveryGives stronger proof for high-value orders
Login and usage logsShows the customer used a digital product after paying
Terms accepted at checkoutShows the customer agreed to your refund and billing terms

Save tracking as screenshots, because issuers often do not open links.


How to fight a fraud-coded chargeback with the right evidence

Start by asking whether the claim is true. If the order matches the warning signs and the cardholder clearly never bought from you, accepting the dispute is usually the better call, since a weak response only costs more time. If you spot a fraud order before any dispute, a full refund stops it being disputed at all.


When you believe the real cardholder made the purchase, answer with evidence that links them to it. Cardholders usually have up to about 120 days from the payment to raise a dispute, so a claim can arrive long after you ship. Once it does, processors usually give you a short window, often a few weeks depending on the network, and one chance to submit. These are the items that tend to win fraud-coded disputes:


  • 3-D Secure authentication - proof the payment was authenticated, which should move the loss to the issuer if the liability shift applies to that payment.
  • Matching AVS and CVV results - proof the billing address and card code entered at checkout matched what the issuer holds for that cardholder.
  • Delivery to the cardholder's address - tracking that shows the goods reached the billing address or an address used on earlier, undisputed orders.
  • Earlier undisputed payments - past orders on the same card with the same device, IP address or account, which Visa's Compelling Evidence 3.0 rules can use for repeat customers.
  • Use of the product - logins, downloads or usage after the purchase date, or a message from the customer that shows they recognise the charge.


If the amount is small and the evidence thin, letting the dispute go can cost less than fighting it. Either way, record the outcome and feed what you learn back into your checkout rules.


Taking card payments from customers in India with Xflow Import

If you sell to customers in India from abroad, Xflow Import lets you collect from them through Visa, Mastercard, RuPay, UPI, UPI AutoPay, e-NACH and netbanking, with funds settled to you outside India, usually within two business days.


Visa and Mastercard payments from India follow the card network dispute rules covered above, while RuPay, UPI and netbanking may follow different dispute and complaint routes. That gives your Indian customers familiar ways to pay without changing how you run your business abroad. See how to accept international payments from India with Xflow.

Collect payments from customers in India


Final word on spotting and stopping card fraud disputes

Most fraud-coded disputes come from stolen cards, real customers who dispute their own purchase, or seller mistakes. Stolen-card orders are the ones you can stop at checkout with CVV, address checks, 3-D Secure and velocity limits.


Keep the records that tie each buyer to each order, accept the disputes that are clearly true and answer the rest with evidence. Watch your dispute ratio monthly, so card network programmes do not catch you by surprise.


Frequently asked questions

Yes. A merchant can take payments and send nothing, which acquirers watch for. Cases like that are usually treated as merchant fraud rather than chargeback fraud, and the acquirer can end the merchant's account.

Mostly, yes. In everyday use, chargeback fraud means friendly fraud, also called first-party fraud, where the real cardholder disputes their own purchase. The term is also used for disputes that follow criminals using stolen cards.

A fraud reason code is the label an issuer uses when a cardholder says they did not authorise a payment.


Visa uses 10.4 for card-absent fraud and Mastercard uses 4837. Processors also often list Mastercard 4863 for "does not recognise" disputes.

Card testing is when criminals run many small payments, often with scripts, to find which stolen card numbers still work. It leads to declines, fees and later stolen-card disputes, and is also called carding.

Tell your acquirer or payment processor first, so they can flag the cards. In the UK, criminal schemes go to Report Fraud (formerly Action Fraud).


In the US, you can file with the FBI's IC3, which collects complaints but does not investigate.

Visa's VAMP marks a merchant as excessive at a 1.5% ratio of disputes plus fraud reports (and at least 1,500 of them in a month) in most regions.


Mastercard's excessive chargeback programme starts at about 100 chargebacks and a 1.5% rate in a month. Your processor may set lower limits.

No. Most guarantee plans cover fraud-coded disputes on orders the provider approved. Friendly fraud, declined orders and some reason codes are often left out on base plans, so check the reason codes and exclusions in the contract.

Related Posts