PanicStation.org
UK USA
us Money & financial emergencies chargeback notification • card payment chargeback • customer disputed a card charge • buyer reversed a legitimate payment • bank reversed card payment • seller received dispute notice • merchant chargeback notice • friendly fraud chargeback • cardholder claims unauthorised • customer says item not received • customer says not as described • funds held by payment processor • chargeback fee charged • disputed credit card transaction • payment processor dispute alert • sudden payment reversal • legitimate sale being disputed • customer claims refund expected

What to do if…
you get a “chargeback” notification and you think someone is trying to reverse a legitimate payment

Short answer

Move fast and stay organized: confirm the notice is real inside your processor/acquirer dashboard, note the reason and deadline, then either accept it quickly or submit a short evidence packet that directly answers the stated reason.

Do not do these things

  • Don’t miss the response deadline — many disputes are lost automatically if you don’t respond in time.
  • Don’t click login links from the email if you’re unsure; open your processor dashboard via your usual bookmark/app instead.
  • Don’t try to “handle it” only by arguing with the customer; chargebacks must be handled through your processor/acquirer workflow.
  • Don’t upload a giant document dump; irrelevant or unreadable evidence can sink your case.
  • Don’t threaten, harass, or publicly accuse the customer.
  • Don’t refund “just in case” and also submit a dispute unless your processor says that’s appropriate for the stage you’re in.

What to do now

  1. Verify the notification is genuine and capture the key details.
    • Log in through your normal route and open the dispute in the dashboard.
    • Write down the reason code/category, deadline, amount/fees, transaction ID, and the current stage.
  2. Pick your path: accept vs challenge (before spending hours collecting docs).
    • Accept if you can’t directly disprove the stated reason (e.g., no delivery proof for “not received”).
    • Challenge if you can clearly answer the reason with specific evidence.
  3. Build a clean, reason-matched evidence packet (keep it short and legible). Examples:
    • Fraud / “unauthorized”: proof the cardholder participated or benefited (account history, IP/device data you already lawfully hold, prior successful transactions, proof of digital access/usage, shipping to a consistent address).
    • Not received: carrier tracking, delivery confirmation, ship date, address, delivery communications.
    • Not as described / refund expected: what the customer saw at purchase (listing/description), proof of what was delivered, refund/cancellation terms shown and accepted, customer communications, and any refund record/timestamp if relevant.
    • Always include: order/invoice, date/time, amount, item/service details, and a simple timeline.
  4. Write a short rebuttal summary that “maps” evidence to the reason.
    • 1–2 sentences stating you’re disputing it.
    • 3–6 bullets linking each key attachment to what it proves.
    • A brief timeline (purchase → fulfillment/access → any customer contact → today).
  5. Submit through your processor/acquirer portal by the deadline and save proof.
    • Save the submission confirmation and a copy of exactly what you uploaded.
  6. Check for spillover risk (10 minutes):
    • Look for additional disputes tied to the same email/address/device/product.
    • In your payment dashboard, review recent admin/staff logins and any payout/bank-detail changes (chargeback emails are a common phishing hook).
  7. If you suspect broader fraud or cyber-enabled crime (optional):
    • Report cyber-enabled crime to the FBI’s Internet Crime Complaint Center (IC3).
    • Report fraud/scams patterns to the Federal Trade Commission (FTC).
  8. If your provider offers an “early warning” alert, treat it as urgent (only if it applies to your platform).
    • Some providers offer alerts before a chargeback fully lands (for example, PayPal “pre-chargeback alerts”).
    • If you see one, follow the platform’s instructions immediately—time windows can be short and vary by provider.

What can wait

  • You don’t need to decide today whether to pursue legal action, collections, or major policy changes.
  • You don’t need a long argument with the customer right now — the processor’s deadline and evidence rules come first.
  • You don’t need perfect evidence; you need relevant evidence that directly answers the dispute reason.

Important reassurance

A chargeback notice can feel like an accusation, but it’s often just the bank dispute process. Many legitimate businesses receive them. The most helpful first response is calm, deadline-focused, and evidence-led.

Scope note

This covers first steps to stabilise the situation and avoid irreversible mistakes. If chargebacks are frequent or high-value, you may need specialist help from your merchant services provider or a qualified adviser.

Important note

This is general information, not legal or financial advice. Chargeback rules, deadlines, and acceptable evidence vary by card network, issuer, processor, and dispute category. Follow the instructions shown in your specific case.

Additional Resources
Support us