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 merchandise not received, service not received, or a close cousin. Nothing here coaches cardholders on filing non-delivery disputes or inventing tracking stories.
A dispute lands stamped product not received, merchandise not received, or service not provided. Ops pulls the carrier page. Support remembers the customer opened a "where is my order" ticket weeks ago. Warehouse shows a scan. Finance sees the fee clock. One model already wrote a scolding letter about porch pirates and buyers who "must have gotten it." The submit button still wants a mapped narrative and attachments a reviewer can skim. That is the moment this page is for.
People searching product not received chargeback response, merchandise not received dispute rebuttal, or how merchants respond to not-received reason codes usually get generic evidence checklists. Useful starting points. This page is narrower. It treats not-received as a merchant evidence narrative: show what left your dock or unlocked for the buyer, at what address or account, with dates a stranger can verify, without treating label-created as delivered.
This is distinct from respond to a fraud claim (unauthorized / stolen-card), from friendly fraud chargeback response (first-party misuse pattern), and from credit not processed chargeback response (refund already owed). 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, ship-to address, carrier and tracking status that is actually delivery (or digital access logs), signature or photo where relevant, customer chats about arrival, refund or reship attempts, and the deadline. Default chain: Grok, then Perplexity, then ChatGPT, then Gemini, then Claude. Later labs challenge soft "it must have arrived" claims, label-created treated as delivered, 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: defending one mid-ticket not-received dispute you would otherwise accept can cover a long stretch of Plus. No win-rate promises. Evidence quality only.
Not received is a reason family, not one magic code
Issuers and processors label these cases with network-specific codes (Visa, Mastercard, Amex, and others) and console phrases like merchandise not received, service not provided, or product not received. Read the code on this case. The response still has to answer that code, not the slang in Slack.
What usually breaks not-received replies: treating label-created or "in transit" as delivered; uploading a warehouse photo with no ship-to match; arguing digital goods without login or download proof; ignoring a wrong-address ship that you cannot defend; missing the reply window while drafting outrage; mixing a fraud rant into a not-received code; claiming the buyer "must have gotten it" with no scan to the address on the order.
Hard line: legitimate merchant defense of real fulfillment only. If the goods never left, the tracking is soft, or you cannot honestly show delivery or access, refund or reship and close. Do not invent a delivery event. No coaching to deny valid non-delivery claims.
The merchant ritual before Submit on a not-received case
Read the reason code and the processor checklist. Gather what you can prove: carrier status that shows delivered to the address on the order (or a documented alternate), signature or photo where your channel uses them, digital access or download logs for services and downloads, ship confirmation emails the buyer could see, customer chats about arrival or porch issues, reship or refund offers already made, policy language on delivery windows. Restate the claim in the cardholder's words. Draft a short dispute description that maps each proof line to the not-received 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. 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-received response
Example shape: Processor PROCESSOR, reason code CODE (merchandise / service / product not received as labeled), amount AMOUNT, order ORDER_ID, ship-to ADDRESS, carrier and tracking STATUS, digital access proof LIST (if any), customer communications LIST, reship or refund attempts LIST, deadline DATE. Write my merchant product-not-received dispute description, map each paragraph to the claim on the case, and list evidence to upload versus omit. Flag soft delivery claims and label-created statuses. 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 non-delivery with no honest proof where the move is refund or reship. Save the free eligible review for mid-ticket and high-ticket cases where delivery or access proof exists but your first draft still treats label-created as delivered, or the narrative lectures the cardholder.
Related
Hub: dispute cases. Write the response: write your dispute description. CASE MAKER: win disputes. Sibling reason: 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. Pricing.
Run it before you submit the not-received response
Start now: open pingpongit.com and dump reason code, claim, delivery or access inventory, 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 non-delivery coaching.