> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/merchant-portal/guides/disputes-management/managing-disputes-via-merchant-portal.md).

# Managing Disputes via Merchant Portal

To review and manage disputes on the dashboard, get access to the [Merchant Portal](/merchant-portal/merchant-portal/accessing-the-merchant-portal.md) and visit the **Disputes** tab.

Watch the interactive walkthrough below to review, respond to, and manage cardholder disputes.

{% embed url="<https://app.guideflow.com/player/zpelw2ms3k>" %}

## **Disputes Dashboard** <a href="#disputes-dashboard" id="disputes-dashboard"></a>

Here, you can review the new dispute case, list of reported disputes, details of disputes, completed disputes, and evidence.

<figure><img src="https://3375311351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNkAy7CO9ci3kcil9jOX%2Fuploads%2FXWlrSglOHzI69LYWBFNK%2Fimage.png?alt=media&amp;token=adc55285-9c08-4b0c-94be-1aaa6fa03ca6" alt=""><figcaption><p>Figure: Disputes page</p></figcaption></figure>

### **Upload Evidence for Dispute**

* You can upload supporting zip file documents up to 10MB in size.
* Each zip file contains up to 500 files.
* The files format allows JPG or PDF.

Upload the evidence on dashboard to challenge dispute and protect the chargeback.

### **Accept Dispute**

Ensure that once you accept liability for a dispute, the decision is final and cannot be reversed.

1. From the Dispute tab, choose the chargeback entry from the dispute table.
2. Review the case details and dispute details.
3. In the **Response** section, select **Accept Dispute**, then click **Submit**.<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xplorpay.com/merchant-portal/guides/disputes-management/managing-disputes-via-merchant-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.