Finding disputes

The Disputes list is your working queue — every case, filterable by stage, brand, processor, reason, and date. It’s where you triage what needs attention and open individual cases.

📷 Screenshot

The Disputes list: the pipeline bar across the top, the filter bar, and the case table. Replace this note with: ![Disputes list](/images/disputes/list.png)

The pipeline bar

A row of stage tiles at the top doubles as a one-click filter, each showing a live count: All, Gathering, Needs attention, Awaiting review, Submitted, Under review, Won, Lost, Pre-Arb Accepted, and Accepted. Select a tile to see just those cases. Needs attention turns red when there are cases waiting on you.

Filtering and search

Below the pipeline bar you can narrow the list by:

• Search — order ID, dispute ID, or customer.
• Brand, Processor, and Reason dropdowns.
• A date range for when disputes were created.

The table

Each row shows the created date, dispute ID, order, amount, processor, brand, reason, due date, and status. Due dates are color-coded by urgency, and rows needing attention are highlighted with a Fix → link instead of Open →. Cases carry TEST and PRE-ARB badges where relevant.

Export to CSV

Select Export CSV to download the current list. The export respects your active filters, so you can pull exactly the slice you’re looking at.

Create a test case (admins)

Admins can create a test case to watch the evidence pipeline run against a real order before live disputes arrive:

1. Select Create test case.
2. Enter the brand and order ID, then Look up order to prefill the customer and amount.
3. Pick a reason code and an optional reply-by date.
4. Create test case.

A test case runs the full evidence pipeline but cannot be submitted to the processor, and is visible to admins only. It’s the best way to confirm your setup end-to-end.

Tip

Use the Needs attention tile as your daily starting point — it surfaces exactly the cases where automation needs a hand. See Cases that need attention.