> 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.
## **Disputes Dashboard**
Here, you can review the new dispute case, list of reported disputes, details of disputes, completed disputes, and evidence.
To learn more, see below Disputes feature in detail.
Figure: Disputes page
### **Upload Evidence on 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 the 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**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.xplorpay.com/merchant-portal/guides/disputes-management/managing-disputes-via-merchant-portal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.