← Blog

Playbook 4 min read

PayPal disputes & chargebacks: win the cases — and stop getting them

A chargeback is the most expensive way to lose an argument with a customer: you lose the goods, the money, a dispute fee on top — and every case counts toward a ratio that can eventually threaten your payment account. Yet most merchants treat disputes as random weather. They aren’t. The majority are predictable, and a large share are preventable.

Know the three dispute machines

  • PayPal buyer protection. Two claim types matter: item not received and significantly not as described. PayPal decides internally, on evidence both sides upload, within fixed deadlines — and charges the merchant a dispute fee on lost cases.
  • Card chargebacks. The customer calls their bank, the bank pulls the money back through the card network. Works even underneath PayPal or Klarna — a card-funded PayPal payment can come back as a chargeback after you’ve already won the PayPal case. Fees typically run €15–40 per case.
  • BNPL disputes (Klarna & co.). The provider pauses the merchant payout while the customer disputes — low friction for the customer, immediate cash-flow impact for you.

The shared logic: whoever documents better, wins. And: every dispute — won or lost — costs you fee, time and ratio. The card networks start formal monitoring programs at dispute ratios below one percent; a small shop with a bad month can get there faster than it sounds.

Why chargebacks actually happen

Genuine stolen-card fraud is the minority. Industry analyses consistently attribute the bulk to what’s called friendly fraud — and most of it decodes as ordinary situations that escalated:

  1. “Where is my order?” with no answer. The customer wrote, waited, wrote again — then asked their bank instead. A dispute is the support ticket you didn’t answer in time.
  2. The refund felt too slow or too hard. If your returns process is opaque, the bank’s one-click process wins.
  3. Unrecognized statement descriptor. The card statement says a company name that isn’t your shop name → “I don’t know this charge.”
  4. Family purchases. The classic “my kid ordered this.”
  5. Actual fraud. A real but small remainder.

Note that 1–3 are process problems on the merchant side. That’s the optimistic read: they’re fixable.

Winning the cases worth fighting

When a dispute lands, you’re in an evidence game with deadlines (PayPal typically gives you about ten days to respond — a missed deadline is an automatic loss). Your evidence pack, assembled per case:

  • Tracking with delivery confirmation to the address from the payment system — for PayPal seller protection this is a hard condition: ship to the registered address, keep the proof. Signature confirmation above value thresholds.
  • The full communication history — timestamps showing you responded, offered solutions, and the customer’s own statements (“arrived, but I don’t like it” kills an item not received claim).
  • Order metadata — device, login, prior orders by the same customer.
  • Your policy texts as accepted at checkout.

Then do the math before fighting: item value versus fee plus your time plus ratio impact. Below roughly €25–40, a proactive refund is usually the cheaper outcome even when you’d win — with one exception: documented repeat abusers, where folding trains the behavior.

Preventing them — the higher-leverage half

  1. Answer fast, especially shipping questions. The single biggest lever. A customer who gets a real tracking answer in minutes has no reason to involve a bank (how to automate exactly that).
  2. Proactive delay notices. The “item not received” dispute is usually a stuck parcel plus silence — catch the stuck parcel first (the lost-parcel process).
  3. Make refunds boring. A clean self-service return path with refund-on-first-scan beats the bank’s process on speed — and a refund you execute is a dispute that never existed (the legal baseline).
  4. Fix your descriptor. Statement text = shop name customers recognize. Two minutes in your PSP dashboard, measurable dispute reduction.
  5. Track disputes per customer and per SKU. Repeat disputers get signature shipping or prepayment; a SKU with a dispute cluster has a listing problem, not a customer problem.

The operational angle

Everything above is casework: pull the tracking, assemble the communication log, check the address match, apply the value rule, either refund or file the evidence pack — inside a deadline. It’s mechanical, deadline-driven and expensive to do by hand, which is why it’s usually done late or not at all. A resolution system that already holds the order, tracking and full case history can assemble the evidence pack the moment a dispute arrives — and prevent most of them by answering the original question in minutes. The live demo shows that on a real case from your store.

What can we help with?

How many support tickets a month?

What powers your store?

Great — who should we reply to?

Last step — a bit about your store.

Free & no obligation · reply within one business day

Thanks — message received.

We’ll get back within one business day. Want to talk sooner?