Work every open Stripe dispute from one chargeback war room

Build me a chargeback war room: one app where I work every open Stripe dispute in one place instead of scrambling around the Stripe dashboard while evidence deadlines creep up on me.

The home screen is a board of disputes pulled with the Stripe List Disputes operation, filtered to the ones that still need a response, sorted by how close the evidence deadline is so the most urgent sits at the top. Each row shows the disputed amount and currency, the reason code the customer's bank gave, how much time is left before the evidence deadline, and whether we have a drafted rebuttal for it yet. Flag any row whose deadline falls inside the next 72 hours so it is impossible to miss.

Clicking a dispute opens a detail screen. Pull the underlying payment with Stripe Retrieve Charge, and pull that same buyer's other payments with Stripe List Charges filtered to their customer id, so I can see at a glance whether this is a long-standing customer or a first and only transaction. Next to that, show a risk panel built from IPQualityScore: run IP Reputation and Proxy/VPN Detection on the IP address the payment came from, Email Validation on the buyer's email, and Phone Number Validation on their phone. Show the fraud scores plainly using the bands IPQualityScore documents, where 75 and above is suspicious and 90 and above is high risk, and call out the individual signals that decide this case: proxy or VPN use, a disposable or freshly created email, a VOIP or inactive phone number.

Give me a Build my rebuttal button that starts a background agent. The agent gathers the charge and the buyer's full payment history, runs those three IPQualityScore lookups, weighs the signals together, and drafts an evidence narrative that lands back in the app as editable text attached to that dispute. The argument has to change depending on what the signals say. If the IP is clean residential, the email is valid and long-lived, and the buyer has prior successful payments that were never disputed, this is most likely friendly fraud, meaning someone disputing a purchase they genuinely made, so the narrative should lean on the matching payment history, the delivery or usage record, and the consistency between this payment and their past ones. If the IP is a proxy or VPN, the email is disposable, or the phone is VOIP with no history behind it, the agent should write the case as genuine card fraud and say plainly in its recommendation that fighting it is probably not worth the effort.

Nothing gets sent until I approve it. The agent only ever produces a draft. I read it, edit the text inside the app, and only when I click Submit evidence does the app send it through Stripe Update Dispute with the evidence marked for review. Saving my edits without submitting should also go through Stripe Update Dispute but without submitting for review, so a work in progress is always safe to leave. Because submitting evidence is effectively irreversible, put a clear confirmation step in front of that button which spells out that the submission is final.

When the risk data says the charge really was fraudulent and fighting it would only waste the time, I want the other option available on the same screen: accept the dispute using Stripe Close Dispute, which accepts the dispute and lets the charge be reversed. Put that behind its own confirmation as well, and record the reason we chose to accept.

Save every dispute's evidence, decision and eventual outcome to the General Input Database. Each record should carry the dispute id, the charge id, the reason code, the amount, the risk scores we saw, whether the agent classified it as friendly fraud or true card fraud, whether we fought or accepted, the evidence text we submitted, and the final outcome once Stripe resolves it. Use that table to give me a second view showing our win rate by reason code over time, so I can learn which categories are worth fighting and which ones we lose every time.

This is for whoever owns chargebacks, usually one person in finance or risk ops working the queue a few times a week. Optimise the layout for that: the queue is the home screen, the deadline is always visible, and the path from opening a dispute to having a draft to submitting or accepting should be short and hard to get wrong.