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 shape a dispute description and a letterhead addendum (supplemental evidence pack) when the processor or network allows additional documentation after the first reply, or when your first pack needs a clean index. Nothing here coaches cardholders on filing disputes or inventing addendum stories.
A case is open. You already submitted a first narrative, or the console asks for more. Ops has new tracking, a late refund ID, or a clearer disclosure archive. Support has a chat that arrived after the first upload. One model already wrote a second angry letter that restates the first. The submit button still wants a mapped addendum: what is new, what it answers, and how it indexes to the claim without burying the examiner in unlabeled screenshots. That is the moment this page is for.
People searching cardholder dispute addendum, merchant supplemental evidence, or how to attach an addendum to a chargeback response usually land on generic "upload more files" FAQs. Useful starting points. This page is narrower. It treats the addendum as a CASE MAKER social object: a short letterhead pack that restates the claim, lists what is new versus already filed, and maps each exhibit to the reason code, shaped with Pingpong before you paste or upload.
This is distinct from reason-code pages such as goods not as described chargeback response or cancelled merchandise chargeback response (those answer a specific stamp). It is also distinct from dispute representment (second presentment when you have something new at the network stage) and from pre-arbitration chargeback response. Compelling pack language: compelling evidence for chargebacks. Primary writing ritual: write your dispute description. CASE MAKER letterhead PDF path (first PDF free; Plus $19.99/mo includes 5 PDFs; extras $12 or 10-pack $99; Pro 25/mo; form live on win-disputes): win disputes. Hub: dispute cases. Buyer-side pause: before you file a chargeback.
Use Pingpong to write your dispute description and outline the addendum. Paste the reason code, what you already filed, what is new (tracking, refund ID, disclosure archive, chat), how each new item answers the claim, processor field limits, and the deadline. Default chain: Grok, then Perplexity, then ChatGPT, then Gemini, then Claude. Later labs challenge soft "see attached" dumps without an index, restating the first letter without new proof, 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: one clean mid-ticket addendum that surfaces a real refund ID or delivery artifact you almost left out can cover a long stretch of Plus versus fees and lost revenue. No win-rate promises. Evidence quality only.
An addendum is a supplemental index, not a second rant
The cardholder story is already on the case. Your addendum job is usually: answer a follow-up from the issuer or processor; attach proof that arrived after the first upload; or replace a messy first pack with a letterhead index the examiner can scan. Honest shapes: new tracking or access logs mapped to not-received; new refund or cancel IDs mapped to credit or cancel claims; disclosure archives mapped to misrepresentation or SNAD; or a clear "nothing new, accept" when proof is still soft. Processor labels vary (addendum, supplemental documentation, additional evidence, follow-up). Read what your console allows and the deadline on this case.
What usually breaks addenda: uploading the same PDF twice with a new filename; writing a longer lecture without new exhibits; omitting an index so the examiner cannot find the refund ID; mixing representment language into a first-cycle addendum; missing the reply window while waiting for a perfect design; tone that attacks the cardholder instead of mapping proof.
Hard line: legitimate merchant defense only. If the addendum window exists because you owe a credit you already confirmed, credit and close. Do not invent supplemental proof. No coaching to pad empty addenda.
The merchant ritual before you file an addendum
Read the console instructions and what you already submitted. List what is new versus already filed. Gather only exhibits that answer the claim: new timestamps, IDs, archives, chats. Draft a short addendum narrative (claim restated, what is new, exhibit index). Run Pingpong on the draft plus the inventory. Generate a letterhead pack on win disputes when a clean PDF helps. Edit. Upload into the fields your processor provides. Submit before the deadline.
Compelling pack language: compelling evidence for chargebacks. Network maps: Visa chargeback reason codes, Mastercard chargeback reason codes. Reason siblings when the stamp is specific: misrepresentation chargeback response, cancelled merchandise chargeback response, merchandise returned chargeback response, product not received chargeback response. Later-stage cousins: dispute representment, pre-arbitration 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 an addendum
Example shape: Processor PROCESSOR, reason code CODE, amount AMOUNT, dispute ID ID, already filed SUMMARY, new evidence LIST, how each item answers the claim TEXT, deadline DATE. Write my merchant cardholder-dispute addendum narrative and exhibit index for CASE MAKER, map each new item to the claim, and list what to omit as duplicate. Flag soft restatements with no new proof. 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 addendum 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 the addendum outline you paste into your processor. The CASE MAKER lander for a letterhead evidence pack is win disputes: first PDF free, then Plus $19.99/mo includes 5 evidence PDFs (extras $12 or 10-pack $99; Pro $124.99/mo includes 25). The form on win-disputes generates the PDF now, which is often the cleanest vehicle for an indexed addendum. Do not delay a ticking case waiting on polish. 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. Agent API landers (live): API for agents, dispute evidence API (POST /api/dispute-evidence-pdf).
When to skip
Skip for pocket-change accepts, counsel-owned cases, empty "see prior" uploads with no new exhibits, and network-stage fights that belong on dispute representment or pre-arbitration chargeback response. Save the free eligible review for mid-ticket cases where new proof exists but your first draft is a second rant, or the console asked for more and you need a clean index.
Related
Hub: dispute cases. Write the response: write your dispute description. CASE MAKER: win disputes. Reason siblings: misrepresentation chargeback response, cancelled merchandise chargeback response, merchandise returned chargeback response, quality dispute chargeback response. Compelling pack: compelling evidence for chargebacks. Later-stage: dispute representment, pre-arbitration chargeback response. Neighbors: respond to a chargeback, chargeback fees and representment. Network maps: Visa, Mastercard. Processors: Stripe, PayPal, Shopify. Buyer-side distinct: before you file a chargeback. Agent APIs: API for agents, dispute evidence API. Pricing.
Run it before you upload the addendum
Start now: open pingpongit.com and dump reason code, what you already filed, what is new, and deadline into one question. Or go straight to write your dispute description, then generate a letterhead pack on win disputes. 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 dispute-addendum coaching.