A strange kind of fraud
There is a category of chargeback that confuses merchants more than any other: the dispute filed by a customer who genuinely made the purchase. No stolen card, no criminal ring, no breach. The real account holder bought the thing, received the thing, and then told their bank they didn't recognize the charge or never authorized it. The industry calls this friendly fraud or first-party misuse, and despite the cozy name it is one of the largest sources of disputes a typical merchant faces.
What makes it worth understanding is that most of it isn't villainy. Some friendly fraud is calculated theft dressed up as a complaint, yes. But a great deal of it flows from ordinary human psychology — the way memory, friction, and moral reasoning interact at the moment someone scans a credit-card statement. Understanding those mechanisms won't stop every dispute, but it explains why they happen and, crucially, points at the ones you can both prevent and contest.
The recognition gap
Start with the most mundane cause. People do not remember their purchases as well as they think they do, and credit-card statements are designed to defeat recognition. A line item reads as a cryptic billing descriptor, an unfamiliar parent-company name, a date that doesn't match when the customer remembers buying anything. Cognitive science is blunt about this: recognition memory depends on cues, and a statement strips away nearly every cue that was present at the moment of purchase. No product image, no shopping context, no brand styling — just a string of characters and a number.
So a customer in good faith looks at "LMNLABS* SVC 04/12" and genuinely does not recognize it. The honest response to an unrecognized charge is to dispute it. From the bank's seat this looks identical to fraud; from the customer's seat it is fraud, because as far as they can reconstruct, they never bought this. The recognition gap turns a satisfied customer into a disputant through no malice at all — which is also why merchants who tighten their billing descriptor to match the brand the customer actually saw watch this category shrink.
Moral disengagement and the distance of a tap
The deliberate end of friendly fraud is more interesting, and it runs on a well-studied mechanism that psychologists call moral disengagement — the set of mental moves people use to do something against their own ethics without feeling like a bad person. Disputing a charge is almost engineered to invite it.
Consider the distance involved. The customer never faces you. They tap a button in a banking app, and an institution they'll never meet pulls money from a company they picture as faceless. Every element that normally restrains us — eye contact, social consequence, the discomfort of confronting a real person — is absent. The act is reframed: not I am taking back money for a product I used, but I am reporting a problem to my bank. The bank's own language helps, asking clinically whether the customer "recognizes" or "authorized" the charge, never whether they are being fair. Diffusion of responsibility does the rest; the customer feels they're flagging an issue, and whatever happens next is the system's decision, not their theft.
This is the same psychology that lets otherwise honest people pad an expense report or keep a cashier's mistaken extra change. The behavior isn't a stable trait of "dishonest customers." It's a situation that lowers the moral cost of a small dishonest act until plenty of ordinarily honest people step over the line.
The friction asymmetry
There is a third mechanism, and it is the one merchants have the most power over: the relative effort of disputing versus asking. Behavioral economists talk about friction — the small costs and frustrations that determine which path a person actually takes, often more powerfully than the rewards at the end of each path.
For a frustrated customer, two doors lead to a refund. One is your support process: find the contact link, write an email, wait for a reply, possibly negotiate. The other is the dispute button in their banking app, which is one tap and returns the money fast. When asking you is harder than going around you, a meaningful share of customers who would happily have accepted a refund choose the chargeback instead — not because they wanted to harm you, but because it was the path of least resistance. The chargeback is more expensive for you, carries a fee, and damages your dispute ratio, but the customer never sees that cost. They only feel their own friction.
This asymmetry is why hard-to-find cancellation flows and slow support reliably generate disputes. You are, without meaning to, making the destructive door the easy one.
Why most of it is winnable
Here is the redemptive part. Because friendly fraud is committed by the genuine account holder, it leaves the account holder's fingerprints all over the transaction. The same person who disputed the charge logged in from their usual device, shipped to their verified billing address, and — very often — made earlier purchases from you that they never disputed. The card networks have begun to formalize exactly this: Visa's Compelling Evidence framework lets a merchant rebut a fraud claim by showing a history of prior, undisputed transactions tied to the same customer identifiers. The trail that friendly fraud leaves is the trail that defeats it.
That's the practical payoff of understanding the psychology. True criminal fraud is hard to contest because a stranger really did use the card. Friendly fraud is contestable precisely because the disputer is the legitimate customer, and their own history contradicts their claim. The merchant who recognizes a dispute as first-party misuse — and assembles the device, address, and purchase-history evidence to prove it — is fighting the most winnable category there is.
Reducing it and contesting it
The two responses reinforce each other. On the prevention side: make your billing descriptor unmistakably match your brand, send purchase confirmations that customers will recognize later, and make asking you for a refund easier than disputing — because every customer who chooses your support door instead of the bank's button is a chargeback that never happens. On the contest side: when a friendly-fraud dispute does land, gather the identity and history evidence that ties the purchase back to the person now claiming they never made it.
You will not eliminate friendly fraud, because you cannot eliminate the gaps in human memory or the moral distance of a tap. But you can stop feeding it, and you can fight the instances that are winnable — which is most of them.
Where Argeback fits
Argeback is designed for the reality that "fraudulent" disputes are usually friendly fraud, not stolen cards. When a fraud-coded dispute lands in your Stripe inbox, it asks the targeted questions that surface the account-history and identity evidence those cases turn on — the matching address, the prior undisputed orders, the trail the genuine customer left — rather than treating every fraud claim as hopeless. It packages that evidence and files it via Stripe before the deadline. And by sorting disputes by reason code over time, it shows you which patterns keep recurring, so you can fix the descriptor or the cancellation flow that's manufacturing them upstream. The bank decides each case. Argeback makes sure the winnable ones actually get fought.