First-Party Fraud Automation: Fight Friendly Chargebacks
Payments News

Automation vs. First-Party Fraud: How to Fight Friendly Chargebacks

First-party fraud automation can cut what each dispute costs you. See what to automate, which calls need a person, and how to protect your Visa VAMP ratio.

Smiling woman in headphones working at a laptop with sticky notes and an open notebook at a home office desk

Photo: Pixabay

On this page 7 sections
  1. What PaymentsJournal Reported on Nov. 11
  2. Friendly Fraud vs. True Fraud: How Each Lands in Your VAMP Ratio
  3. Where First-Party Fraud Automation Pays Off
  4. What Still Needs a Human in Dispute Representment
  5. Worked Example: When a Friendly Chargeback Is Worth Fighting
  6. Policy Fixes That Prevent Disputes Before They Count
  7. Measuring Results: Win Rates, Dispute Ratios and Cost per Dispute

Key takeaways

  • Automate evidence capture, Compelling Evidence 3.0 matching and pre-dispute alert rules. Keep people on high-value disputes, real service failures and decisions to cut off repeat abusers.
  • Under Visa's VAMP, winning a normal representment gets your money back but doesn't take the dispute out of your count. Only qualifying pre-dispute resolutions and CE3.0-qualified fraud reports are excluded.
  • Break-even win rate = cost to fight a dispute ÷ amount you'd recover. Automation lowers that cost enough that many small disputes become worth fighting.
  • As issuers automate their side, low-dollar claims they used to write off may get decided case by case. Watch your dispute mix for changes.

The practical way to fight friendly chargebacks is to split the work. Let first-party fraud automation handle evidence collection, data matching and pre-dispute alerts, and keep people on the expensive, judgment-heavy calls. Then fix the billing, receipt and cancellation habits that cause disputes in the first place. Prevention and a few specific Visa tools keep disputes out of your monitoring ratio. Winning a dispute after it's filed gets your money back, but the dispute still counts against you.

What PaymentsJournal Reported on Nov. 11

On Nov. 11, 2026, PaymentsJournal published "How Automation Is Changing the Fight Against First-Party Fraud." The piece is built on a podcast with Pallavi Kuppa-Apte, CEO and co-founder of Decisionly, and Suzanne Sando, lead analyst of fraud management at Javelin Strategy & Research. Decisionly sells AI-powered dispute automation to card issuers. According to Finovate, its founders previously built Chargehound, a dispute automation tool for merchants, so the conversation draws on both sides of a chargeback.

The piece reports 160 million disputes filed in the prior year. It also cites studies, which aren't named in the summary we reviewed, suggesting that as many as half of disputes may involve first-party fraud. Sando said first-party fraud has come to be seen as a victimless crime. Kuppa-Apte described issuers with manual processes running up against deadlines and writing off claims instead of investigating them, especially low-dollar ones. Her point that matters most for merchants: "you often don't know it's first-party fraud until the result of that dispute."

The article argues that automation changes the economics on both sides. Merchants no longer have to pick a few disputes to fight and can respond to nearly all of them.

Here's one thing to watch, and this is our read, not something the podcast said. If issuers automate intake and stop writing off small claims, some disputes they used to absorb may now be decided case by case. Some may be screened out at intake as misuse, and others may reach you as chargebacks. Nobody knows yet how that nets out for a given merchant, so track your dispute volume by ticket size over the next few quarters.

Friendly Fraud vs. True Fraud: How Each Lands in Your VAMP Ratio

True fraud means someone used a stolen card or a hijacked account. Friendly fraud, which Visa's Compelling Evidence 3.0 readiness guide also calls "first party misuse," means the cardholder made or authorized the purchase and disputed it anyway. Sometimes it's deliberate. More often it's a forgotten subscription renewal, a teenager using a parent's saved card, a charge the cardholder didn't recognize on the statement, or a customer who couldn't figure out how to cancel. We cover the warning signs in our guide on how to spot friendly fraud without losing good customers.

The label matters because a lot of friendly fraud arrives looking like true fraud. A cardholder who says "I didn't authorize this" triggers a fraud dispute, whatever really happened. On a Visa card-not-present sale, that's reason code 10.4.

That dispute then feeds Visa's Acquirer Monitoring Program (VAMP). Visa's 2025 fact sheet defines the VAMP ratio as the count of fraud reports (TC40) plus disputes (TC15), divided by the count of settled card-not-present transactions. Because issuers file fraud reports and disputes separately, Chargeback Gurus points out that one fraud-coded chargeback can effectively count twice.

As of April 1, 2026, the U.S. "Excessive" merchant line is a 1.5% ratio with at least 1,500 fraud and dispute events in a month, down from 2.2%, according to Justt's summary of Visa's update. Visa also measures your acquirer's whole portfolio, flagging it at 0.5% and 0.7%, which is one reason processors often step in well before a merchant reaches its own threshold.

Our explainer on Visa's VAMP fraud and dispute thresholds covers the program in more depth.

Many merchants get the next rule wrong. Winning a standard representment (the formal response you submit through your processor) recovers the sale, but the dispute stays in your VAMP count. Visa's fact sheet lists only two exclusions: disputes resolved through pre-dispute solutions, and fraud reports that qualify for Compelling Evidence 3.0. Both depend on the resolution happening before Visa pulls its data. Those two tools are where automation helps your ratio, and not just your recovery rate.

Where First-Party Fraud Automation Pays Off

Chargeback automation is good at repetitive, rule-based work with deadlines attached: gathering records, matching data and submitting on time. Those are the three places to start.

Capture Evidence When the Sale Happens

The best dispute response is assembled before any dispute exists. Set your store, gateway or subscription platform to save evidence with every order. That means IP address, device identifier, the shipping and billing addresses, the email and phone used, and the customer's acceptance of your terms and renewal disclosure, with a timestamp.

Each business model needs slightly different proof. Physical goods need carrier tracking and delivery confirmation. Digital products and software need login records, download timestamps and usage logs, since there's no package to track. Subscriptions need the renewal reminder you sent and proof the customer used the service after the charge. If you keep cards on file for renewals, our glossary entry on how network tokens keep stored cards current explains how they work. If you sell on Shopify, check what your order export and fulfillment data already capture before you buy a tool to collect it. MannyPay's Shopify payment integration page covers how processing connects to your store.

Match Fraud Disputes Against Compelling Evidence 3.0

Visa launched Compelling Evidence 3.0 (CE3.0) on April 15, 2023, for reason code 10.4 disputes. Visa describes it as an optional program meant to show that a cardholder took part in card-not-present purchases they now say were fraudulent. In Visa's words, the core test is "at least two prior undisputed transactions with matching IP addresses or device IDs older than 120 days."

Dispute vendors such as Chargeflow describe the full window as more than 120 and no more than 365 days before the dispute, with at least two matching data elements. Visa has kept changing the program. Starting Oct. 17, 2025, it began qualifying transactions for CE3.0 automatically through Visa Secure, and it added a fee for successful qualifications effective April 17, 2026. Confirm current requirements and fees with your processor.

Software does this matching well because it means searching a year of order history for qualifying transactions, and a person working against a deadline will miss some. A good tool flags which incoming disputes qualify, pulls the matching orders and formats the submission. Repeat-purchase businesses gain the most, because subscriptions and consumables give the tool more history to match against. A brand-new customer's first order can't qualify, so CE3.0 does nothing for one-time buyers.

Set Rules for Pre-Dispute Alerts

Pre-dispute services tell you about a cardholder's complaint before it becomes a chargeback. Justt names Visa's Rapid Dispute Resolution (RDR) and the Cardholder Dispute Resolution Network (CDRN) among the tools whose resolved cases drop out of the VAMP dispute count. Visa also points merchants to Verifi's Order Insight, which shows issuers and cardholders purchase details before anyone files a dispute. Automation lets you set rules for these alerts, such as refunding every alert under a dollar amount you choose and sending order data on the rest.

There are two catches. Refunding through an alert still costs you the sale. And according to Chargeback Gurus, an RDR resolution removes the dispute but not the issuer's fraud report, so a fraud claim settled that way can still count once. Ask your processor which alert services it supports for each card brand and how resolved alerts show up in your reports.

What Still Needs a Human in Dispute Representment

Automation should prepare cases. A person should still make some decisions:

  • High-value disputes. Above a dollar amount you set, have someone read the file before it goes out. A missing tracking page or a wrong policy screenshot can lose a case that should have been won.
  • Real service failures. If the customer has a point (late shipment, broken product, a renewal they were never told about), refund them and fix the process. Representment is the wrong tool here.
  • Repeat-abuser decisions. Software can flag a customer whose disputes are piling up. Cancelling that customer's subscription, blocking future orders or asking for a different payment method is a business call, and a mistaken block costs you a good customer.
  • New patterns. A sudden run of disputes from one product, campaign or affiliate usually points to a problem upstream that no template will catch.

Worked Example: When a Friendly Chargeback Is Worth Fighting

Here's a simple test: break-even win rate = cost to fight one dispute ÷ amount recovered if you win. If your real win rate is below that number, fighting loses money.

Illustrative assumptions: a subscription business with a $35 monthly plan receives 12 fraud-coded disputes in a month. Staff time costs $30 an hour. A manual response takes 40 minutes. An automated response takes 5 minutes of review, and the tool charges 25% of whatever it recovers. The processor's chargeback fee is charged whether you win or lose, so it's the same in both scenarios and left out. Assume a 30% win rate either way (3.6 wins on average).

ManualAutomated
Labor per dispute$20.00$2.50
Net recovered per win$35.00$26.25
Break-even win rate57.1%9.5%
Recovered on 12 disputes (30% win)$126.00$126.00
Tool fee$0$31.50
Labor on 12 disputes$240.00$30.00
Net result−$114.00+$64.50

At these assumptions, fighting $35 disputes by hand loses money, and automating the same work turns a profit. This is the merchant-side economics PaymentsJournal described: automation makes it practical to fight disputes you'd otherwise write off. Plug in your own fees, ticket size and win rate before you decide. The table also leaves out a benefit that doesn't show up in dollars. A fraud report that qualifies for CE3.0 drops out of your VAMP ratio, while a dispute you win the ordinary way stays in.

Policy Fixes That Prevent Disputes Before They Count

Every dispute you prevent stays out of your ratio, so these fixes often matter more than anything you automate:

  1. Make your billing descriptor recognizable. The name on the cardholder's statement should match the brand they bought from, not your LLC name. Ask your processor what descriptor fields it supports, including a phone number or URL.
  2. Make cancelling easy. If a customer can't find the cancel button, they may cancel through their bank instead. Check your flow against current state law in our article on automatic renewal laws for subscription businesses, and see subscription rules that still apply after the click-to-cancel rule was vacated. This is general information, so confirm your obligations with a qualified attorney.
  3. Send receipts and renewal reminders that answer the dispute ahead of time. List the product, the brand name the customer knows, the renewal price and how to get help. Customers who can reach you quickly are less likely to call their bank.
  4. Authenticate the riskier orders. Running high-ticket or first-time orders through 3-D Secure authentication gives you a stronger record that the cardholder was there, and Visa now uses Visa Secure data to qualify transactions for CE3.0. Our glossary entry on 3DS2 and the liability shift explains the trade-off against checkout friction.

Measuring Results: Win Rates, Dispute Ratios and Cost per Dispute

Track four numbers each month and look at them together:

  • Win rate. Disputes won ÷ disputes fought. Break it out by reason code, because fraud-coded and "not as described" disputes behave very differently.
  • Dispute ratio. Calculate it the way Visa and your acquirer do, counting fraud reports and disputes, not just chargebacks you lost. Our guide on how close is too close to chargeback ratio thresholds shows how to leave yourself a buffer.
  • Cost per dispute. Chargeback fees + labor + tool fees, divided by total disputes. Automation should push this number down even if your win rate stays flat.
  • Prevention rate. The share of complaints resolved through alerts, CE3.0 or customer service before they became chargebacks.

A high win rate paired with a rising dispute ratio means you're winning cases while your account risk grows. If that's your pattern, put policy fixes and pre-dispute tools ahead of better representment. When you shop for tools, our guide to comparing chargeback management services covers pricing models and contract terms.

This week, export last quarter's disputes and tag each one as true fraud, friendly fraud or a real service failure. Then check how many fraud disputes had two earlier orders from the same customer that might have qualified for CE3.0, and run the break-even test on your average ticket. If your ratio is already close to the line, or a processor has warned you, request a free quote and a MannyPay specialist will respond within one business day. MannyPay also offers high-risk merchant accounts for businesses with elevated dispute profiles, subject to underwriting.

Sources

  1. How Automation Is Changing the Fight Against First-Party Fraud (PaymentsJournal Podcast episode page)
  2. PaymentsJournal home page (Nov. 11, 2026 listing for "How Automation Is Changing the Fight Against First-Party Fraud")
  3. FinovateFall 2025: Decisionly
  4. Visa Acquirer Monitoring Program Fact Sheet (2025)
  5. Visa: Compelling Evidence 3.0 Acquirer Readiness (March 2023)
  6. Visa Merchant Business News Digest (CE3.0 qualification through Visa Secure)
  7. Visa: Friendly Fraud Explained: Prevention and Solutions
  8. Justt: Visa VAMP Threshold April 2026: What Merchants Must Know
  9. Chargeback Gurus: Visa Acquirer Monitoring Program (VAMP)
  10. Chargeflow: Visa Compelling Evidence 3.0 (CE3.0): Rules and 2026 Changes

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading