For PlatformsRun Connect
Disputes
Every dispute across every merchant in Connect - statuses, filters, the evidence PDF and its version history, and viewing a dispute as the merchant sees it.
Disputes is every dispute across all your merchants, and where each one stands right now.
Statuses
| Status | Meaning |
|---|---|
| Needs response | The clock is running and evidence has not been submitted |
| Under review | Submitted, waiting on the issuer |
| Won | Decided in the merchant's favour |
| Lost | Decided against the merchant |
| Appealable | Lost, but a further stage is available |
| Insured | Covered under the merchant's arrangement regardless of outcome |
| Prevented | Deflected before it became a chargeback |
The underlying state machine, including which transitions are possible, is documented in Dispute state machine.
What you can do
- Track volume over time, with a processing versus won breakdown and total charges.
- Filter by status, response deadline, reason, source (Stripe, Klarna, PayPal, Afterpay, Adyen, or the Chargeflow API), card, stage, and amount.
- See what is managed by Chargeflow versus handled elsewhere, so a dispute never falls between you and the engine.
- Open the evidence PDF submitted for a dispute, and view its version history where the evidence was revised.
- View as merchant to see a dispute exactly as the merchant sees it, which is what you want open when they call support.
Response deadlines
Deadlines come from the card network and the processor, not from Chargeflow, and they are the one thing that cannot be recovered once missed. Filter by response deadline when you want to know what is at risk this week. Network timelines are documented in Network timelines.
Reading it over the API
Everything on this screen is available programmatically:
| You want | Endpoint |
|---|---|
| List disputes for a merchant | Get disputes |
| Load a dispute into Connect | Create dispute |
| Fetch a generated evidence package | Get evidence by ID |
| Be told when something changes | Platform webhook events |
Next step
Was this page helpful?