Friendly fraud explained: how to spot, prevent, and fight first-party misuse
Friendly fraud is a cardholder disputing a purchase they made. How to spot first-party misuse, what Compelling Evidence 3.0 needs, and a response playbook.
Friendly fraud, now called first-party misuse, happens when a cardholder disputes a purchase they actually made. It is rising and expensive to fight. Merchants that keep structured transaction and identity history can use Visa's Compelling Evidence 3.0 rules to defend more of these disputes, and pre-dispute tools can resolve many before they become chargebacks.
This guide explains what first-party misuse is, how to recognize it, what evidence defends against it and how to respond. It reflects Visa's merchant guide, Visa's monitoring fact sheet and the 2026 Visa and Merchant Risk Council fraud report, as of November 2026.
Key takeaways
- First-party misuse is a dispute on a real purchase. The cardholder, not a thief, made the payment.
- It is growing. In Visa and the Merchant Risk Council's 2026 report, 64% of respondents reported a meaningful increase.
- It is expensive. The same research puts the average cost to resolve one of these disputes at $82.
- History is your defense. Compelling Evidence 3.0 needs two earlier undisputed transactions with matching device or network details.
- Pre-dispute tools help twice. They refund the case early and keep it out of Visa's monitoring ratio.
What is first-party misuse?
First-party misuse is a card dispute raised by the real cardholder on a purchase they made or benefited from. The older name is friendly fraud. Visa uses both terms on its friendly fraud page and says friendly fraud is "also known as first party misuse".
It differs from third-party fraud, where a criminal uses a stolen card. It also differs from a valid consumer dispute, where the merchant did not deliver. The table shows how the three compare.
| Third-party fraud | First-party misuse | Valid consumer dispute | |
|---|---|---|---|
| Who made the purchase | A criminal with stolen card details | The cardholder or someone they know | The cardholder |
| What the cardholder says | "I did not make this purchase" | "I did not make this purchase" or "I never got it" | "I did not get what I paid for" |
| Is the claim true? | Yes | No | Yes |
| Best merchant response | Accept, then fix fraud controls | Respond with history and delivery evidence | Refund quickly |
First-party misuse usually arrives under a fraud reason code. That makes it look like stolen-card fraud in your reports. The chargebacks guide explains the reason code categories and the full dispute process.
Not every case is dishonest. Common causes include:
- A billing descriptor the customer does not recognize.
- A family member who used the card without telling the cardholder.
- A subscription renewal the customer forgot.
- Buyer's remorse, where a dispute feels easier than a return.
- Deliberate abuse, where the customer wants the item and the money.
Why is it rising?
It is rising because disputing a charge has become easy, and because some consumers now use tools built for abuse. The best current data comes from the 2026 Global eCommerce Payments and Fraud Report by Visa and the Merchant Risk Council (March 2026).
- 64% of fraud and payment professionals surveyed reported a meaningful increase in first-party misuse over the past year.
- 30% of merchants blamed newer fraud tools and tactics, including fraud-as-a-service and consumers using AI.
- $82 is the average cost to resolve one first-party misuse dispute, as summarized on Visa's dispute resolution page (last updated November 2, 2026).
- 17% of fraudulent disputes were attributed to first-party misuse, down from 20% the year before. North America stood at 21%.
The last figure looks like good news, and it partly is. The share fell while most merchants still reported more cases. One reading is that merchants are getting better at telling misuse apart from other fraud. Treat the share as a survey result, not a census.
The wider cost is larger than the disputed amount. LexisNexis estimated in its True Cost of Fraud Study (September 2023), as cited by Visa, that merchants spend $3.85 for every $1.00 lost to fraud. Visa also reports that it handled 105 million disputes in 2025.
How do you spot it?
You spot first-party misuse by comparing the disputed order with the customer's own history. A stolen card rarely matches the cardholder's device, address and login. A real customer usually does.
Look for these signals:
- The same device or IP address as earlier, undisputed orders.
- The same account login, especially one with a long history.
- The same delivery address, with a confirmed delivery.
- Use after purchase, such as logins, downloads or streaming on the account.
- Contact before the dispute, such as a refund request that was refused.
- A pattern of disputes from the same customer, device or address.
- A dispute shortly after a renewal, with no cancellation attempt on record.
No single signal proves misuse. Three or four together make a strong case, and they are the same data points the card networks accept as evidence.
What is Compelling Evidence 3.0?
Compelling Evidence 3.0 is a set of Visa rules that lets a merchant defend a card-absent fraud dispute by proving a purchase history with the same customer. Visa introduced it in April 2023, per PayPal. It applies to dispute condition 10.4, other fraud in a card-absent environment.
Visa's Dispute Management Guide for Merchants (October 2026 edition) sets the requirements.
| Requirement | What Visa's guide says |
|---|---|
| Number of earlier transactions | At least two, not reported as fraud by the issuer |
| Latest date | Processed more than 120 calendar days before the issuer submitted the dispute |
| Earliest date | Processed within 365 calendar days before the disputed transaction |
| Core match | The device ID, device fingerprint or IP address is consistent across the transactions |
| Additional match | Customer account or login ID, full delivery address, or other device or network information |
| Description | A description of the goods or services in the disputed and earlier transactions |
Some summaries describe the window as 120 to 365 days before the disputed transaction. Visa's guide measures the 120 days from the date the issuer submitted the dispute. Follow the guide and confirm the reading with your acquirer.
The 120-day rule has a practical logic. A recent purchase could still be disputed itself, so it proves little. Older purchases that were never reported as fraud show that the cardholder accepted them.
Compelling Evidence 3.0 has a second benefit. Visa's monitoring program fact sheet (2025) says fraud that qualifies for Compelling Evidence 3.0 is excluded from the monitoring ratio, depending on the timing of Visa's data extract.
What should a merchant capture at checkout?
You can only submit evidence you stored at the time of sale. Capture this on every online order:
- The IP address and a device ID or device fingerprint.
- The customer account or login ID, and the time of each login.
- The full delivery address and the billing address.
- The email address and phone number on the order.
- The authentication result, if you ran 3-D Secure.
- The address check and security code check results.
- A plain description of each item or service sold.
- Proof of delivery, or usage logs for digital goods.
- The terms, refund policy and cancellation policy the customer accepted, with a timestamp.
- A record of every support contact about the order.
Keep these records for at least a year, and longer if your acquirer advises it, because the lookback window is 365 days. Store them so they can be retrieved by transaction, not only by customer. Your privacy policy must cover this data, so check retention rules with counsel.
Which pre-dispute tools and alerts help?
Pre-dispute tools let you settle a complaint after the cardholder calls the issuer and before a chargeback is filed. They fall into three groups.
- Order information sharing. You send purchase details to the issuer in real time, so the agent or banking app can show the cardholder what they bought. Many "I do not recognize this" calls end there.
- Alerts. A service notifies you that a dispute is starting. You refund the payment and the chargeback is not filed.
- Automated resolution. You set rules in advance, such as "refund any dispute under a set amount", and the service applies them without manual review.
These tools matter for monitoring as well as for cost. Visa's fact sheet says disputes resolved through pre-dispute solutions are excluded from its monitoring ratio. PayPal (September 2026) adds that disputes resolved through Visa's Rapid Dispute Resolution service are excluded.
The trade-off is plain. An alert or automated refund gives up the sale. Use them where the order value is lower than the cost of fighting, and fight where the value and the evidence are strong.
Why are subscriptions and digital goods exposed?
Subscriptions and digital goods are exposed because there is no delivery signature, and because customers forget what they signed up for. A quarter of Mastercard chargebacks are linked to recurring transactions, according to Mastercard data cited by PayPal (September 2026).
Three habits lower the risk:
- Send a reminder before each renewal and after every price change.
- Make cancellation as easy as sign-up. A customer who cannot cancel calls the bank.
- Log usage. Logins, downloads and streams after the charge are your delivery proof.
Recurring card payments covers stored cards, consent and failed-payment recovery in detail. Authentication helps too: 3-D Secure on the first payment creates a record that the cardholder took part.
What does a response playbook look like?
A playbook turns each dispute into the same short sequence. It stops your team from fighting weak cases and missing deadlines.
- Triage within one business day. Read the reason code and the amount.
- Check the history. Look for matching device, login and address on earlier orders.
- Sort the case. Mark it as likely third-party fraud, likely first-party misuse, or a valid complaint.
- Refund valid complaints and accept true fraud. Then fix the control that failed.
- Build the evidence for misuse cases: two qualifying earlier transactions, the matching data and delivery or usage proof.
- Submit through your acquirer before its deadline, with a short summary.
- Record the result by reason code, product and customer.
- Act on repeat disputers. Flag the account, device and address under your terms of service.
- Review monthly. Compare your dispute ratio with the network thresholds and adjust alerts and rules.
What changed recently?
- April 2023. Visa introduced Compelling Evidence 3.0 for card-absent fraud disputes, per PayPal.
- June 1, 2025. Updated thresholds for the Visa Acquirer Monitoring Program took effect (Visa fact sheet).
- March 2026. The Visa and Merchant Risk Council report found that the share of fraudulent disputes attributed to first-party misuse fell from 20% to 17%.
- April 1, 2026. Visa's excessive merchant threshold dropped to 150 basis points in Asia Pacific, Canada, the EU and the US (Visa fact sheet).
- November 2, 2026. Visa updated its dispute resolution page, which reports 105 million disputes handled in 2025.
Sources
- Visa and Merchant Risk Council, 2026 Global eCommerce Payments and Fraud Report (March 2026): visaacceptance.com
- Visa, "Resolve issues earlier to help avoid chargebacks" (November 2026), including the LexisNexis True Cost of Fraud Study figure (September 2023): visa.com
- Visa, Dispute Management Guide for Merchants (October 2026): usa.visa.com
- Visa, Visa Acquirer Monitoring Program fact sheet (2025): corporate.visa.com
- Visa, friendly fraud overview (2026): corporate.visa.com
- PayPal, dispute management and chargeback prevention (September 2026): paypal.com
What to do next
Check whether your order system stores a device ID, IP address and login for every sale. If it does not, add them this month, because the evidence window looks back a full year. Then read chargebacks explained for the dispute process and how card payments work for the stages behind each sale. BlindPay is a stablecoin payout and collection API, and you can test its payins on a free development instance.
This article is general information, not legal, tax, or financial advice.
FAQ
More payments articles
See all payments articlesAcquirer vs issuer: the four-party card model explained with a $100 example
The issuer serves the cardholder, the acquirer serves the merchant, the network connects them. Follow a $100 card sale and see where each fee goes.
Cross-border payments explained: how they work, why they are slow and expensive, and what is changing
How cross-border payments work, why they are slow and costly, the G20 targets, BIS cost data and the FSB's November 2026 report, plus practical options.
Card payment step by step: where each fee is taken, how long each stage takes, and why declines happen
Follow one card payment from authorization to funding: how long each stage takes, where fees come out of a $100 sale, and why declines happen.