Skip to main content
PUT
This call is used both for the initial submission of the dispute and any resubmission made afterwards (in case more documents are required for instance).

Path parameters

string
required
The unique identifier of the dispute.

Body parameters

object
required
Information about the contested funds, in other words, the amount that you wish to contest.
Note: This amount can be lower than the disputed funds amount.

Responses

string
The unique identifier of the initial pay-in being disputed.
string
Returned values: PAYINThe type of the initial transaction being disputed.
string
Returned values: REGULARThe nature of the initial transaction being disputed.
string
Returned values: CONTESTABLE, NOT_CONTESTABLE, RETRIEVALThe 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.
Unix timestamp
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.
string
Information about the disputed funds.
Note: This amount can be lower than the initial transaction amount.
object
Information about the contested funds, in other words, the amount that you wish to contest.
Note: This amount can be lower than the disputed funds amount.
string
Returned values: CREATED, PENDING_CLIENT_ACTION, SUBMITTED, PENDING_BANK_ACTION, REOPENED_PENDING_CLIENT_ACTION, CLOSEDThe 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.
string
Additional information about the dispute Status communicated by Mangopay teams.
object
Information about the reasons for the dispute.
string
Returned values: LOST, WON, VOIDThe 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.
string
The explanation of the result code.
string
Max length: 128 characters (see data formats for details)The unique identifier of the object.
string
Max. length: 255 charactersCustom data that you can add to this object.
Unix timestamp
The date and time at which the object was created.
Unix timestamp
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.
string
The unique identifier of the repudiation.