Friendly Fraud Chargebacks Are Won on Evidence You Collected Before the Order Shipped

November 2, 2026 - RiskRampart

A friendly fraud chargeback, first party misuse in the card networks' current language, arrives as a claim that the goods never came, or the order was never placed, from the person who placed and received it. Some share of those claims are genuine confusion: a partner's purchase, a statement descriptor nobody recognises, a delivery left with a neighbour. The rest are deliberate. The merchant's problem is that the dispute process cannot tell the difference, and does not try very hard. It weighs evidence, and the merchant who can produce the right evidence, in the format the issuer expects, inside a short deadline, wins cases that feel unwinnable in the support inbox.

The evidence that actually moves an issuer

A tracking number alone is weak. What carries weight is a chain: delivery scan at the customer's address, ideally with carrier photo or geolocation, matched to an order placed from a device and IP the account has used before, with pre purchase contact from the same email, and a post delivery account login or product activation. Each link is ordinary data. Together they make the never received and never ordered stories hard to sustain. Assemble that chain as a template long before disputes arrive, because the representment window is measured in days and the data lives in five systems owned by four teams.

Descriptor and communication prevent the honest half

A large slice of first party claims start as confusion, and confusion is cheap to prevent. A statement descriptor that matches the store name the customer knows, a confirmation email that shows that descriptor in its first lines, and delivery notifications that name the carrier and the address, all cut the I do not recognise this charge disputes that were never fraud at all. Post purchase clarity is fraud tooling. Merchants who treat it as marketing copy discover, in dispute data, that their clever holding company descriptor has been generating chargebacks with the regularity of a subscription product.

Policies decide the deliberate half earlier than you think

Generous, loosely policed returns and reship policies teach a small population that a chargeback is simply the fastest returns route, and that population shares its methods. Require returns before refunds on reship claims above a value threshold, verify identity on address change plus high value order combinations, and keep a consistent record when an account repeats a not received claim. None of that punishes a first time honest customer materially. All of it changes the arithmetic for repeat misuse, which is where the money is: in most portfolios a small minority of accounts generates a large share of first party disputes.

Measure win rate by reason code, not in aggregate

Dispute outcomes differ sharply by reason code and issuer, and an aggregate win rate hides where evidence work pays. Track representment win rate, evidence completeness, and time to submit, split by the claim type: not received, not as described, cancelled recurring, unrecognised. The fixes differ by cell: delivery chain work for the first, product page and sizing accuracy for the second, cancellation flow clarity for the third. Teams that run one undifferentiated chargeback process spend the same effort on cases their evidence cannot win as on cases it already should, and conclude the system is rigged. Parts of it are merely specific.

Keep reading

Frequently asked questions

What is friendly fraud?

Now often called first party misuse: a chargeback filed by the genuine cardholder claiming an order was unauthorised or not received, when it was placed and delivered, whether from confusion or deliberately.

What evidence helps win a not received dispute?

A chain linking the order to the customer and the delivery: carrier delivery scan at the address, device and account history, order confirmations, and any post delivery account activity or product use.

Can clear billing descriptors reduce chargebacks?

Yes. Many unrecognised charge disputes come from descriptors customers cannot match to the store. Showing the descriptor in confirmation emails prevents a large share of confusion based claims.