Skip to content

PayPal dispute desk with fight or refund math

Pulls open PayPal disputes into a queue sorted by deadline, investigates each one with read only tools and works out whether fighting beats refunding. You edit the draft and see the exact request before anything is sent.

Ecommerce and resaleWorks with Claude Code · LangGraph+1Community example
Build your promptSee requirements

What it does

  • Lists open disputes with money at risk and the due date
  • Reads the dispute, the order, tracking and the buyer's history
  • Marks each piece of evidence as on file, weak or missing per reason code
  • Turns estimated win odds into an expected cost of fighting versus refunding
  • Drafts the evidence response and a message to the buyer

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Submitting evidence, accepting a claim or making an offer
  • Sending any message to the buyer
  • Refunding anything

You decide what happens next.

More about this workflow

This setup is for online sellers and resale shops juggling listings, orders and buyers. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it lists open disputes with money at risk and the due date. Next, it reads the dispute, the order, tracking and the buyer's history. Then it marks each piece of evidence as on file, weak or missing per reason code. After that, it turns estimated win odds into an expected cost of fighting versus refunding. Finally, it drafts the evidence response and a message to the buyer. It works with your payments, store admin and shipping app, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before submitting evidence, accepting a claim or making an offer, sending any message to the buyer and refunding anything, and says plainly if a step cannot be undone.

“Nothing is ever sent automatically.”
dylanbuchi dylanbuchi on GitHub · Oct 29, 2026
Before you startPayments · Store admin accessScoped permissionsClaude Code or LangGraph
Explore required tools and model recommendations

Tools and access

  • Stripe

    Handles the payments part of this job. Grant a restricted read-only key.

    API required: Yes. Needs an API key. Stripe offers restricted keys that limit what a key can do.

    Sign up: Stripe

  • Shopify

    Handles the store admin part of this job. Grant read orders and products.

    API required: Yes. Needs a Shopify app with an access token and the admin scopes you approve.

    Sign up: Shopify

  • ShipStation

    Handles the shipping app part of this job. Grant read order and shipment status.

    API required: Yes. Needs API credentials from your ShipStation account settings.

    Sign up: ShipStation

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Gemini 3.8 Flash

Built for agent workflows, with a free tier to test on.

$0.75 per million input tokens and $3.75 per million output tokens through December 31, 2026. $1.50 and $7.50 from January 1, 2027.

Google docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for many listings at once.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

read access to disputes and orders

fulfillment and tracking

refund below this amount

2Your prompt

4 of 4 still empty
Fill these in before you run it: [PAYMENT ACCOUNT: read access to disputes and orders] [STORE RECORDS: fulfillment and tracking] [DISPUTE FEE AND YOUR HOURLY COST] [QUICK CALL THRESHOLD: refund below this amount] You are the PayPal dispute desk with fight or refund math agent. Pulls open PayPal disputes into a queue sorted by deadline, investigates each one with read only tools and works out whether fighting beats refunding. You edit the draft and see the exact request before anything is sent. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Lists open disputes with money at risk and the due date - Reads the dispute, the order, tracking and the buyer's history - Marks each piece of evidence as on file, weak or missing per reason code - Turns estimated win odds into an expected cost of fighting versus refunding - Drafts the evidence response and a message to the buyer What you must never do without a yes from a person: - Submitting evidence, accepting a claim or making an offer - Sending any message to the buyer - Refunding anything Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, LangGraph, n8n

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Stripe with its own login, not yours. Grant a restricted read-only key.
  2. 2Connect Shopify with its own login, not yours. Grant read orders and products.
  3. 3Connect ShipStation with its own login, not yours. Grant read order and shipment status.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: submitting evidence, accepting a claim or making an offer, sending any message to the buyer, refunding anything.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for PayPal dispute desk with fight or refund math](https://trustcase.dev/badge/paypal-dispute-desk-with-fight-or-refund-math.svg)](https://trustcase.dev/use-cases/paypal-dispute-desk-with-fight-or-refund-math)
HTML
<a href="https://trustcase.dev/use-cases/paypal-dispute-desk-with-fight-or-refund-math"><img src="https://trustcase.dev/badge/paypal-dispute-desk-with-fight-or-refund-math.svg" alt="Trustcase trust score for PayPal dispute desk with fight or refund math" height="20"></a>

More ecommerce and resale workflows

Other workflows that use the same tools

  • Refund checker

    Support. Checks refund requests against your policy and lays out the facts.

  • Warranty replies that ask before they offer

    Support. A one person store has agents draft every customer email from the full thread and the order history. For a warranty problem the first reply only asks questions, and a hook blocks any draft that promises money or product until the owner approves that exact text.

  • Review moderation helper

    Support. Suggests whether a customer review should stay up, get a warning, be hidden or be reported, using only the text and star rating. A person makes the final call.