Online merchants and subscription businesses
Win the chargebacks you should win, and stop paying to fight the ones you can't
Reads your dispute export from Stripe, Shopify, Square or PayPal, prices every open dispute by reason code and the evidence you hold, and flags Visa CE 3.0, 3D Secure, proof-of-delivery and refunded-but-disputed cases before the deadline. It drafts the representment narrative with the evidence checklist for each reason code, and tells you which small disputes cost more to contest than they return.
The problem
Many chargebacks are worth fighting, but each needs the right evidence in the right format before a short deadline, so merchants often accept the loss. Card networks also watch dispute ratios: Visa lowered its excessive-merchant threshold to 1.5% in the US, Canada, Europe and Asia-Pacific from 1 April 2026.
How it works
- Step 1Export the disputesThe dispute report from each processor you use, as a CSV.
- Step 2Join the order dataDelivery tracking, customer history, refunds, subscription cancellations and authentication results.
- Step 3Triage by reasonDisputes already refunded, duplicated or not worth fighting are set aside, so effort goes where the evidence is strong.
- Step 4Build each responseERPSav assembles the evidence pack and drafts the response for the dispute's reason code.
- Step 5Track due dates and outcomesThe queue is sorted by due date, every outcome is recorded, and your dispute ratio is shown month by month.
Typical results
- Value for merchants with 20–200 disputes a month
- $5,000–60,000 a year
- estimate
What the engine checks
- Evidence deadlines approaching or already missed
- Visa Compelling Evidence 3.0 and 3D Secure fraud disputes
- Item-not-received claims with proof of delivery
- Refunded payments that are still disputed, and duplicate disputes on one charge
- Low-value disputes not worth the countered fee
- Repeat disputers by card or customer
What you upload
A CSV export. Header names are matched automatically; these are the columns the engine reads.
| Column | Required | Example |
|---|---|---|
| Dispute ID | du_1QAa2b2eZvKYlo2C | |
| Charge / payment ID | ch_3QAa2b2eZvKYlo2C | |
| Disputed amount | Yes | 249.00 |
| Currency | usd | |
| Reason | Yes | fraudulent |
| Network reason code | 10.4 | |
| Card network | visa | |
| Status | needs_response | |
| Dispute created | 2026-10-25 | |
| Evidence due by | 2026-11-14 | |
| Charge date | 2026-09-30 | |
| Charge amount | 249.00 | |
| Processor | Stripe | |
| Customer | ana@example.com | |
| Card fingerprint | fp_8Kq2 | |
| Tracking number / has tracking | 1Z999AA10123456784 | |
| Delivered | Y | |
| AVS match | pass | |
| CVC match | pass | |
| 3DS authenticated | authenticated | |
| Customer communication | Y | |
| Refund issued | N | |
| Amount refunded | 60.00 | |
| Prior undisputed transactions | 3 | |
| IP / device match | Y | |
| Visa CE 3.0 eligible | ||
| Product type | physical |
What you need
- The dispute export from each processor: dispute ID, reason, amount and due date
- Order and fulfilment data: tracking, delivery confirmation, customer email and IP address
- Refund and subscription-cancellation records
- Your published refund and cancellation policy
Worked examples
Questions
- How long do we have to respond?
- Response windows are short and set by the card network and your processor. ERPSav sorts the queue by due date and drafts the response as soon as the dispute is imported.
- Which processors does it work with?
- Any processor whose dispute report you can export as a CSV, so one queue can cover several processors.
- Who submits the response?
- You do, in your processor's dashboard, with the evidence pack ERPSav builds. In the UK and Ireland the service is software-only.
- What does it cost?
- Self-serve plans start at $299 a month and you keep 100%. The Recovery plan is $99 a month for this module plus 12% of disputes won. Managed is 20% of disputes won. For comparison, Stripe charges $15 per dispute and its Smart Disputes service takes 30% of each dispute won.
- Is our data safe?
- ERPSav never needs full card numbers: dispute IDs and order data are enough. Your files go into your own workspace, and every row is scoped to it, so no other customer can see them. Imports, letters and status changes are written to an audit trail with who did what and when. ERPSav runs on its own servers in the EU behind Cloudflare, and most modules work from a CSV export, so nothing is installed.
You submit every response through your processor; ERPSav builds the evidence and the draft, and in the UK and Ireland it is software-only.