---
title: "Update a Dispute"
method: PUT
path: "/v2.01/{ClientId}/disputes/{DisputeId}"
tags: ["Disputes"]
---

# Update a Dispute

`PUT /v2.01/{ClientId}/disputes/{DisputeId}`

Update a Dispute

## Path parameters

- `ClientId` string, required
- `DisputeId` string, required

## Headers

- `Authorization` string, required

## Response `200`

Success

- DisputeResponse
  - `InitialTransactionId` string — The unique identifier of the initial pay-in being disputed.
  - `InitialTransactionType` string — **Returned values:** `PAYIN` The type of the initial transaction being disputed.
  - `InitialTransactionNature` string — **Returned values:** `REGULAR` The nature of the initial transaction being disputed.
  - `DisputeType` string — **Returned values:** `CONTESTABLE`, `NOT_CONTESTABLE`, `RETRIEVAL` The type of dispute: - `CONTESTABLE` – Dispute for which the chargeback can be contested by providing proof (i.e., Dispute Documents) justifying the original transaction. - `NOT_CONTESTABLE` – Dispute that is automatically closed after its creation, without any action possible for the platform. - `RETRIEVAL` – Dispute that is actually a chargeback warning issued by the bank. The platform is required to provide documents, but no funds will be taken from the Repudiation Wallet.
  - `ContestDeadlineDate` integer — The date and time until which the platform can contest the dispute (i.e., the `Status` is set to `SUBMITTED`). This date is defined by the issuing bank of the initial transaction and may usually vary between 7 to 18 days. Once the deadline passes, the dispute `Status` is automatically set to `CLOSED`.
  - `DisputedFunds` DisputeResponseDisputedFunds — Information about the amount the disputed funds. This amount can be lower than the initial transaction amount.
    - `Currency` string — **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
    - `Amount` integer — The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
  - `ContestedFunds` DisputeResponseContestedFunds — Information about the contested funds, in other words, the amount that you wish to contest. This amount can be lower than the disputed funds amount.
    - `Currency` string — **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
    - `Amount` integer — The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
  - `Status` string — **Returned values:** `CREATED`, `PENDING_CLIENT_ACTION`, `SUBMITTED`, `PENDING_BANK_ACTION`, `REOPENED_PENDING_CLIENT_ACTION`, `CLOSED` The status of the dispute: - `CREATED` – The dispute is created. - `PENDING_CLIENT_ACTION` – The dispute was not closed automatically upon its creation, it now requires some actions from the platform (either submission after providing the relevant proofs or closing). - `SUBMITTED` – The dispute is submitted by the platform for the Mangopay team to review the documents. - `PENDING_BANK_ACTION` – Mangopay accepted the documents and passed them on to the bank for them to review the dispute contestation. They will either reject or accept the contestation, or require further documents. - `REOPENED_PENDING_CLIENT_ACTION` – Mangopay didn’t accept the documents and requires more information or documents before sending the documents to the bank. - `CLOSED` – The dispute is closed.
  - `StatusMessage` string — Additional information about the dispute `Status` communicated by Mangopay teams.
  - `DisputeReason` DisputeResponseDisputeReason — Information about the reasons for the dispute.
    - `DisputeReasonType` string — The reason for the dispute.
    - `DisputeReasonMessage` string — Additional information about the reason for the dispute sent by Mangopay teams.
  - `ResultCode` string — **Returned values:** `LOST`, `WON`, `VOID` The result of the dispute for the platform, which can be: - `LOST` – The platform lost the dispute and must settle its debt to Mangopay with a Settlement Transfer. - `WON` – The platform won the dispute, the disputed funds will be credited back to the Repudiation Wallet. - `VOID` – The dispute has been canceled.
  - `ResultMessage` string — The explanation of the result code.
  - `Id` string — Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object.
  - `Tag` string — Max. length: 255 characters Custom data that you can add to this object.
  - `CreationDate` integer — Unix timestamp (UTC) of the date and time the object was created.
  - `ClosedDate` integer — The date and time the dispute was closed (i.e., its `Status` is set to `CLOSED`). **Note:** This value will be `null` for any Dispute closed before February 16th, 2023.
  - `RepudiationId` string — The unique identifier of the repudiation.

---

[API](https://skmtc.net/mangopay/apis/api-reference.md) · [All operations](https://skmtc.net/mangopay/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mangopay/api-reference/versions/795281070285/schema)