Not legal or financial advice. This page is not a substitute for your processor dispute console, card-network reason codes, acquirer playbooks, a licensed attorney, or your judgment. It describes a merchant ritual: use Pingpong to write a dispute description when the claim is services not as described, not as described, quality, or a close cousin. Nothing here coaches cardholders on filing quality disputes or inventing listing screenshots.
A dispute lands stamped not as described or services not as described. Product pulls the listing. Support has photos of what shipped or a scope doc for the service. Ops remembers a return offer the buyer refused. One model already wrote a scolding letter about buyers who "expected magic." The submit button still wants a mapped narrative: what the listing or SOW promised, what was delivered, communications about expectations, and remedies already offered. That is the moment this page is for.
People searching services not as described chargeback response, not as described dispute rebuttal, or how merchants respond to quality / SNAD reason codes usually get generic product-description FAQ pages. Useful starting points. This page is narrower. It treats not-as-described as a merchant evidence narrative: show the description the buyer could see, the unit or service delivered, and the gap (or lack of gap) a stranger can verify, without hoping tone substitutes for the listing.
This is distinct from goods not as described chargeback response (merchandise SNAD / listing vs unit), from product not received chargeback response (delivery / access), from before you accept a damaged delivery (buyer-side pause), and from friendly fraud chargeback response (first-party misuse pattern). Compelling pack language: compelling evidence for chargebacks. 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. Buyer-side pause: before you file a chargeback.
Use Pingpong to write your dispute description. Paste the reason code, order facts, listing or SOW text and images the buyer saw, what was shipped or delivered (photos, scope completion, credentials), customer chats about expectations, return or remedy offers, policy language on descriptions and returns, and the deadline. Default chain: Grok, then Perplexity, then ChatGPT, then Gemini, then Claude. Later labs challenge soft "exactly as described" claims without the listing, missing photos of the unit shipped, and tone that lectures the cardholder. Brand: Pingpong at pingpongit.com. Not getpingpong.ai.
Definition: What is Pingpong. Mechanism: How it works. Founders: For founders.
Your first eligible web review is free. Web Plus $19.99/month, web Pro $124.99/month. iOS: three free Pingpongs, then Plus $24.99/month or Pro $59.99/month. Start free on pingpongit.com. Full table: pricing.
Pays-for-itself framing: clarifying one mid-ticket not-as-described dispute (listing matched delivery, or honest remedy already due) can cover a long stretch of Plus. No win-rate promises. Evidence quality only.
Not as described is a promise-versus-delivery social object
The cardholder story is usually: what I got is not what you sold. Your story has to be an honest shape: listing or SOW matched what shipped or performed (show both side by side); a disclosed condition or limitation the buyer saw (show the disclosure); a remedy already offered under policy (show the offer and response); or a real mismatch where the honest move is refund, replace, or redo. Network codes and processor labels vary (not as described, services not as described, quality, counterfeit-shaped cousins). Read the code on this case.
What usually breaks SNAD replies: uploading a catalog hero image instead of the listing the buyer saw; arguing quality without photos of the unit shipped or a completion checklist for services; ignoring chats where you promised a different SKU; mixing a fraud rant into a description code; missing the reply window while drafting outrage; tone that lectures the cardholder about expectations.
Hard line: legitimate merchant defense only. If the listing or SOW did not match what you delivered, remedy and close. Do not invent listing screenshots. No coaching to deny valid description mismatches.
The merchant ritual before Submit on a not-as-described case
Read the reason code and the processor checklist. Gather what you can prove: archived listing or SOW the buyer saw (text, images, specs), what was shipped or performed (photos, serials, completion notes, access logs), customer chats about expectations, return or remake offers, policy language on descriptions and returns. Restate the claim in the cardholder's words. Draft a short dispute description that maps each proof line to the description claim. Run Pingpong on the draft plus the evidence inventory. Edit. Upload. Submit before the deadline.
Compelling pack language: compelling evidence for chargebacks. Network maps: Visa chargeback reason codes, Mastercard chargeback reason codes. Sibling reasons: product not received chargeback response, canceled recurring transaction chargeback response, duplicate processing chargeback response. Broader first response: respond to a chargeback. Related irreversible-submit habit: Catch AI mistakes before you commit.
How the five-model handoff works on a not-as-described response
Example shape: Processor PROCESSOR, reason code CODE (not as described / services not as described / quality as labeled), amount AMOUNT, order ORDER_ID, listing or SOW TEXT, delivery proof LIST, customer communications LIST, remedy offers LIST, deadline DATE. Write my merchant services-not-as-described dispute description, map each paragraph to the claim on the case, and list evidence to upload versus omit. Flag soft "exactly as described" claims without the listing the buyer saw. Do not invent proof I did not list. Do not paste full PAN, CVV, bank passwords, or government IDs you are not allowed to store.
Grok drafts. Perplexity through Claude review in sequence. You leave with a tighter description and a gap list. Architecture: Sequential vs parallel AI. Framing: AI second opinion. Debias: Debias AI.
Letterhead PDF path (and what is live today)
Today Pingpong writes and pressure-tests the dispute description and checklist you paste into your processor. The CASE MAKER lander for a letterhead evidence pack outline is win disputes: first PDF free, then $9/PDF or 5-pack $29 when export ships. One-click PDF export is not a live product button today. Do not delay a ticking case waiting for it. Start the free Pingpong now, or jump straight to write your dispute description. Assemble files in the console you already have. Existing API orientation: developer docs.
When to skip
Skip for pocket-change accepts, counsel-owned cases, and clear mismatches you already know you should remedy. Save the free eligible review for mid-ticket cases where listing and delivery match on paper but your first draft lectures the cardholder, or the description archive needs a clean map to the code.
Related
Hub: dispute cases. Write the response: write your dispute description. CASE MAKER: win disputes. Sibling reasons: goods not as described chargeback response, counterfeit merchandise chargeback response, canceled recurring transaction chargeback response, duplicate processing chargeback response, product not received chargeback response, credit not processed chargeback response. Compelling pack: compelling evidence for chargebacks. Neighbors: respond to a chargeback, friendly fraud chargeback response, dispute representment. Network maps: Visa, Mastercard. Processors: Stripe, PayPal, Shopify. Buyer-side distinct: before you file a chargeback, before you accept a damaged delivery, before you return. Pricing.
Run it before you submit the not-as-described response
Start now: open pingpongit.com and dump reason code, claim, listing archive, delivery proof, and deadline into one question. Or go straight to write your dispute description. Run Pingpong once. Keep survivors. Confirm in the processor UI. Continue on Plus or Pro if the ritual sticks (web $19.99 / $124.99; iOS $24.99 / $59.99). Or the App Store.
Again: not legal or financial advice. Merchant-side defense and evidence quality only. No consumer quality-dispute coaching.