Not legal or financial advice. Network rules, processor contracts, and retention requirements change. Confirm every requirement with your acquirer and counsel. Merchant-side only: basic hygiene for dispute ops. Does not coach cardholders. No invented win-rate percentages.
Compliance asks for retention periods. Ops asks which fields must exist before Submit. Someone pasted a Visa PDF into Slack and called it the policy. Chargeback compliance basics are concrete: who owns the console, what you store, how long you keep it, and which reason codes require which evidence objects.
Long legal primers bury the desk checklist. This page lists ownership, retention, evidence hygiene, and routes into policy, retention, and CASE MAKER letterhead.
Start here: chargeback policy for merchants, dispute evidence retention, win disputes, chargeback ops runbook. Also: chargeback evidence checklist, pays for itself, API for agents. 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.
Hygiene items desks miss
- Console ownership. Named owner and backup for each processor. Runbook: chargeback ops runbook.
- Retention window. How long evidence packs and logs stay available. Retention: dispute evidence retention.
- Written accept and fight bars. Policy: chargeback policy for merchants. Accept: when to accept a chargeback.
- No invented proof. Agents and humans share the same stop rule. Agentic: agentic dispute ops.
Hard line: defend real sales only. Do not invent evidence to fill a compliance checkbox. Do not deny valid unauthorized-use claims. Do not coach consumers.
Minimum sequence
- Name owners and due-date alerts for every processor console. Notification: Stripe dispute notification.
- Write retention and storage rules for evidence packs. Retention: dispute evidence retention.
- Publish accept vs fight thresholds. Policy: chargeback policy for merchants.
- Use a checklist before Submit. Checklist: chargeback evidence checklist.
- Pressure-test borderline packs: write your dispute description, win disputes.
How Pingpong fits hygiene work
Policy docs and storage stay yours. Paste claim text, inventory, and compliance questions into Pingpong when a live case needs a pressure-test before Submit. 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. Retention notes. Soft or missing evidence listed. Current lean (fight / refund / accept). Ask: does the pack answer this reason code under our policy; 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
Counsel-owned matters, pure policy drafting weeks with no live case, and alerts that never became disputes. Use the free eligible review on live response windows where policy and proof disagree.
Related
Policy: chargeback policy for merchants. Retention: dispute evidence retention. Runbook: chargeback ops runbook. CASE MAKER: win disputes. Budgeting: chargeback budgeting. Startup playbook: chargeback playbook for startups. Hub: dispute cases. Pricing.
Name owners and retention, then defend live cases
Start now: confirm console owners and retention windows, then paste a live borderline case into pingpongit.com before the due date. Policy: chargeback policy for merchants. Retention: dispute evidence retention. Letterhead: win disputes. Runbook: chargeback ops runbook. 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.