> 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/api-reference/api/disputes.md).

# Disputes

The **Disputes API** lets you manage the lifecycle of payment dispute cases. You can retrieve information for dispute cases, monitor case statuses, and submit responses with supporting evidence.

### **Disputes lifecycle**

A **dispute** occurs when a cardholder questions a transaction with their issuing bank. If you notice unauthorized charges, incorrect transactions, or issues with a purchase, you can contact your bank to investigate and potentially reverse the charge.

The bank reviews the claim and asks for additional information from the merchant to determine whether the transaction was valid.

The following steps help you manage the dispute lifecycle:

{% stepper %}
{% step %}

#### **Dispute**

A dispute begins when a cardholder reports a transaction concern to their issuing bank.

Common reasons for disputes include:

* Unrecognized charges
* Dissatisfaction with the product
* Undelivered merchandise
* Subscription cancellation issues
* Suspected fraud

{% hint style="success" icon="memo-circle-check" %}
Visa does not support retrieval requests and proceeds directly to a chargeback.
{% endhint %}
{% endstep %}

{% step %}

#### **Chargeback**

If the issuing bank determines that the dispute requires a financial reversal, the transaction becomes a chargeback. The disputed amount is temporarily credited to the cardholder and withdrawn from the merchant account.

Chargebacks may result in:

* Reversal of the transaction amount
* Chargeback processing fees
* Impact on the merchant’s dispute ratio
  {% endstep %}

{% step %}

#### **Representment**

In a representment, the merchant challenges a chargeback by submitting evidence to the issuing bank.

Supporting evidence may include:

* Transaction receipts
* Delivery confirmations
* Customer communication records

If the issuing bank accepts the evidence, the chargeback is reversed, and the funds are returned to the merchant.
{% endstep %}

{% step %}

#### **Pre-Arbitration**

If the issuing bank rejects the outcome of a representment, the dispute moves to pre-arbitration.

During pre-arbitration:

* The issuing bank requests an additional review of the dispute.
* The cardholder or issuing bank challenges the representment outcome.
* The merchant may choose to accept the chargeback or escalate the dispute.
  {% endstep %}

{% step %}

#### **Arbitration**

If the dispute remains unresolved, it may proceed to arbitration.

During arbitration:

* The card network reviews the dispute and all submitted evidence.

* The card network makes the final decision.

* Additional arbitration fees apply to the losing party.
  {% endstep %}
  {% endstepper %}

* [Disputes Management](https://docs.xplorpay.com/api-reference/api/disputes/disputes-management.md)
  * [Dispute Responses](https://docs.xplorpay.com/api-reference/api/disputes/disputes-management/dispute-responses.md)
  * [Disputes Reporting](https://docs.xplorpay.com/api-reference/api/disputes/disputes-management/disputes-reporting.md)


---

# 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/api-reference/api/disputes.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.
