Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Feb 8, 2026
Friendly Fraud
Unauthorized
Customer Acknowledgment
Behavior Signals

How Do I Know If A Dispute Is Friendly Fraud?

In this article

Chargebacks?
No longer your problem.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.

600+ reviews
No credit card needed.

TL;DR:

  • A dispute is friendly fraud when the real cardholder disputes a purchase they made, by mistake or on purpose; delivery or a matching IP alone does not prove it.
  • Read the reason code first: each claim, from Visa 10.4 to 13.6, has its own signs of misuse and its own signs of a real problem.
  • For Visa 10.4, passing the CE3.0 test with two earlier undisputed orders is a strong sign the cardholder made the purchase.
  • For Mastercard 4837, check whether you can send First-Party Trust device, delivery, and identity data.
  • Label cases for your team, then answer the issuer with facts, not claims about intent.

A dispute is friendly fraud when the real cardholder disputes a purchase they made, by mistake or on purpose. To know, compare the claim with your records for that order. Delivery, account history, or a matching IP address can point that way, but none of them proves it alone.

Written by Chargeflow Experts. Updated 12 November 2026.

Start With the Allegation and Competing Explanations

ObservationPossible explanationNext check
Product was usedApproved use, shared access, or account takeoverAccount history and payment checks such as 3D Secure
Customer contacted supportThey knew about a problem, which is not the same as approving the chargeWhat the messages actually say
Refund came before the disputeA refund that is pending, partial, failed, or sent twice. A fully refunded payment cannot be disputed, but a partly refunded one can.Refund status and payment reference
Repeat complaintsMisuse, or a problem you keep causingThe facts and outcome of each order

Stripe’s guide to fraud types says first-party misuse can be accidental, such as a charge the buyer did not recognize, or deliberate. It also says a payment that went through can still be unauthorized. So do not judge intent from approval or delivery alone.

Read the Claim by Reason Code

The chargeback reason code tells you what the cardholder claims. Each code has its own signs of first-party fraud and its own signs of a real problem.

ClaimPoints to friendly fraudPoints to a real problem
Fraud, card absent: Visa 10.4, Mastercard 4837Same device, IP, or login as earlier undisputed orders. Delivered to the usual address. The buyer kept using the account.New device and location, a password reset just before checkout, or a changed shipping address
Not received: Visa 13.1, Mastercard 4853Carrier scan shows delivery to the right address. Later orders went to the same place.No delivery scan, a wrong address, or a support ticket about a missing item
Canceled subscription: Visa 13.2, Mastercard 4841No cancel request on file, and logins continued after the renewalA cancel request on file before the renewal date
Not as described: Visa 13.3, Mastercard 4853No complaint or return request before the disputeA complaint, return request, or known product defect
Credit not processed: Visa 13.6The refund already went out, with a reference numberA refund was promised but never sent

Cardholders have 120 days from the transaction or expected delivery date to file under most Visa and Mastercard reason codes. Your processor’s response deadline is much shorter, so sort the case on the day it arrives.

Build a Factual Timeline

Line up the order, payment, delivery or service, customer messages, cancellation, refund, and dispute. Mark any missing record. If two systems disagree, find out why. Do not keep only the records that help your side.

Check for refund and dispute overlap and read the unauthorized-payment steps before you call the case misuse.

Run the CE3.0 and First-Party Trust Checks

For a Visa fraud claim under reason code 10.4, the network gives you a built-in test. Visa Compelling Evidence 3.0 asks for two earlier undisputed orders on the same card, 120 to 365 days old.

Those orders must share at least two data points with the disputed one, such as IP address, device ID, account login, or shipping address. One of the two must be the IP address or device ID.

If the order passes, you have a strong sign that the cardholder made the purchase, and liability moves back to the issuer. If it fails, the case may still be friendly fraud, but you need other compelling evidence.

For Mastercard 4837 claims, check whether you can send Mastercard First-Party Trust data. That means one device data point, one delivery data point, and one more identity data point for the order.

Hypothetical example: A $180 order is disputed under Visa 10.4. The buyer ordered from the same laptop and login twice before, 140 and 290 days earlier. Neither order was disputed, and this one was delivered to the address on file. It passes CE3.0, so you fight it.

If the laptop and login were new and the password was reset an hour before checkout, treat it as possible account takeover.

Keep Signals Separate From Proof

Payment checks, device matches, and returning accounts help frame a review. They do not prove who someone is. A familiar account can be hacked, and a new device can belong to a real customer.

Label each case as merchant error, suspected third-party fraud, suspected first-party misuse, or unresolved. These labels are for your team only. Your formal response still has to answer the dispute reason and its rules. The guide to friendly fraud vs stolen card fraud shows how the labels differ.

Choose the Response on the Merits

If the customer has a real problem, fix it. If your records support a challenge, state the facts without accusing the cardholder or claiming to prove intent. A friendly fraud response template helps you keep that tone. Do not use an industry average to judge one complaint.

Use repeat-pattern review for linked cases and the evidence checker for submission problems. Chargeflow’s chargeback recovery workflow builds and submits the case file for you, and Chargeflow Insights shows which reason codes keep coming back.

A Four-Branch Triage You Can Document

Team labels only · not findings about intent

Pick the branch your records support

Merchant error supported

Records show failed delivery, the wrong product, or a missed cancellation. Fix the issue through the right refund or case route.

Account compromise supported

Look into the unauthorized-charge claim and your login and security records.

First-party misuse suspected

Note where the claim conflicts with your records, plus any CE3.0 purchase history. Keep what you saw apart from guesses about intent.

Unresolved facts

Keep every possible cause open, ask for the missing record, and give the case an owner before the deadline.

Keep the provider’s formal dispute reason and rules apart from these team labels.

Unclear example: A login follows a purchase, but the customer reports account takeover. The login shows account activity, but who approved the payment is still open. Check the current fraud rules and the fight-or-accept decision guide before you challenge it.

Frequently Asked Questions

Does Receiving the Product Make a Dispute Friendly Fraud?

Receiving or using a product does not by itself make a dispute friendly fraud. Account takeover, product problems, or billing errors can still explain the complaint.

Does Contacting the Bank Before Support Prove Abuse?

Contacting the bank before support does not prove abuse or intent. Judge the dispute on the order records and the claim the cardholder made.

Should I Tell the Issuer the Customer Is Lying?

No, do not tell the issuer the customer is lying. State facts the issuer can check and explain your defense. A claim about the customer’s intent does not replace evidence.

What Is the Difference Between Friendly Fraud and True Fraud?

Friendly fraud is a dispute from the real cardholder about a purchase they made. True fraud, or third-party fraud, is a purchase made by someone using stolen card or account details. Both often arrive under the same fraud reason codes, such as Visa 10.4 and Mastercard 4837.

How Long Can a Customer Wait to File a Friendly Fraud Chargeback?

A cardholder has 120 days from the transaction or expected delivery date to file a friendly fraud chargeback under most Visa and Mastercard reason codes. Your processor then gives you a much shorter deadline to respond.

SHARE THIS ARTICLE

Chargebacks?
No longer your problem.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.

600+ reviews
No credit card needed.
subscribe

The latest chargebacks, fraud, and ecommerce content, in your inbox. Every week.

By providing your email you're agreeing to our Terms of Service and Privacy Notice
Diagram with dashed and curved lines forming segmented arcs highlighted by three blue diamond markers on the left side.Abstract circular grid design with blue diamond markers on a half-black, half-white background.

More articles.

June 4, 2026

How Do I Track Dispute Performance Across Multiple Accounts?

Track dispute performance across multiple accounts with clear rate definitions, a reconciled case register, weighted win rates, net recovery after fees, and a fixed report schedule.

Dispute Workflows
Processor Behavior
Dispute Decisioning
Representment Strategy
Chargeback Ratio
June 4, 2026

How Do I Standardize Evidence Across Dispute Types?

Standardize chargeback evidence with one core record set, a module for each dispute category, a fixed file format, and a check that each response was sent.

Proof of Delivery
Transaction Logs
Bank Requirements
Representment Strategy
June 4, 2026

How Do I Align Customer Support and Payments to Reduce Disputes?

Align customer support and payments with a shared case record, complaint-to-dispute playbook, refund and dispute overlap rules, and subscription habits that cut disputes.

Dispute Workflows
Poor Communication
Customer Confusion
Refund Timing Issues
Friendly Fraud
Frequently Asked Questions

Questions?
we’ve got answers.

What makes Chargeflow different from Stripe Disputes?

Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..

How does Chargeflow fight chargebacks?

Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.

Can Chargeflow handle chargebacks from multiple payment processors?

Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.

How does Chargeflow Automation’s pricing work?

Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.

Is Chargeflow safe to use?

Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.

need more help?

Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.