Not legal or financial advice. "Compelling evidence" is network and processor language that changes in live docs. This page is a merchant packing guide, not Visa Compelling Evidence 3.0 official text, not Mastercard's dispute manuals, and not a substitute for your console, acquirer playbook, or counsel. Merchant defense only. It does not coach cardholders on filing chargebacks.
A dispute reviewer opens your case with a reason code and a clock. Soft evidence is a social failure mode: label-created screenshots, catalog hero photos, internal Slack notes the buyer never saw, and a polite letter that argues the wrong story. Compelling evidence is the opposite social object. It is a pack a stranger can skim that answers the claim with files and narrative that actually fit the code.
Use Pingpong to assemble that pack. Paste the reason code, order facts, evidence inventory, and deadline. Default chain: Grok, then Perplexity, then ChatGPT, then Gemini, then Claude. Later labs pressure-test soft claims and missing files. Brand: Pingpong at pingpongit.com. Not getpingpong.ai.
Primary writing ritual: write your dispute description. CASE MAKER letterhead PDF path (first PDF free, then $9/PDF or 5-pack $29 when export ships): win disputes. Hub: dispute cases. Network maps: Visa chargeback reason codes, Mastercard chargeback reason codes.
First eligible web review free. Web Plus $19.99/month, Pro $124.99/month. iOS three free, Plus $24.99, Pro $59.99. Start on pingpongit.com. Pricing. No invented win-rate percentages on this page.
What merchants mean by compelling evidence (and what they do not)
Operators say "compelling evidence" when they mean: delivery or access proof that shows receipt, not intent to ship; listing and unit photos that match what the shopper bought; cancel or refund paths the customer could see with timestamps; authorization notes when the code cares about fraud; prior customer history that is real, not invented biometrics; a short narrative that maps each attachment to the claim.
What is not compelling: "we always ship on time" without scans; AVS match stated as identity proof for every fraud code; a refund essay when the credit already posted and you should show the credit; attacking the cardholder; uploading a zip of camera rolls with no evidence index; waiting for a perfect PDF while the reply window closes.
Visa Compelling Evidence programs and Mastercard dispute rules name specific document types for specific codes. Your processor (Stripe, Braintree, Square, Adyen, Shopify Payments, PayPal) paraphrases those rules in their UI. Always confirm the live checklist on the notice. This page teaches the packing habit, not a frozen statute.
Hard line: legitimate defense of real sales only. If the sale was wrong, refund and close. Do not run fiction through the chain.
How to assemble a pack before Submit
Read the reason code and the cardholder claim in their words. Build an evidence inventory: what you have, what status it actually proves, what the buyer saw. Draft a dispute description that answers the claim without insulting anyone. Index attachments so a reviewer can quote them. Run Pingpong on the draft plus the inventory. Ask: list what is compelling for this code, what is soft, and what to omit. Edit. Upload. Submit on time.
Letterhead shape (company logo, case header, narrative, evidence index, then files) is how many operators submit. Outline that pack on win disputes. Write the prose on write your dispute description. Related habit: Catch AI mistakes before you commit.
Soft claims sequential models usually catch
Tracking that stops at label-created. Product-as-described packs that only show catalog images. Cancel fights without a customer-facing cancel path. Fraud replies that only restate AVS/CVV. Credit-not-processed cases that never show the credit entry. Digital goods without login or usage logs. Subscription renewals after cancel emails that never reached the customer. Duplicate processing answered with a quality rant.
One chatbot grading its own dispute letter rarely catches that pattern. Five labs in sequence, each forced to look at the prior answer, are a different ritual. Framing: AI second opinion. Debias: Debias AI. Architecture: Sequential vs parallel AI.
Paste shape for Pingpong
Processor or network NAME. Dispute ID. Reason code and exact notice text. Amount. Order ID and date. Product or service. Cardholder claim. Evidence inventory with status (not just file names). Policy language the customer could see. Deadline. Ask: write my merchant dispute description, map attachments to compelling evidence for this code, flag soft claims, and list what to omit before Submit. Do not paste full PAN, CVV, bank passwords, or government IDs you are not allowed to store.
Grok drafts. Perplexity through Claude pressure-test. You edit into live console fields. For letterhead PDF outline when export ships (first free, then $9): win disputes.
When to skip
Skip pocket-change accepts, counsel-owned cases, and clear fraud with no compelling evidence where the honest move is accept. Save the free eligible review for mid-ticket and high-ticket cases where your first draft still confuses soft screenshots with a pack a reviewer can trust.
Related
Hub: dispute cases. Write the response: write your dispute description. CASE MAKER: win disputes. Network maps: Visa chargeback reason codes, Mastercard chargeback reason codes. Processors: Stripe, Braintree, Square, Adyen, PayPal, Shopify. Neighbors: respond to a chargeback, product not received chargeback response, credit not processed chargeback response, dispute representment. Buyer-side: before you file a chargeback. Pricing. Also: misrepresentation chargeback response, cancelled merchandise chargeback response, cardholder dispute addendum. Also: chargeback evidence checklist, chargeback response deadline, how to respond to a Stripe dispute, Stripe dispute fee, chargeback win rate myths, AI chargeback response, Compelling Evidence 3.0, Stripe Radar and disputes, chargeback threshold monitoring. Also: merchant representment letter, chargeback rebuttal letter, partial dispute response. Network response: Visa dispute response, Mastercard dispute response, representment best practices. Also: Visa Compelling Evidence checklistAlso: Visa Compelling Evidence checklist, Mastercard compelling evidence, chargeback evidence timeline.
Build the pack now
Open the free eligible review on pingpongit.com. Paste the reason code and evidence inventory. Ask Pingpong to write the merchant description and mark soft versus compelling attachments. Keep what survives five labs. Submit on time. Continue on Plus or Pro when the chain earns a seat. Or the App Store.
Again: not legal or financial advice. A compelling pack is how operators submit organized evidence. It is not a win guarantee and not a substitute for live network rules. Merchant defense only.