---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/risk/disputesAPI/index.md
description: >-
  dispute API Used for automated processing of payment disputes, supporting
  proactive retrieval of transaction information and chargeback details,
  querying and uploading defense materials, and other functions. Suitable for
  rapid response and management of the entire process after dispute initiation,
  including submitting or abandoning appeals. Through this API, merchants can
  more efficiently handle issuer's retrieval requests and chargeback situations.
---
## dispute API

If you plan to handle dispute cases from your server side, this page provides both the integration flow and quick API entry points.

::: tip Scope
- This page keeps the dispute-handling flow and entry order.
- For request fields, examples, and response structures, use the dedicated API detail pages.
- For callback event meanings and webhook handling, see [Dispute Notification Integration Guide](/en/notes/risk/disputeNotify/).
:::

To help you quickly manage disputes, we provide the dispute API. These APIs let you automate the dispute-handling process and respond as soon as a case is initiated.

### Quick API Entry

- [Get Retrieval Details](/en/notes/dispute/v4-apis/getRetrievalDispute/)
- [Get Chargeback/Dispute Details](/en/notes/dispute/v4-apis/getDisputeInfo/)
- [Query Defense Materials](/en/notes/dispute/v4-apis/getDefenseReasons/)
- [Upload Dispute File](/en/notes/dispute/v4-apis/disputeUploadFile/)
- [Upload Defense Document](/en/notes/dispute/v4-apis/supplyDefenseDocument/)
- [Delete Defense Document](/en/notes/dispute/v4-apis/deleteDefenseDocument/)
- [Submit Defense](/en/notes/dispute/v4-apis/defendDispute/)
- [Accept Dispute](/en/notes/dispute/v4-apis/acceptDispute/)

## dispute API Processing Flow

### Chargeback Process

When <a href="/en/notes/technicalterm/disputes/" target="_blank">retrieval</a> occurs, the issuer requests additional transaction information. At this stage, no funds are withdrawn from your account, so it is recommended that you handle the case actively.

<v4-iImage src = "/v4/dispute/dispute.png" name = "Overall Process Flow"></v4-iImage>

When using the dispute API, the usual handling order is:

1. First receive dispute notifications and use the `eventCode` in the [Dispute Notification Integration Guide](/en/notes/risk/disputeNotify/) to determine the current case stage.
2. Then query case details and available defense information, for example by calling [Query Defense Materials](/en/notes/dispute/v4-apis/getDefenseReasons/).
3. If you decide to defend the case, continue with evidence upload, evidence correction, and final submission.

Optional actions:

- If you do not plan to continue defending the case, you can directly [Accept Dispute](/en/notes/dispute/v4-apis/acceptDispute/).
- Before final submission, you can [Upload Dispute File](/en/notes/dispute/v4-apis/disputeUploadFile/), [Upload Defense Document](/en/notes/dispute/v4-apis/supplyDefenseDocument/), and if needed [Delete Defense Document](/en/notes/dispute/v4-apis/deleteDefenseDocument/).
- Once the materials are ready, call [Submit Defense](/en/notes/dispute/v4-apis/defendDispute/) to complete the case action.

### Background Reading

- [Dispute Overview](/en/notes/risk/overview/)
- [Disputes](/en/notes/technicalterm/disputes/)
- [Chargebacks](/en/notes/technicalterm/chargebacks/)