Fraud costs you 3.6x the chargeback fee — and blocking it can cost more

What a fraudulent order actually costs

When a stolen card is used on your store, the chargeback fee is the part you can see. Everything else arrives quietly in other lines of the P&L, which is why nobody adds it up. Take a brand with an $80 average order value. A fraudulent order costs it:

• Product cost: $28 of COGS, shipped and gone. The refund to the cardholder returns the $80, not the inventory.
• Outbound shipping: $9 you paid the carrier to deliver it.
• Chargeback fee: $20 from the processor, charged win or lose.
• Dispute labor: about $12 of someone's time gathering evidence and responding.
• Unrefunded processing fee: roughly $3 you paid to take the payment that was then reversed.

That's $72 per fraudulent order, against a $20 line on the dispute notice. The fee is 28% of the real number. If you only budget for the fee, you are underestimating the loss by 3.6x, and every decision downstream inherits the error.

Scaling it to a P&L line

Per-order loss means little until it's multiplied by volume. Assume $5M in annual online revenue at that $80 AOV, which is 62,500 orders a year. A fraud and dispute rate of 0.5% of orders is about 312 incidents. At $72 each, that's roughly $22,500 a year in direct loss, of which only $6,240 shows up as chargeback fees.

Notice what $22,500 is relative to the business: on a 12% contribution margin, it erases the contribution from roughly $187,000 of revenue, about 3.7% of the year's sales. That's before the indirect costs. Card networks monitor dispute ratios, and merchants that drift toward the 1% neighborhood can land in monitoring programs with added fees, higher reserves, or in the worst case lose processing. A 0.5% rate is comfortable. A 0.9% rate after a bad quarter is not, and the relationship between your fraud rate and your processing terms is not linear.

The chargeback fee is the smallest cost of fraud. The product you shipped, the labor you spent, and the processing terms you risk are the bill.

Friendly fraud: the disputes you can win

Not every dispute is a stolen card. A meaningful share of chargebacks, in many merchant categories the majority, are customers disputing a legitimate purchase: they didn't recognize the descriptor on the statement, they couldn't find a return label, or they found it faster to call the bank than the brand. This is why fraud and returns are connected costs. A clunky returns experience quietly converts refund requests into disputes, and a dispute costs you the $20 fee, the labor, and the product on top of the refund you would have issued anyway.

The fixes here are cheap and unglamorous: a statement descriptor customers recognize, order and shipping confirmations that arrive immediately, a returns policy that is easy to find, and a support inbox that answers within a day. If your dispute reason codes skew toward "product not received" or "unrecognized," you have a communication problem, not a fraud problem, and tightening your fraud rules will not touch it.

The other side: what false declines cost

Now the part most teams miss. Every fraud rule has a false-positive rate: a legitimate customer who gets declined, flagged for manual review, or asked for extra verification and abandons. Those lost orders never appear as a loss anywhere. They show up only as a slightly lower conversion rate, which most people attribute to something else.

Price one in the same example. Contribution per good order is $34: $80 AOV, less $28 COGS, $9 shipping, $3 payment processing, and $6 for pick, pack and packaging. One false decline costs you $34 in first-order contribution, before counting the lifetime value of a customer who now bought somewhere else. A fraud order costs $72. A false decline costs $34 and up.

The break-even: when tighter rules lose money

That comparison gives you the rule of thumb. Tightening is worth it only if each fraudulent order you block costs you fewer false declines than the ratio of the two losses: $72 divided by $34, or about 2.1. Block one fraudulent order and you can afford to turn away two good customers. Any more and you're losing money on the trade.

Run it on a realistic rule change. Suppose a stricter ruleset cuts fraud by 40%, avoiding 125 incidents a year and saving $9,000. If it also declines 1% of the roughly 62,190 legitimate orders, that's about 622 lost orders at $34, or $21,150 of contribution. Net effect: roughly negative $12,000. The rule blocked 125 bad orders and cost 622 good ones, a ratio near 5 false declines per fraud prevented, against a break-even of 2.1.

The same logic runs in reverse and is why this matters for contribution margin work generally: you can only evaluate a control by its cost on both sides. A loosened rule that adds 30 fraud orders but recovers 200 good ones is a win, even though the dispute count goes up.

How to measure it properly

Most stores can't answer the false-decline question because they never log it. Build the measurement before touching a rule:

• Log every decline and review flag with the reason, then follow a sample to see whether the same customer returned and bought successfully, a strong sign of a false positive.
• Track fraud by segment, not in aggregate: new versus returning customers, first order versus fifth, shipping-address mismatch, high-value baskets. Fraud is concentrated; your rules should be too.
• Report a net fraud cost per 1,000 orders that includes fees, labor, product, and estimated lost contribution from declines. One number, trended monthly.
• Test rule changes on a holdout where possible, the same discipline as any well-run experiment program, because the fraud and false-decline effects are both noisy.

A playbook that respects both sides

Put together, the order of operations is: fix the friendly-fraud causes first because they're cheap and reduce disputes without any false-decline risk; segment your fraud so rules apply where the loss concentrates; replace hard declines with step-up verification for the gray zone, so legitimate customers get a path through; and evaluate every rule change on net contribution rather than dispute count.

A final note on incentives. Whoever owns fraud usually owns the dispute number, not the conversion number. That asymmetry guarantees over-blocking, because the cost of a false decline is invisible to the person making the call. Give the same owner both numbers, and the break-even takes care of itself.

Put a number on your own fraud cost

If you've never added up the product, labor, and lost-sale cost of your disputes, the real figure is probably several times the fees you see. It is also probably not the highest-return margin problem on your P&L, which is why it's worth pricing before you spend a quarter on it.