> 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/merchant-portal/core-features/viewing-chargebacks.md).

# Viewing Chargebacks

The **Chargeback r**eport allows you to view chargeback activity for transactions. Use the **Month/Year** filter to find chargeback records for a specific period.

Watch the interactive walkthrough below to review chargeback activity and related transaction details.

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

The report includes details such as **Settlement Date, Card Number, Type, Reference #, Card Brand, Reason Code, Settlement Amount,** and **Fee Amount**. Select **Export** to download the report for further review.

Search chargeback records using:

* **Filter by Month/Year** — Select a month and year to filter chargeback records.
* **Search** — Select **Search** to display matching chargeback records.
* **Reset** — Select **Reset** to clear the selected filters.
* **Export** — Select **Export** to download the chargeback report.

<div data-with-frame="true"><figure><img src="https://3375311351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNkAy7CO9ci3kcil9jOX%2Fuploads%2FqWdruMeSnAUr3w7vepBa%2Fimage.png?alt=media&amp;token=2b8bf9fa-6a4b-4c3a-b45a-0d9e492170bd" alt=""><figcaption><p>Screenshot: Chargebacks page</p></figcaption></figure></div>


---

# 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/merchant-portal/core-features/viewing-chargebacks.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.