> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pocketsflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dispute fees covered

> When a buyer disputes a sale, Pocketsflow covers the dispute fee and writes the response for you.

<Note>
  Dispute fees covered is part of the **Volume** plan and above.
</Note>

A dispute (chargeback) costs a **\$15 fee** whether you win or lose. On Volume,
Pocketsflow covers that fee and our team writes the response with the order's
evidence. You don't have to do anything.

## What you see

Open the disputed order. In the **Disputed** card:

* **Dispute fee covered by Pocketsflow — \$15.00**
* the response status: *Response queued*, *Writing the response*, *Response
  submitted*, then *Dispute won* or *Dispute lost*.

You can still add details for our team with **Get help with a dispute**.

## What is covered

A dispute is covered when:

* the sale was made **while you were on the Volume plan** (sales from before
  you upgraded are not covered);
* you have not used this month's covered disputes yet (10 per calendar month,
  UTC);
* the store is in good standing.

When a dispute isn't covered, the order says why, for example *This sale was
made before your Volume plan started*.

## How the fee reaches you

The covered fee is recorded on the order the moment the dispute arrives. Our
finance team settles it with your payouts. When automatic transfers are on,
the order says **Added to your balance** once the fee has been sent to your
payouts account.

## API and AI agents

* `GET /creator-services` shows your monthly usage (`disputeCover.usage`).
* `GET /creator-services/dispute-covers` lists every dispute dispute cover
  looked at, covered or excluded with the reason.
* `GET /creator-services/dispute-covers/{saleId}` returns one order's cover
  (404 when it has none).

Reads are never gated. MCP tools: `list_dispute_covers`, `get_dispute_cover`.
See the [endpoint reference](/api-reference/endpoints#creator-services).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.