A friendly fraud chargeback happens when a real customer disputes a legitimate charge they made themselves, and tells their bank it was fraudulent or unauthorized. Stripe puts it this way: "the customer initiates the transaction but later claims that the charge was fraudulent or unauthorized." The order was placed, paid and delivered. The dispute still arrives as fraud, and you have to prove the buyer was your customer.
That is why these disputes can be won. With true fraud, a stranger used a stolen card and there is little to argue. With friendly fraud, your store holds a trail that links this purchase to the same person: the device, the IP address, the account, the email, earlier orders that went through without a problem.
Why customers file them
Stripe lists the common reasons in its guide to friendly fraud:
- Forgetfulness: they forget the purchase or don't recognize the charge on their statement.
- Misunderstandings about your terms, cancellation or return policy.
- Unauthorized use of their card or account, disputed as fraud instead of reported to their card company.
- Impulse buying, then regretting the purchase.
Some of these are fixable before they become disputes. A billing descriptor the customer recognizes and a refund policy shown before checkout both remove a reason to call the bank.
How to tell friendly fraud from true fraud
On Stripe, a fraud claim on an online card order usually shows as the Fraudulent category, and on Visa as reason code 10.4, "Other Fraud, Card Absent Environment." The reason code alone won't tell you who filed it. The order history will. Look for:
- An earlier order from the same customer, on the same card, that was never disputed.
- The same IP address or device at checkout as on past orders.
- A customer account that logged in before and after the purchase.
- Delivery to the shipping address the customer has used before.
- Downloads or usage after the purchase, for digital products.
If none of that exists (a new account, an unfamiliar device, a rush shipment to a new address), you may be looking at true fraud, and accepting the dispute can cost less than fighting it.
The evidence that wins
Stripe's reason code guidelines set out what to send for each category. For a friendly fraud claim, the strongest packet ties the buyer to the purchase:
- The order and receipt, with the product description.
- Checkout details: customer IP address, email, billing and shipping address.
- Card checks Stripe recorded: AVS, CVC and 3D Secure results.
- Proof of delivery, or proof of download, login or use.
- Every message you've had with the customer about the order.
- The policies the customer agreed to at checkout.
Stripe also recommends contacting the customer, because it "might give you insight to better understand the complaint," and keeping a record of all communication to submit with your response.
Visa Compelling Evidence 3.0
Visa Compelling Evidence 3.0 (CE 3.0) exists for exactly this case. Stripe's CE 3.0 documentation says it lets businesses "demonstrate a non-fraudulent history with cardholders to fight friendly fraud." A dispute qualifies when:
- It is a Visa transaction with network reason code 10.4.
- There are at least two earlier transactions on the same payment method that weren't disputed.
- Those transactions are within 120 to 364 days of the disputed one, and are paid, undisputed and not validation charges.
- The disputed transaction and both earlier ones match on two main evidence elements, or one main and one secondary.
The main elements are the customer purchase IP, the customer device fingerprint or device ID, and the customer account ID. The secondary elements are the shipping address and the customer email address. Device fingerprint plus device ID doesn't count as a valid pair.
When Stripe sees an eligible dispute, it tries to fill in the evidence from your earlier transactions. Stripe notes that all those past transactions must have been processed through Stripe. It also advises filling in the standard evidence too, which is used if the CE 3.0 submission is turned down.
Respond once, and on time
You usually have 7 to 21 days to respond, depending on the card network, and a missed deadline loses the dispute automatically. Stripe's response guide is clear that you have "only one opportunity to submit your response." You can't add files afterwards. Keep the combined evidence files under 4.5 MB, and leave out links, audio and video, since banks won't review outside content.
Counting the cost helps you decide which to fight. Stripe takes the disputed amount and a dispute fee from your balance when the dispute opens. If you counter, a dispute countered fee applies too, which Stripe returns if you win. Unless your Stripe contract says otherwise, the dispute received fee is never returned.
Where WooCommerce stores lose these
Stripe sees the payment. It doesn't see what happened in your store around it: the customer's logins, the device they used, the downloads, the order notes. That evidence sits in WooCommerce, and for friendly fraud it is the part that wins.
DisputeGuard's WooCommerce plugin syncs orders and the activity around them as they happen: the customer's IP address and user agent at checkout, a device ID, terms acceptance, and login history. When a dispute arrives, it also gathers the customer's prior undisputed orders for Visa CE 3.0. For card-absent fraud disputes, DisputeGuard looks for the same customer's prior undisputed transactions by device, IP and account, and each packet is scored with a list of the recommended evidence that's missing before anything is sent to Stripe.
If friendly fraud is costing you money, start free with DisputeGuard and connect Stripe and your store, so the next dispute arrives with its evidence already gathered.