Chargeback from a client: real dispute or fake notification?

A real dispute is handled only inside your payment processor dashboard (opened manually). Emails alone can be fake.

I see a dispute in the dashboard Client threatened a chargeback Email says “dispute opened”

Stop. Answer this first

Fail-fast classification

  • Do you see an open dispute inside your processor dashboard? (Stripe/PayPal/etc, opened manually)
  • Which processor is this actually in? (Stripe vs PayPal dispute vs card vs “bank transfer”)
  • Is this “notification” only in email/SMS with a link? (no dashboard case)
  • Did you already issue a refund (full or partial)?
  • Was it card-not-present (online) or card-present?
  • Is it subscription/recurring or one-time?

If you can’t confirm a dashboard dispute, don’t treat it as Route A.

Routes A/B/C (pick the one that matches reality)

Hard rule

  • Don’t refund outside the dispute flow until you’ve checked the dispute status in the dashboard.
  • If you can’t see the dispute in the dashboard, don’t act on email claims.

Evidence to collect (10 seconds)

If Route A (dashboard dispute):

  • Case ID + dispute reason/category + deadline (screenshot)
  • Invoice/receipt ID, amount, date, customer identity in your records
  • Delivery/access proof you already have (links/files/logs)

If Route C (email-only notification):

  • Sender address + domain (screenshot)
  • Subject line + timestamp
  • Link domain (copy/hover only — don’t open)
  • Any “case number” shown in the email (as text)

Route A — dispute exists in dashboard (real case: deadlines + evidence pack)

  • Open the dispute in the dashboard (typed/bookmarked login).
  • The only date that matters is the dashboard deadline.
  • If it’s digital/service: pause delivery or revoke access if allowed, to avoid “delivered after dispute” mess.
  • Choose one clean action: submit evidence pack OR follow processor guidance to refund (if recommended).
  • Respond once, cleanly. Don’t drip-feed evidence across 20 messages.
  • Even here: don’t trust the email itself — trust the dashboard case.

Route B — client threatens chargeback (no case yet) (pre-dispute: reduce risk, document, don’t panic)

  • Ask for the specific reason in writing (what exactly is disputed).
  • Offer one resolution option in writing (fix OR refund policy path).
  • Don’t refund impulsively just because they used pressure words.
  • If they threaten chargeback as leverage: keep it factual, offer one option in writing, then stop debating.
  • Keep everything written. Avoid phone-only negotiation.

Route C — message claims a dispute, but nothing in dashboard (fake notification / phishing)

  • Default: treat as phishing until proven otherwise.
  • Do not click links. Do not login via email buttons.
  • Log in manually to your processor dashboard and search for disputes.
  • If you see unknown access alerts → secure accounts immediately (see Damage control).
  • If this is a “bank/payment email” angle, use Bank email: scam or real?

Common panic mistake: refunding based on a scary email. Correct move: dashboard → status → processor-guided action.

Evidence pack format (recommended)

  • One PDF, 3–7 pages total.
  • One short timeline (ordered → delivered → support attempts).
  • One dispute statement (clear, factual, 5–7 sentences).
  • Attach only what supports the dispute reason (no random dumps).

Evidence kits (by dispute reason)

Build a short, structured pack that matches the dispute reason. Volume doesn’t win cases — clarity does.

Fraud / “Unauthorized”

Hard truth: Unauthorized disputes are the hardest to win.

  • Invoice/receipt details: amount, date, customer name/email
  • Proof of customer interaction: messages, onboarding, account activity
  • Delivery proof (digital): access logs, download logs, login timestamps
  • Matching signals you have: AVS/CVC results, 3DS/SCA evidence, device/location consistency (if available)
  • Your policy acceptance (terms/refund policy shown/accepted)

If you don’t have strong proof (3DS/AVS/CVC/logs), refund may be cheaper than fighting — follow processor guidance.

Not received
  • Tracking/delivery confirmation (physical) OR access/delivery logs (digital/service)
  • Client messages acknowledging receipt/progress
  • Timeline: ordered → delivered → follow-ups
  • Support/resolution attempts you made
Not as described / service dispute
  • Contract / scope / proposal accepted
  • Milestones delivered (files, links, commits) + dates
  • Client approvals or “OK” messages
  • Revision policy and what was included
  • Resolution attempt: fixes offered + client response
Subscription / “Canceled but charged”
  • Subscription terms: renewal cadence + cancellation rules
  • Cancellation state: whether/when canceled, what the user did (if you have logs)
  • Billing timeline: last successful charge → renewal attempt → notices (if any)
  • Usage after the charge (if applicable)
  • Refund policy and pro-rating offer (if any)
Mini dispute statement template (copy-ready) 
Dispute statement (short)

1) This charge relates to: [service/product] for [customer], invoice/receipt #[ID].
2) Date and amount: [date], [amount], processed via [processor].
3) What was delivered: [one sentence]. Delivery date/time: [timestamp].
4) Evidence: [tracking/access logs/meeting record/files sent] (attached).
5) Customer communication: [brief summary + date], showing acknowledgment or scope agreement.
6) Our policy: [refund/cancellation/returns], available at: [policy location] / accepted at checkout/onboarding.
7) Requested outcome: uphold the charge (or follow processor guidance if refund is recommended).

Timeline & fees (what to expect)

  • The only date that matters is the dashboard deadline.
  • Deadlines vary by processor and dispute reason — always follow the dashboard date.
  • Funds may be withdrawn/held while the case is reviewed.
  • Many processors charge a dispute/chargeback fee (rules vary).
  • Resolution often takes weeks; sometimes months.

Damage control (if this smells like fraud or compromise)

This is not about “finishing the process.” This is about limiting damage.

  • Secure your processor account: change password, enable 2FA, review login history.
  • Check payout settings: bank account, payout email, admin users/roles.
  • If you use API keys/webhooks: rotate keys and review recent changes.
  • Stop fulfillment for the disputed order if high risk and allowed by policy.
  • If you haven’t yet, scroll up to Evidence to collect.

Risk → actions (not just labels)

Low

Administrative / “didn’t recognize”

  • Check descriptor clarity + invoice details.
  • Follow processor guidance: refund vs evidence depends on amount + relationship.
Medium

Service/delivery disagreement

  • Submit a structured evidence pack + short dispute statement.
  • Avoid chat arguments; keep written, factual records.
High

Abuse pattern / leverage / suspected fraud

  • Assume abuse: tighten terms, stop service, require upfront for future work.
  • Secure your accounts and review payout/admin settings.

FAQ

How do I know if a chargeback is real?

A real dispute appears in your processor dashboard. Don’t trust email links — open the dashboard manually and confirm the case exists.

Client says “I will chargeback.” Is that already a chargeback?

No. That’s a threat (Route B) until you see an open dispute in the dashboard (Route A).

What if this is PayPal, not Stripe?

The principle is the same: verify inside the correct dashboard (PayPal Resolution Center / Stripe disputes) opened manually, not via email links.

Should I refund immediately?

Not automatically. First check the dispute status. If a dispute is open, follow your processor’s recommended action (refund vs submit evidence).

What’s the biggest mistake here?

Refunding or logging in via an email link. Confirm in-dashboard first.

How long do disputes take?

Often weeks; sometimes months. The response deadline is much shorter and varies by processor/reason.

Will I pay a fee?

Many processors charge a dispute/chargeback fee. The rules vary — check your dashboard policy.

What evidence wins most often?

Clear delivery/use proof + scope agreement + a short timeline, formatted cleanly.

Does arguing with the client help?

Usually no. Keep communication minimal, written, and factual.

What if it’s “not received” but it’s a service?

Use access logs, delivery timestamps, meeting records, and any client acknowledgment.

What if it’s subscription “canceled but charged”?

Show renewal terms, cancellation state, billing timeline, and usage evidence after charge (if applicable).

When should I worry about account compromise?

If there’s no dashboard case but you received a “dispute opened” message, or you see unknown logins/payout changes. Secure the account immediately.

Official resources

ClearExplained — simple pages that remove panic and reduce mistakes.