Merchant dispute ritual

Chargeback ops runbook

Not legal or financial advice. Processor consoles and internal tools change. Confirm every step against your live console. Merchant-side only. Does not coach cardholders. No invented win-rate percentages.

New hire opens Stripe. Due date is tomorrow. The wiki has a 40-page deck and no click path. An ops runbook is the short path: open notice, inventory evidence, decide fight or refund, write, Submit, log outcome.

Playbooks lecture. Runbooks sequence clicks and owners. Pair with merchant dispute workflow and chargeback team roles.

Start here: merchant dispute workflow, chargeback team roles, win disputes, write your dispute description. Also: chargeback ops runbook, Stripe dispute notification, pays for itself, chargeback SLA for merchants. Hub: dispute cases.

One case rescued from a soft pack, or closed before a fee-only fight, often covers a long stretch of Plus and evidence PDFs. Fee framing: pays for itself. No fake guarantees.

Pingpong lives at pingpongit.com (not getpingpong.ai). First eligible web review free. Web Plus $19.99/month, Pro $124.99/month. iOS three free, Plus $24.99, Pro $59.99. Open pingpongit.com. Pricing.

Runbook steps

  1. Open the notice. Copy ID, reason, amount, due date. Stripe first hour: Stripe dispute notification.
  2. Inventory evidence. Checklist: chargeback evidence checklist.
  3. Fee-aware fight or refund. Fee: chargeback fee vs fighting. Accept: when to accept a chargeback.
  4. Write and pressure-test. Write: write your dispute description. Letterhead: win disputes.
  5. Upload and Submit. Upload: Stripe dispute evidence upload. Submit: submit chargeback evidence.
  6. Log outcome. Won: Stripe dispute won next steps. Lost: Stripe dispute lost next steps.

Hard line: defend real sales only. Do not invent proof to finish a runbook step. Do not deny valid unauthorized-use claims. Do not coach consumers.

Owners and clocks

Name who runs each step and the internal SLA before the network due date. Roles: chargeback team roles. SLA: chargeback SLA for merchants. Queue: dispute queue management.

How Pingpong fits the runbook

The console stays the submit system. Paste claim text and inventory into Pingpong at the write step when the pack is borderline. Letterhead: win disputes. Agents: API for agents, dispute evidence API.

Paste this shape

Processor NAME. Dispute ID. Reason or category. Amount. Fee already charged AMOUNT. Console due date DATE. Evidence inventory. Soft or missing evidence listed. Current lean (fight / refund / accept). Ask: does the pack answer this reason code; draft a dispute description only if the pack holds; list what must not be invented. Do not invent proof. Do not paste full PAN, CVV, bank passwords, or government IDs you are not allowed to store.

When not to spend a review

Small accepts already decided, counsel-owned matters, and alerts that never became disputes. Use the free eligible review when the runbook reaches the write step on a borderline pack.

Related

Workflow: merchant dispute workflow. Roles: chargeback team roles. CASE MAKER: win disputes. Write: write your dispute description. SLA: chargeback SLA for merchants. Startup playbook: chargeback playbook for startups. Hub: dispute cases. Pricing.

Follow the click path, then write once

Start now: open a live notice, run the inventory and fee decision, then paste into pingpongit.com before Submit. Workflow: merchant dispute workflow. Letterhead: win disputes. Write: write your dispute description. Roles: chargeback team roles. Continue on Plus when the ritual sticks. Or the App Store.

Again: not legal or financial advice. Merchant-side defense and evidence quality only. No consumer dispute coaching. No fake win rates.