Friendly Fraud (First-Party Fraud / Chargeback Fraud)

Friendly fraud occurs when a legitimate cardholder initiates a chargeback on a valid transaction without justification. The cardholder (or someone authorized to use their card) receives goods or services, then disputes the charge through their issuing bank. This differs from third-party fraud, where stolen credentials are used without the cardholder's knowledge.

‍

‍

‍

The Challenge: Why Friendly Fraud Matters

‍

Friendly fraud represents a persistent challenge in merchant risk management for several reasons:

‍

• Burden of proof shifts to the merchant. Card schemes and issuing banks typically side with the cardholder by default. Merchants must provide evidence (delivery confirmation, IP logs, signed receipts) to defend against disputes. Without clear documentation, the chargeback stands.

‍

• It masquerades as legitimate customer behavior. The transaction appears normal: AVS (Address Verification System) and CVV (Card Verification Value) checks pass, device fingerprints match prior activity, and no fraud signals trigger. Only after fulfillment does the cardholder dispute the charge.

‍

• Intent is difficult to prove. Some cardholders genuinely forget a purchase or fail to recognize a billing descriptor. Others deliberately abuse the chargeback process to obtain refunds while retaining merchandise. Distinguishing intentional abuse from honest confusion requires evidence that many merchants lack.

‍

• Chargeback ratios erode portfolio health. Acquirers and payment facilitators (PayFacs) managing merchant portfolios face regulatory consequences when chargeback rates exceed scheme thresholds (typically 0.9% for Visa and 1.0% for Mastercard). High rates trigger monitoring programs such as Visa's Fraud Monitoring Program (VFMP) or the Excessive Chargeback Program (ECP), which impose fines and operational requirements. Unchecked friendly fraud can push an entire portfolio into a high-risk category.

‍

• It creates operational overhead. Representment (the process of contesting a chargeback) requires dedicated resources: pulling transaction records, compiling evidence, responding within tight deadlines (often 7 to 10 days), and managing correspondence with issuing banks. For acquirers onboarding or monitoring hundreds of merchants, this scales into significant cost.

‍

‍

‍

How to Mitigate Friendly Fraud: Five Control Points

‍

We recommend building defenses across prevention, detection, and response:

‍

‍

1. Use clear, recognizable billing descriptors

‍

Cardholders dispute charges they do not recognize. Ensure the merchant name on statements matches what customers expect. Avoid generic descriptors or parent company names unfamiliar to cardholders. Test descriptors by reviewing them from a customer's perspective.

‍

‍

2. Collect and retain strong transaction evidence

‍

Capture data that can substantiate a legitimate transaction during merchant onboarding and throughout the transaction lifecycle:

• Delivery confirmation: Signature, tracking number, delivery timestamp.
• Digital goods: IP address, device ID, login timestamp, download or usage logs.
• Customer communication: Email confirmations, chat transcripts, support tickets showing the cardholder acknowledged the purchase.

‍

Store this evidence in a format accessible during representment. Acquirers and processors should ensure merchants in their portfolios have technical capability to log and retrieve this data.

‍

‍

3. Monitor for repeat offenders

‍

Track chargeback patterns by cardholder. A customer who files multiple disputes across different merchants may be abusing the process. Share intelligence across the portfolio. Some acquirers maintain internal blocklists or flagging systems for cardholders with suspicious dispute histories. Card schemes also offer tools such as Ethoca and Verifi (CDRN), which allow merchants to refund disputed transactions before they escalate to formal chargebacks.

‍

4. Implement pre-dispute alerts and collaboration networks

‍

Ethoca Alerts and Verifi's Cardholder Dispute Resolution Network (CDRN) provide early notification when a cardholder contacts their issuer. Merchants can issue refunds before the dispute becomes a chargeback, avoiding ratio inflation and fees. Acquirers should encourage or require merchants to integrate these tools, particularly for high-ticket or subscription-based businesses.

‍

‍

5. Invest in representment workflows

‍

Contesting chargebacks is resource-intensive, but often successful when evidence is strong. Build processes to:

• Triage disputes by likelihood of winning (based on reason code and available evidence).
• Automate evidence compilation where possible.
• Track win rates by reason code and merchant to identify training opportunities or policy gaps.

‍

For acquirers, this may mean offering representment services or partnering with third-party dispute management platforms. For merchant monitoring teams, it means flagging merchants with low win rates or inadequate evidence retention as higher risk.

‍

‍

‍

Real-World Scenario: Digital Subscription Service

‍

A customer subscribes to a SaaS (Software as a Service) tool for $99 per month. After six months of active usage (login logs confirm daily access), the customer disputes all six charges as "unauthorized transactions". The issuing bank initiates six chargebacks totaling $594.

‍

The merchant provides:

• IP address consistency across logins.
• Email confirmation of subscription signup with customer's verified address.
• Usage logs showing feature access on dates corresponding to each charge.
• Terms of service agreement accepted at signup, including billing terms.

‍

The merchant successfully represents four of the six chargebacks. Two are upheld because the evidence submission missed the deadline. The outcome: the merchant recovers $396 but loses $198 plus chargeback fees ($15 to $100 per dispute, depending on the acquirer). The cardholder's account is flagged internally, and future transactions from that email or payment method trigger manual review.

‍

This scenario illustrates the operational cost even when representment succeeds. Multiply this across dozens of disputes per month, and the resource burden becomes clear. Acquirers managing merchant portfolios must account for this when assessing merchant quality and pricing risk.

‍

‍

‍

Strategic Impact: Why Acquirers and PayFacs Must Act

‍

Friendly fraud affects portfolio stability in three ways:

‍

1. Regulatory exposure. Card schemes impose penalties on acquirers whose portfolios exceed chargeback thresholds. A single high-risk merchant can push an entire portfolio into monitoring programs, resulting in fines, increased reserves, or even termination of scheme membership. Acquirers must identify merchants with poor fraud controls during underwriting and continuously monitor chargeback trends post-onboarding.

‍

2. Merchant attrition. Merchants burdened by chargebacks often face increased processing fees, held reserves, or account termination. When merchants lose acquiring relationships due to high chargeback ratios, acquirers lose revenue and face reputational risk if they approved merchants with inadequate controls.

‍

3. Erosion of legitimate dispute resolution. As friendly fraud increases, issuers and schemes may tighten chargeback policies, making it harder for merchants to contest even legitimate disputes. This harms the ecosystem by shifting risk disproportionately to merchants and acquirers, discouraging innovation in high-chargeback verticals such as digital goods, subscriptions, and travel.

‍

We see friendly fraud as a shared responsibility. Issuers must improve cardholder education and enforce consequences for abuse. Schemes should refine reason codes to distinguish intentional fraud from merchant error. Acquirers must hold merchants accountable for evidence retention and dispute response. Merchants must invest in systems that document transactions and communicate clearly with customers.

‍