Skip to content

Chargeback evidence pack

When a customer files a card dispute, it gathers proof they used what they paid for and builds the evidence pack. A person checks it before anything is submitted.

SupportWorks with Claude Code · Cursor+1Community example
Build your promptSee requirements

What it does

  • Catches new disputes from your payment provider
  • Pulls the customer's plan, payments and usage history
  • Builds a PDF with an activity log and samples of their work
  • Tracks each dispute to won or lost and pings you

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Submitting evidence to the payment provider
  • Issuing any refund

You decide what happens next.

More about this workflow

This setup is for support leads and small teams who answer customers every day. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it catches new disputes from your payment provider. Next, it pulls the customer's plan, payments and usage history. Then it builds a PDF with an activity log and samples of their work. Finally, it tracks each dispute to won or lost and pings you. It works with your payments, database and chat, 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 to the payment provider and issuing any refund, and says plainly if a step cannot be undone.

“it even includes the interior designs they generated in the evidence PDF”
levelsio @levelsio · Apr 6, 2026
Before you startPayments · Database accessScoped permissionsClaude Code or Cursor
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

  • Supabase

    Handles the database part of this job. Grant a role limited to one table.

    API required: Yes. Needs a Supabase project and an API key. Give the agent a role limited to one table.

    Sign up: Supabase

  • Slack

    Handles the chat part of this job. Grant a bot token in the channels it needs.

    API required: Yes. Needs a Slack app created in your workspace. It gets a bot token with the scopes you approve.

    Sign up: Create a Slack app

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Writes careful replies and reads long ticket threads.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Made for sorting and routing at high volume.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic 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.

e.g. files made, logins

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR PAYMENT ACCOUNT] [WHAT COUNTS AS USE: e.g. files made, logins] [YOUR REFUND POLICY] [WHERE TO PING YOU] You are the Chargeback evidence pack agent. When a customer files a card dispute, it gathers proof they used what they paid for and builds the evidence pack. A person checks it before anything is submitted. 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: - Catches new disputes from your payment provider - Pulls the customer's plan, payments and usage history - Builds a PDF with an activity log and samples of their work - Tracks each dispute to won or lost and pings you What you must never do without a yes from a person: - Submitting evidence to the payment provider - Issuing any refund 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, Cursor, 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 Supabase with its own login, not yours. Grant a role limited to one table.
  3. 3Connect Slack with its own login, not yours. Grant a bot token in the channels it needs.
  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 to the payment provider, issuing any refund.

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 Chargeback evidence pack](https://trustcase.dev/badge/chargeback-evidence-pack.svg)](https://trustcase.dev/use-cases/chargeback-evidence-pack)
HTML
<a href="https://trustcase.dev/use-cases/chargeback-evidence-pack"><img src="https://trustcase.dev/badge/chargeback-evidence-pack.svg" alt="Trustcase trust score for Chargeback evidence pack" height="20"></a>

More support workflows

  • Evidence first support replies

    Works the support queue a couple of times a day, checking bug reports against the code before drafting a reply. The owner reviews every reply before it goes out.

  • Community help answers with moderator review

    Drafts answers to questions in your community help forum from your docs. A moderator checks each one before the user sees it.

  • Help tutorials from your app

    Drives your web app on demo data to make step by step help pictures, narrated videos and a help page. Rerun it when the screens change.

  • Customer renewal readiness check

    Checks every customer account renewing in the next 120 days and gives each one a readiness status with reasons. Built for small customer success teams working from exports.