Somewhere tonight a parent is looking at a credit card statement, frowning at a charge they don't recognize. They didn't make it, and they're sure of that. They tap "dispute," pick "I didn't authorize this," and go to bed feeling a little safer, the way you do after locking a door. Down the hall, their twelve-year-old is asleep next to the tablet that made the purchase. Nobody in that house has lied, and you're still about to lose the money.

The industry calls this family fraud: a chargeback filed as unauthorized when the purchase was actually made by someone in the cardholder's household, usually a child, sometimes a spouse or an aging parent. It's one of the most common kinds of friendly fraud, and merchants misread it more than any other kind. They picture a con artist and build their case as if they were exposing one. But the person on the other side isn't hiding anything. They just don't know. You don't win this kind of dispute by proving someone lied. You win it by quietly showing the household what happened inside its own walls.

Why the parent is so sure

The cardholder isn't being careless with the truth. Memory isn't a recording, and psychologists have shown again and again that people reconstruct the past from what they expect to find. A parent who has never bought a game's in-app currency doesn't go looking for a memory of buying one. The charge looks foreign, and "foreign" quickly becomes "fraud."

Then it gets more personal. Sociologist Erving Goffman called it face: the public image of ourselves we work to protect. Finding out your child spent a few hundred dollars on your saved card is a small threat to face. It suggests you weren't paying attention. Disputing the charge as fraud makes the problem go away without anyone having to admit anything. Cognitive dissonance does the rest. Once someone has formally declared "I didn't authorize this," new information that contradicts the claim feels like an attack, not a correction.

This explains why merchants who answer family fraud with indignation do so badly. Every sharp email asks the cardholder to lose face, and people will pay a lot to avoid that. Often they'll pay with your money.

What the dispute actually looks like on your end

On Stripe you won't see the word "family." You'll see a fraudulent dispute, usually mapped to a card-not-present fraud reason code: Visa's 10.4 (Other Fraud, Card-Absent Environment) or Mastercard's 4837 (No Cardholder Authorization). The issuer's question is narrow. Did the cardholder, or someone acting with their access, really make this purchase, or was the card stolen?

This is where family fraud turns into a winnable case. A stolen card leaves a trail that points away from the cardholder: a new device, an unfamiliar IP, a shipping address in another state, a brand-new account. A child on the family iPad leaves a trail that points straight home. The device has bought from you before. The IP address matches the one on the cardholder's earlier purchases. The account is the cardholder's own account, logged in for months. Your evidence doesn't have to say who tapped the button. It has to show the purchase came from inside the cardholder's own digital household.

The case you're actually building

A strong family fraud response tells one story: this purchase is the same as the ones the cardholder hasn't disputed. Each piece of evidence should support that.

Device and network continuity. Put the disputed transaction's device identifier and IP address next to the ones from the cardholder's previous purchases. If they match, that's your main argument. A thief in another city doesn't share your customer's home Wi-Fi.

Account history. Show that the purchase came from an account the cardholder created and has used before, with the same login, email, and saved payment method. Include earlier transactions on that account that were never disputed. An issuer reviewer will notice that the cardholder accepted those charges and is rejecting this one.

Consistency of behavior. If the disputed purchase looks like the account's normal activity (same product category, similar amounts, the usual time of day), say so plainly. Fraud usually looks like a break from the pattern. Family fraud looks like the pattern continuing.

Visa's Compelling Evidence 3.0, where it applies. For Visa 10.4 disputes, CE 3.0 lets you point to at least two prior undisputed transactions from the same cardholder that are between 120 and 365 days old and share matching data elements with the disputed one, at least one of which must be the IP address or device ID. If you qualify, it can shift liability decisively. If you don't, the continuity argument above is still persuasive on its own terms.

Notice what's missing from that list: any claim that the cardholder is lying. Your rebuttal doesn't need one, and it reads better without one. Something like "The disputed transaction was placed from the same device and network as the cardholder's three prior undisputed purchases, using the cardholder's own logged-in account" lets the reviewer draw the obvious conclusion. Spell it out more harshly and you sound defensive. Leave it understated and you sound confident.

The conversation that saves face and the sale

In some family fraud cases you can skip the fight entirely, because the cardholder only needs a graceful way to change their mind. That depends on how you write to them.

Compare two messages. The first: "Our records show this purchase was made from your account. Filing a false chargeback is fraud." The second: "We noticed a dispute on this order and wanted to help. It was placed from the same device you've used for past purchases with us, on [date] at [time]. Sometimes a family member uses a saved card without realizing. If that's what happened, we're glad to sort it out directly."

The first message makes the parent defend the claim they already made. The second gives them a story where nobody did anything wrong, only a kid with a tablet. You're offering face instead of taking it away. Some cardholders will contact their bank to withdraw the dispute. Others won't, but you still have a written record of a reasonable, documented good-faith contact, and that belongs in your evidence too.

One caution: don't promise a refund in exchange for a withdrawal unless you mean it and can process it cleanly. A refund on top of a live dispute creates its own mess.

Your next moves

  • Open your most recent fraud dispute and pull two numbers today: the IP address and device ID on the disputed charge. Then search your records for the same values on that customer's earlier, undisputed purchases. If they match, you're probably looking at family fraud, not theft.
  • Write a one-sentence continuity statement for that case, naming the matching device, network, and account, with the dates of the prior purchases. Make it the first line of your rebuttal.
  • Save the face-saving message above as a template in your support tool, with blanks for date, time, and device, so the next time a fraud dispute arrives you send a warm note within hours instead of an angry one days later.
  • Check whether you're capturing device and IP data at checkout at all. If your logs don't keep IP addresses or device identifiers for each transaction, fix that this week. The evidence that wins these cases can't be recreated after the fact.
  • Add a small point of friction for high-value purchases on saved cards, such as re-entering a password or confirming a code sent to the account holder's email. It stops the purchase before a child can make it, which is the only family fraud defense better than winning.

Where Argeback fits

The hardest part of a family fraud case isn't the argument. It's the digging: matching device IDs across months of transactions, finding the undisputed purchases that tell the story, and writing a rebuttal that's calm instead of furious, all before the deadline closes while you're running the rest of your business. Argeback was built for that work. It pulls in your Stripe disputes, gathers the transaction history that shows a purchase came from inside the cardholder's own household, drafts an evidence-backed response, and files it from your phone before the clock runs out. If you'd like to stop losing disputes to a misunderstanding at someone's kitchen table, you can see how it works at argeback.lumenlabs.works.