Not legal or financial advice. This lander is for merchants and agent builders assembling legitimate defense packets. It is not a substitute for Stripe docs, card-network reason-code guides, your acquirer playbook, a licensed attorney, or your judgment. Merchant defense only. It does not coach cardholders on filing disputes.
Live endpoint: POST https://pingpongit.com/api/dispute-evidence-pdf. JSON in, application/pdf out. Auth: optional anonymous preview; production agents send X-PingPong-Key or Authorization: Bearer ppk_…. Human form: win disputes.
A dispute lands with a clock. Your agent already pulled the order, tracking, chats, and cancel logs. The social move that wastes money is pasting a single-model letter into the console and calling that compelling evidence. Operators who defend more often submit a tight letterhead pack: company header, narrative mapped to the reason code, attachments labeled so a reviewer can skim.
Agent shape: POST case JSON → letterhead evidence PDF framing. Your agent sends structured case facts. Pingpong runs sequential review (Grok → Perplexity → ChatGPT → Gemini → Claude). You leave with a pressure-tested description and a pack outline sized for letterhead export. Brand: Pingpong at pingpongit.com.
Pays for itself: Stripe dispute fees plus lost revenue on one mid-ticket case routinely dwarf Plus and a stack of evidence PDFs. One prevented or won dispute is the no-brainer math. No invented win-rate percentages.
First call free framing: the first eligible evidence call is free. Then subscribe Plus $19.99/mo (includes 5 evidence PDFs per month plus dispute-description Pingpongs). Extra PDFs: $12 each or a 10-pack for $99. Pro $124.99/mo includes 25 evidence PDFs per month (Pro 25/mo allotment).
Start free Pingpong Developer docs API for agents
Sibling human lander: win disputes. Description ritual: write your dispute description. Stripe agent sibling: Stripe dispute API. Hub: dispute cases.
Case JSON your agent should send
Shape one dense object, not a vibe. Minimum useful fields:
{
"processor": "stripe|paypal|shopify|other",
"case_id": "DISPUTE_ID",
"reason_code": "CODE",
"reason_text": "category text",
"amount": "12.00",
"currency": "USD",
"order_id": "ORDER_ID",
"order_date": "YYYY-MM-DD",
"product": "one-line description",
"cardholder_claim": "what they allege",
"evidence": {
"tracking": "carrier + status",
"invoices": ["..."],
"chats": ["..."],
"cancel_logs": ["..."],
"avs_cvv": "notes if relevant",
"refunds_offered": ["..."],
"policy_urls": ["..."]
},
"letterhead": {
"legal_name": "Your Co LLC",
"support_email": "support@example.com"
},
"deadline": "YYYY-MM-DD",
"ask": "Write a dispute description mapped to this reason code. List what belongs in a letterhead PDF pack versus what to omit. Flag soft claims before Submit."
}Do not paste full PAN, CVV, bank passwords, or government IDs you are not allowed to store. Paste excerpts. Keep secrets server-side.
What comes back
A mapped dispute description you can paste into console fields. An evidence index that names each attachment and why it fits the code. Soft-claim flags (label-created sold as delivered, cancel email never reached the customer, refund already posted). That outline is what a letterhead PDF exporter renders under your logo. Today you still assemble files in the processor UI when the export button is not live yet.
Honest product status: POST /api/dispute-evidence-pdf is live (JSON in, PDF out). Human form: win disputes. Sequential multi-model review for richer case dumps remains on the main product / OpenAPI surface: developer docs.
Metering for agents (Plus / API)
First free wedge call per browser/device (cookie + durable claim). After that, anonymous callers get a hard Plus CTA (402) pointing at pricing — Plus $19.99/mo with a 5-PDF monthly allowance; extras $12 each or 10-pack $99; Pro $124.99/mo with 25 PDFs. Agents in production send a ppk_ key (issue at /api/dashboard; steps in developer docs). Keyed PDF calls count against business API quota and an hourly keyed rate limit. Anonymous IP hourly anti-abuse still applies. Confirm live plan at checkout. Full table: pricing.
How to get a ppk_ key
- Sign in at pingpongit.com.
- Open /api/dashboard and create an API key.
- Copy the one-time
ppk_live_…secret; send it asX-PingPong-KeyorAuthorization: BeareronPOST /api/dispute-evidence-pdf. - Keep keys server-side. Revoke from the dashboard if leaked.
Signed-in Plus/Pro customers manage subscription via the existing Stripe customer portal in the app. This wedge does not invent a separate Stripe meter for PDFs beyond the business API quota path.
Hard line
Legitimate merchant defense only. Not coaching to fabricate tracking, deny a valid refund, or pressure customers who correctly reversed an unauthorized charge. If the sale was wrong, refund and close. Do not run fiction through the chain.
Related
Hub for agents: API for agents. Stripe automation: Stripe dispute API. Docs: developer docs. Human CASE MAKER: win disputes. Cluster: dispute cases. Description: write your dispute description. Compelling pack: compelling evidence for chargebacks. Respond: respond to a chargeback. AI lander: AI chargeback response. Fee: Stripe dispute fee. Myths: chargeback win rate myths. CE 3.0: Compelling Evidence 3.0. Radar: Stripe Radar and disputes. Representment: dispute representment. Buyer-side (do not mix): before you file a chargeback. Also: submit chargeback evidence, Stripe dispute notification, chargeback alert response, merchant dispute workflow, Stripe dispute evidence examples, chargeback defense playbook. Also: Stripe dispute evidence template, chargeback case file, chargeback narrative writing. Also: chargeback automation for merchants, Stripe dispute evidence deadline, chargeback response letter template.
Run it before Submit
Have your agent POST the case dump (or paste it on pingpongit.com). Ask for the description and PDF pack outline. Keep what survives later models. Fix soft claims. Upload real attachments on time. If the chain earns a seat in your ops loop, choose Plus or Pro under Plans.
Again: not legal or financial advice. Merchant defense only.