Friendly Fraud: The Merchant's Guide to Prevention & Recovery

What Is Friendly Fraud?

Friendly fraud — also called first-party fraud or chargeback fraud — occurs when a legitimate cardholder disputes a transaction they actually made. The word "friendly" is a misnomer: the fraud is perpetrated using the cardholder's own account and card, making it harder to detect and challenge. For merchants, it is one of the most expensive problems in e-commerce.

Friendly fraud can be intentional or unintentional. Intentional friendly fraud means the cardholder knowingly files a false dispute to obtain both the goods and a refund — effectively stealing from the merchant. Unintentional friendly fraud occurs when a cardholder disputes a legitimate charge because they didn't recognise the billing descriptor, forgot about a subscription, misunderstood a return policy, or assumed a family member's purchase was fraudulent.

Both types result in a chargeback that must be contested with evidence. Both count against the merchant's chargeback ratio. And both require the merchant to actively defend the transaction rather than passively accept the loss.

The Scale of the Problem

Industry research consistently shows that 60–80% of all chargebacks are friendly fraud cases. For global e-commerce merchants, this represents tens of billions of dollars in annual losses — money lost not to criminal hackers using stolen cards, but to customers who made genuine purchases and then disputed them.

The pandemic accelerated the trend. As online purchasing surged from 2020 onwards, so did friendly fraud rates. Research from Aite-Novarica found that 23% of consumers who filed chargebacks had actually received the goods or services they disputed. A separate survey found that 40% of consumers who successfully obtained a chargeback through friendly fraud repeated the behaviour within 60 days.

For subscription businesses, the problem is even more acute. Recurring billing creates a persistent target: customers can dispute any charge, at any renewal interval, and claim they cancelled or never authorised the subscription. Without meticulous renewal communication and documented consent records, many of these disputes are difficult to win.

The structural cause is the chargeback system itself. Designed to protect consumers, it places the burden of proof on merchants. The issuing bank's default assumption favours the cardholder, and the evidence requirements that would satisfy a court don't always satisfy a chargeback analyst working through a high-volume queue. Merchants who understand this dynamic — and build their defence accordingly — win far more disputes than those who simply submit generic evidence packages.

Common Types of Friendly Fraud

Friendly fraud occurs in recognisable patterns. Understanding these patterns helps merchants build targeted prevention and detection strategies.

"I Never Received It"

The cardholder claims goods were never delivered despite successful delivery. Common with high-value items shipped to forwarding or parcel-locker addresses, shipments without signature confirmation, and digital products with no physical delivery proof. The merchant has delivery data; the customer disputes it. This is the most common dispute reason code and, with proper documentation, one of the most winnable.

"I Didn't Authorise This"

The cardholder claims the transaction was fraudulent despite having made the purchase. Common in shared-device households (children purchasing on parents' accounts), with impulse purchases later regretted, or when a cardholder simply wants an easy refund without going through customer service. Because these disputes are filed under fraud reason codes, they're harder to challenge — but device fingerprint, IP data, and purchase history can establish authorisation.

Subscription Amnesia

The customer disputes a recurring charge, claiming they cancelled or never authorised the subscription. This category is disproportionately common in SaaS, streaming, and box subscription businesses. Sometimes genuine (the customer intended to cancel but didn't complete the process); often intentional (disputing rather than cancelling is easier). Prevention through renewal reminders and one-click cancellation flows is more effective than response for this category.

"Not as Described"

The customer claims the product or service differed materially from what was advertised. Legitimate in some cases; abused in others — particularly for digital products, custom orders, or services that can't be "returned." Detailed product specifications, confirmation emails showing what was ordered, and any pre-purchase communication are the key evidence elements.

Post-Event Remorse

Particularly common with travel bookings, event tickets, and professional services — the customer disputes a charge after the travel dates pass, the event occurs, or the service is rendered. The cardholder's goal is to recover a payment for something they used. These are winnable with service delivery records, but require careful evidence construction.

How to Detect Friendly Fraud

Distinguishing intentional friendly fraud from genuine disputes requires examining behavioural and transactional signals. No single indicator is definitive, but patterns emerge.

Signals that suggest intentional friendly fraud:

• The customer's stated reason (e.g., "never received") directly contradicts delivery confirmation data you hold
• The dispute was filed immediately after a failed refund request or a contentious customer service interaction
• The disputed item was high-value and easily resaleable (electronics, gift cards, luxury goods)
• The customer has multiple prior orders to the same address, some of which have also resulted in disputes
• The account was created shortly before the disputed transaction with no purchase history
• The order shipped to a freight forwarder or reshipping address

Signals that suggest an unintentional dispute:

• The customer has a long history of legitimate orders with no prior disputes
• The billing descriptor doesn't clearly match your brand name
• The transaction occurred 45–120 days before the dispute (forgotten purchase)
• The product was a subscription with no recent renewal reminder sent
• The disputed amount is very small (convenience disputes are less common for low-value transactions)

This distinction matters for two reasons. First, it shapes your response strategy — intentional fraud may require a more aggressive evidentiary response, while unintentional disputes may settle with better evidence of delivery or authorisation. Second, it informs prevention: intentional fraudsters should be blocked from future purchases; customers who disputed accidentally can be retained with improved communication.

Building Your Evidence Package

The evidence package is the heart of your representment. It must be specific to the reason code, organised for a reviewer who will spend less than two minutes on your case, and connected explicitly to the cardholder's specific allegation. Generic evidence — an order confirmation with no delivery proof, a tracking number with no confirmation of delivery — rarely succeeds.

For goods not received disputes:

• Full order confirmation with line items, shipping address, and timestamp
• Carrier tracking number and delivery confirmation record from the carrier
• Signature confirmation record if available and if the address supports it
• For digital goods: IP address of purchase, device fingerprint, account creation record, post-purchase login timestamps, download history, or feature usage logs
• Any customer communication acknowledging receipt, asking follow-up questions about the order, or interacting with the product/service after delivery

For not as described disputes:

• Screenshot or PDF of the exact product listing at time of purchase, including photos and specifications
• Order confirmation showing precisely what was purchased
• Any pre-purchase communication where the customer asked about product specifications
• Evidence that the item shipped matched the listing — packing list, photos of packaged item if available
• Post-delivery communication if the customer contacted support about the product

For unauthorised transaction disputes:

• IP address of the purchase geographically consistent with the cardholder's location and prior purchase history
• Device fingerprint matching prior authenticated sessions on the same account
• AVS (address verification) match confirmation from your payment processor
• Full purchase history from the same card and account, demonstrating an established pattern
• 3DS2 authentication record if used (eci code and authentication value) — this alone can win the dispute
• Post-purchase interactions: delivery communications, support tickets, product reviews, login activity

The rebuttal letter should be structured and concise. Lead with a clear summary of why the chargeback should be reversed: "The merchandise was delivered to the cardholder's address on [date] as confirmed by carrier record (Exhibit A). The disputed transaction was authorised." Then present exhibits in order, numbered and labelled. Explicitly connect each exhibit to the specific allegation.

Winning the Dispute: Response Strategy

The core of a successful friendly fraud response is systematically disproving the specific claim — not providing general information about how your business operates. The cardholder alleged something specific. Your evidence needs to address that specific allegation directly.

Use reason code terminology. Card network analysts are looking for specific language in merchant responses. Phrases like "the merchandise was received by the cardholder," "the transaction was authorised by the legitimate cardholder," or "the service was rendered as agreed" carry technical weight because they directly map to the dispute categories the analyst is evaluating.

Respond as early in the window as possible. Response windows range from 7 to 45 days depending on the network and reason code. Filing early signals an organised, confident response and leaves time for your acquirer to request clarification if needed. Waiting until the last day is high-risk.

Know your win rates by reason code. Not all dispute types are equally winnable. Fraud-coded disputes (Visa 10.4, MC 4840) without 3DS authentication are significantly harder to win than "goods not received" or "not as described" disputes with full delivery documentation. Understanding your win rates by code identifies where to focus response investment — and where prevention is the better lever.

Track outcomes systematically. Merchants who win more disputes over time are those who treat each case as data — what evidence worked, what didn't, which reason codes are most common, which have the highest win rates. This analysis directly informs both response quality and prevention priorities.

Prevention: Stopping Friendly Fraud Before It Starts

The most effective defence against friendly fraud is ensuring customers have no plausible basis for disputing legitimate transactions. Prevention eliminates both the reversed revenue and the chargeback fee — making it substantially more cost-efficient than response alone.

Fix your billing descriptor. The single most impactful prevention measure, and the easiest to implement. If your bank statement shows your holding company name or a payment processor prefix ("SQ *", "PYMT*") instead of your brand name, customers won't recognise the charge. Update to your exact brand name, ideally with a support phone number in the supplementary descriptor field.

Send delivery confirmations proactively. A "your order has been delivered" notification timed to carrier confirmation removes the "I never got it" foundation before it can be used. For subscription businesses, renewal reminders sent 7 days before each charge — with the amount, date, and a cancellation link — prevent the majority of "I forgot I was subscribed" disputes.

Use signature confirmation for high-value orders. The cost ($3–5 per shipment) is trivial compared to the chargeback fee plus lost goods on a $150+ order. Signature confirmation creates an irrefutable delivery record that eliminates the "never received" argument entirely.

Make cancellation genuinely easy. Requiring a phone call to cancel a subscription, or burying the cancellation option under multiple settings screens, doesn't retain customers — it generates chargebacks. A one-click cancellation flow prevents more disputes than any response strategy can recover.

Keep detailed interaction records. Every support ticket, chat log, and email exchange is potential future evidence. If a customer who later disputes a transaction previously acknowledged receipt in a support email, or asked follow-up questions that imply they used the product, that correspondence becomes your strongest exhibit.

When Friendly Fraud Becomes Serial Abuse

Some customers dispute systematically and repeatedly across multiple merchants. These are not occasional misunderstandings — they are calculated exploitation of the chargeback mechanism. The 40% repeat rate within 60 days documented in industry research suggests a meaningful subset of friendly fraud is habitual behaviour.

Merchants cannot see a customer's dispute history at other merchants — that information belongs to the issuing bank. However, some dispute alert and prevention services (including Verifi's Order Insight and Ethoca's Consumer Clarity) share signals across merchant networks, giving early warning of cardholder disputes before they become formal chargebacks. These tools allow proactive refunds that prevent the chargeback fee and ratio impact.

For confirmed serial fraudsters — customers who dispute repeatedly across multiple transactions from the same account — blocking the card number, email, device fingerprint, and shipping address prevents future exposure. This should be calibrated carefully: shared billing addresses (apartment buildings, office parks) and employer-issued devices can create false positives. The goal is to block the specific customer, not their building.

At scale, managing serial fraud patterns, calibrating evidence packages by reason code, and maintaining win rate analytics requires operational discipline that most in-house teams struggle to sustain. Professional chargeback management — through software or an outsourced service — provides this infrastructure systematically, allowing merchants to focus on revenue generation while disputes are handled by specialists.