> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mangopay.com/api-reference/disputes/dispute-object/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mangopay.com/_mcp/server. # The Dispute object ### Description Mangopay relies on the Dispute object to manage chargeback requests from a User. This object is automatically created when the user’s bank orders the reversal of a pay-in. As a consequence, Mangopay withdraws the required funds from the platform’s Repudiation Wallet. This is called a repudiation and results in the repudiation wallet having a negative balance that the platform will need to settle. ### Attributes ### Schema (`DisputeResponse`) ```yaml components: schemas: Currency: type: string description: >- **Allowed values:** The three-letter ISO 4217 code (EUR, GBP, etc.) of a supported currency (depends on feature, contract, and activation settings). The currency of the amount. title: Currency Amount: type: integer description: >- 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`. title: Amount DisputeResponseDisputedFunds: type: object properties: Currency: $ref: '#/components/schemas/Currency' Amount: $ref: '#/components/schemas/Amount' description: |- Information about the amount the disputed funds. This amount can be lower than the initial transaction amount. title: DisputeResponseDisputedFunds DisputeResponseContestedFunds: type: object properties: Currency: $ref: '#/components/schemas/Currency' Amount: $ref: '#/components/schemas/Amount' description: >- 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. title: DisputeResponseContestedFunds DisputeResponseDisputeReason: type: object properties: DisputeReasonType: type: string description: The reason for the dispute. DisputeReasonMessage: type: string description: >- Additional information about the reason for the dispute sent by Mangopay teams. description: Information about the reasons for the dispute. title: DisputeResponseDisputeReason ResultMessage: type: string description: The explanation of the result code. title: ResultMessage Id: type: string description: >- Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object. title: Id Tag: type: string description: >- Max. length: 255 characters Custom data that you can add to this object, such as unique identifiers in your system. To store multiple values, you can serialize them into a single string, for example a JSON object: `"{\"id_1\":AB123,\"id_2\":DE456}"`. title: Tag CreationDate: type: integer description: Unix timestamp (UTC) of the date and time the object was created. title: CreationDate DisputeResponse: type: object properties: InitialTransactionId: type: string description: The unique identifier of the initial pay-in being disputed. InitialTransactionType: type: string description: |- **Returned values:** `PAYIN` The type of the initial transaction being disputed. InitialTransactionNature: type: string description: |- **Returned values:** `REGULAR` The nature of the initial transaction being disputed. DisputeType: type: string description: >- **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: type: integer description: >- 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: $ref: '#/components/schemas/DisputeResponseDisputedFunds' description: |- Information about the amount the disputed funds. This amount can be lower than the initial transaction amount. ContestedFunds: $ref: '#/components/schemas/DisputeResponseContestedFunds' description: >- 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. Status: type: string description: >- **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: type: string description: >- Additional information about the dispute `Status` communicated by Mangopay teams. DisputeReason: $ref: '#/components/schemas/DisputeResponseDisputeReason' description: Information about the reasons for the dispute. ResultCode: type: string description: >- **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: $ref: '#/components/schemas/ResultMessage' Id: $ref: '#/components/schemas/Id' Tag: $ref: '#/components/schemas/Tag' CreationDate: $ref: '#/components/schemas/CreationDate' ClosedDate: type: integer description: >- 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: type: string description: The unique identifier of the repudiation. title: DisputeResponse ``` ### Related resources #### [Guide](/guides/disputes) Learn more about disputes