Friendly fraud is now the majority of chargebacks. Chargebacks911 has put first-party misuse as high as 61% of chargebacks, and Visa estimates it can reach 75% of cardholder disputes. For high-risk merchants, this is the top threat to VAMP ratios and processing accounts.
It is a relationship-collapse problem, not a chargeback problem. Fix billing descriptors, cancellation paths, and post-transaction communication before spending on chargeback tools.
3DS2 shifts fraud liability, but only for fraud. When authentication succeeds, fraud chargebacks move to the issuing bank. It does not protect against service disputes or “item not as described” claims.
Intercept disputes before they post, surgically. RDR and Ethoca stop disputes before they become chargebacks, but since April 2026 Visa counts RDR refunds in the VAMP ratio, so use targeted thresholds, not a blanket refund policy.
Friendly fraud now accounts for the majority of chargebacks. Chargebacks911’s research has pegged first-party misuse as high as 61% of all chargebacks, and Visa estimates it can reach 75% of cardholder disputes. Not stolen cards. Not account takeover. Not organized crime. Your own customers, filing chargebacks on transactions they authorized.
For high-risk merchants, this is not background noise. It is the primary threat to your VAMP ratio, the reserve your acquirer holds against you, and ultimately your processing account. The conventional response, fighting chargebacks one by one after they land, is both expensive and strategically wrong.
The merchants who actually solve this problem reframe it first. Friendly fraud is not a chargeback problem. It is a relationship collapse problem. By the time a customer files a dispute, three things have already gone wrong. The chargeback is just the invoice for those failures.
The Friendly Fraud Surge Is Not What You Think
The term “friendly fraud” creates a mental model problem. It sounds soft. The reality: first-party misuse jumped from roughly 15% of reported fraud in 2023 to 36% of all reported fraud in 2024, and it is accelerating. Global chargeback volume is projected to reach 324 million transactions by 2028, and the total cost of chargebacks is climbing toward $41.69 billion by 2028.
What is driving it? Primarily convenience and low perceived risk. Filing a dispute through a bank app takes ninety seconds. There is no penalty for cardholders who abuse the process. Refund policies at many merchants are deliberately friction-heavy, which pushes dissatisfied customers directly to their bank instead of to your support team.
For high-risk merchants, add one more factor: stigma. A customer who buys from an adult platform, a dating site, or an online casino often does not want the charge appearing on their statement. When it does, disputing it feels easier than explaining it.
Why High-Risk Merchants Are the Hardest Hit
Friendly fraud is painful for every merchant. For high-risk operators, it is existential, because the consequences do not stop at the chargeback fee.
Visa’s VAMP ratio combines fraud and disputes into a single metric, with the “excessive” threshold at 1.5% for merchants. Mastercard’s SMMP flags any merchant that looks like a scam pattern, and friendly fraud chargebacks produce exactly the data signature Mastercard is hunting for. Every disputed transaction you lose counts against both programs.
The compounding problem: high-risk merchants typically have a customer population with higher dispute propensity by definition. Subscription products get forgotten. Adult purchases get hidden. Crypto-adjacent transactions get second-guessed. You are not competing on a level playing field for dispute rates. That means your prevention systems need to be better than average, not merely equal to it.
The Three Failure Points Before a Dispute Is Filed
Most friendly fraud prevention advice focuses on representment: gathering evidence and fighting the chargeback after it lands. That is necessary, but it is downstream of where the real problem lives. The dispute was preventable at three earlier moments.
Billing descriptor failure. A customer who does not recognize the charge on their statement calls their bank, not you. Your billing descriptor is often the first communication a customer receives after purchase, and it needs to be unambiguous. Many high-risk merchants operate under a different legal entity or processor name. The customer bought from “DatingPro Premium” and the charge appears as “MCE SOLUTIONS DUBLIN.” That is a guaranteed dispute. Fix this with your processor before anything else. Use the full brand name plus a recognizable URL or support phone number in the descriptor field.
Cancellation path obstruction. If a customer cannot cancel quickly and clearly, they will cancel via chargeback. This sounds obvious, but many subscription merchants bury their cancellation flow deliberately, which backfires catastrophically in high-risk verticals. Every day a customer tries to cancel and fails is another day they build a case that the charge was unauthorized. Your cancellation should be one click from the account dashboard with an immediate confirmation email.
Post-transaction silence. The window between purchase and potential dispute is where relationships are built or abandoned. A purchase confirmation email, a receipt that matches the descriptor, a reminder three days before a subscription renews, a “here is how to pause or cancel” message sent proactively before the first renewal. These are not just customer experience details. They are dispute prevention signals. They are also documented evidence if you end up fighting a chargeback.
3DS2 and the Liability Shift: What It Covers and What It Misses
3D Secure 2 (3DS2) is the single most powerful tool available to card-not-present merchants for eliminating fraud chargebacks. Only about 32% of merchants currently use it. For high-risk operators, that adoption gap is both a vulnerability and an opportunity.
When a transaction completes a successful 3DS2 authentication, liability for fraud chargebacks shifts from you to the issuing bank. The cardholder still has recourse, but the card network assigns financial responsibility to the issuer. Issuers are far less willing to grant fraud chargebacks on authenticated transactions because they take the loss.
The critical limitation: 3DS2 protects against fraud disputes. It does not protect against service-related disputes, non-delivery claims, or “item not as described” chargebacks. Friendly fraud often gets filed under these categories precisely because cardholders have learned that fraud reason codes trigger the fastest refund. A 3DS-authenticated transaction does not give you immunity from a customer who simply wants their money back.
The conversion tradeoff is real but manageable. Frictionless authentication (which 3DS2 enables for low-risk transactions based on issuer risk scoring) passes through without any customer-facing step, preserving conversion. Friction only appears for genuinely high-risk sessions. For high-risk merchants, the friction is worth accepting on a higher proportion of transactions because the chargeback cost so dramatically exceeds the friction cost.
RDR, CDRN, and the Dispute Interception Layer
Even with 3DS2 deployed and pre-dispute communication optimized, some chargebacks will still land. The next layer is automated dispute interception before the chargeback is formally filed.
Visa’s Rapid Dispute Resolution (RDR) program, operated through Verifi, allows merchants to configure automatic refund rules. When an issuer initiates a pre-dispute inquiry that matches your rules, the refund is processed automatically and the dispute closes before it ever becomes a chargeback on your VAMP tally. A refund costs you the sale. A chargeback costs you the sale plus the fee plus the ratio impact.
Mastercard’s Collaboration Network (Ethoca) operates on similar logic. You integrate, set your refund threshold rules, and disputes below the threshold resolve automatically.
April 2026: RDR Refunds Now Count Toward VAMP
The blanket-refund loophole is closed. Visa updated VAMP in April 2026 to count transactions resolved through RDR toward your overall fraud rate. Using RDR as a blanket “refund everything” strategy to suppress chargeback counts no longer works. Set targeted refund thresholds for specific reason codes rather than auto-approving all pre-dispute inquiries.
Your 30-Day Action Checklist
Not everything requires a developer sprint. Some of this you can fix this week.
- Within 48 hours: audit your billing descriptor. Log into your bank’s app and look at the charge as a customer would see it. If it does not match your brand name, contact your processor and request a descriptor update. This is often a same-week fix.
- Within one week: fix your cancellation flow. Time how long it takes a new user to cancel without any assistance. More than two minutes or more than three clicks means it is too long. Fix it before the next billing cycle.
- Within two weeks: set up pre-renewal notifications. Email subscribers three to five days before each billing date with a direct cancellation link. This single change has produced measurable dispute rate reductions across multiple subscription merchant case studies.
- Within 30 days: implement 3DS2 and dispute interception. Deploy 3DS2 on your highest-chargeback product lines first. Integrate with Verifi (RDR) or Ethoca and configure targeted refund thresholds for your most common dispute reason codes.
The goal is not zero chargebacks. The goal is a dispute rate that keeps you below VAMP thresholds, keeps your acquirer comfortable, and keeps your processing account viable for the next three to five years. Friendly fraud is solvable. It just has to be solved upstream, not in the chargeback queue.
- Chargebacks911, “Chargeback Stats: Key Dispute Data for 2026,” chargebacks911.com.
- Chargeflow, “Chargeback Statistics 2026: Trends, Costs & Solutions,” chargeflow.io.
- Beacon Payments, “Visa & Mastercard Chargeback Rule Changes 2025-2026,” beaconpayments.com.
- Chargebacks911, “Evaluating the Effectiveness of 3D Secure in Chargeback Prevention,” chargebacks911.com.
