> For the complete documentation index, see [llms.txt](https://help.jupico.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jupico.com/disputes.md).

# Disputes

Learn about disputes, evidence best practices, and what you can do to prevent them.

A dispute (also known as a chargeback) occurs when a cardholder questions your payment to their card issuer.

To process a chargeback, the issuer creates a formal dispute by challenging all or parts of the payment. This immediately reverses the payment and pulls the money for the payment from Jupico. After that, Jupico debits your balance for the payment amount and dispute fee. 

To help our merchants submit the best possible response for each dispute, Jupico guides you through the process within this dashboard. If you need any additional help, please contact our Jupico Support team at <support@jupico.com>.&#x20;

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><strong>Responding to Disputes</strong></td><td>Learn how to challenge or accept a dispute.</td><td><a href="/disputes/responding-to-disputes.md">Responding to Disputes</a></td></tr><tr><td></td><td><strong>Dispute Evidence Best Practices</strong></td><td>Learn about evidence guidelines for challenging a dispute.</td><td><a href="/disputes/dispute-evidence-best-practices.md">Dispute Evidence Best Practices</a></td></tr><tr><td></td><td><strong>Dispute Prevention</strong></td><td>Learn best practices for preventing disputes</td><td><a href="/disputes/dispute-prevention.md">Dispute Prevention</a></td></tr></tbody></table>


---

# 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://help.jupico.com/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.