Now defending disputes on Shopify Payments, Whop and PayPal. See integrations
Runs without you

What happens between the chargeback and the verdict

All automatic. You can watch every stage, and stop any of them.

1

A dispute opens — and we already know

The clock on a chargeback starts without you. A processor webhook fires the moment one is filed, and Recoup opens the case immediately with the order, the customer, the reason code and the response deadline already attached.

  • Disputes raised before you installed are picked up too — we reconcile against the processor rather than relying only on webhooks, so nothing is invisible just because it predates us.
  • The deadline is recorded from the processor's own value, not estimated, and everything downstream is scheduled against it.
  • Slack and email alerts fire on open, so your team sees it without opening another dashboard.
2

The evidence is gathered from your own systems

Nothing here is invented. Every element is pulled from a source that already exists — your store, your carrier, your processor, your inbox — so the packet is made of facts a reviewer can verify.

  • Order record: line items and variants, fulfilment status, billing and shipping addresses, and the full timeline of the order.
  • Delivery: carrier tracking with the complete scan history, the delivery confirmation isolated and dated — including when delivery landed after the dispute was filed, which is often decisive.
  • Risk signals: AVS street and ZIP results, CVV match, the purchase IP, and the processor's own risk assessment and positive risk factors.
  • Policies: your refund, return, shipping and cancellation terms as published, plus a capture of your checkout showing they were presented before payment.
  • Customer conversation: if you connect a mailbox or helpdesk, we find the thread for that order — what was offered, what was refused, and what the cardholder said in their own words.
3

The argument is written for that specific claim

A representment is not a data dump. The same order can need a completely different argument depending on what the cardholder actually claimed, and the packet is built around that claim.

  • The reason code decides what leads. A not-received claim is answered by the delivery scan; a product-unacceptable claim is answered by the listing, the condition on arrival and the return the cardholder did not make.
  • Facts that would weaken the case are not volunteered. The letter states what helps and stays silent where silence is honest — it never asserts something the record does not support.
  • The sections that matter most survive the processor's character limit. When a filing has to be trimmed, the argument and the conclusion are the last things cut, not the first.
  • Exhibits are attached as a PDF: the delivery proof, policy pages, the checkout capture and the conversation, each labelled.
4

It is filed before the deadline — and checked

Evidence that is written but not filed is worth nothing, and evidence filed in a broken state is worse than none. Both are verified against the processor's own copy rather than our logs.

  • Every packet is checked after upload by reading back what the processor actually stored — not by trusting our own return value.
  • A filing that comes back truncated, missing its conclusion, or missing an attachment is held and flagged rather than left to go out silently.
  • You choose whether filing is fully automatic or requires your approval first. Either way the deadline is tracked, and you are warned before one is about to pass.
  • The outcome is synced back when the issuer decides, so your dashboard reflects what actually happened rather than what we last knew.
What we will not do

The limits, stated plainly

We cannot prevent every chargeback. Prevention depends on an alert arriving in time — most do, but a cardholder who goes straight to a chargeback without querying the charge first never generates one. Those we fight instead.

We only refund within your rules. Automatic refunding is off until you switch it on, you set the ceiling above which we always ask, and anything that matches two orders equally well comes to you. We never write to your catalogue.

We do not invent evidence. If your store cannot prove something, the letter does not claim it. A representment built on an assertion the record contradicts is worse than a weak one — issuers read the whole file.

We cannot win every dispute. Some claims are simply correct, and some arrive with nothing to argue from. Those cost you nothing, because we only charge on a win.

See it on your own disputes

Install, and the next chargeback is answered automatically. Nothing is charged unless it is won.

Get started free See pricing