DisputesRepudiations

The Repudiation object

Description

The Repudiation object represents the funds withdrawn by Mangopay from the platform’s Repudiation Wallet to the user who made the pay-in following a corresponding chargeback. The Repudiation object is always created at the creation of a Dispute.

Note – Repudiation data retained for 13 months

An API call to retrieve a repudiation whose CreationDate is older than 13 months may return 404 Not Found.

For more information, see the Data availability periods article.

Attributes

AuthorIdstringOptional
The unique identifier of the user at the source of the initial transaction.
CreditedUserIdstringOptional

The unique identifier of the user whose wallet is credited. In the specific case of the Payout object, this value is always null since there is no credited wallet.

CreditedFundsobjectOptional

Information about the credited funds (CreditedFunds = DebitedFunds - Fees).

StatusstringOptional

Returned values: CREATED, SUCCEEDED, FAILED

The status of the transaction.

ExecutionDateintegerOptional

Unix timestamp (UTC) of the date and time the status changed to SUCCEEDED, indicating that the transaction occurred. The statuses CREATED and FAILED return an ExecutionDate of null.

TypestringOptional

Returned values: PAYIN, TRANSFER, CONVERSION, PAYOUT

The type of the transaction.

NaturestringOptional

Returned values: REGULAR, REPUDIATION, REFUND, SETTLEMENT

The nature of the transaction, providing more information about the context in which the transaction occurred:

  • REGULAR – Relative to most of the transactions (pay-ins, payouts, and transfers) in a usual workflow.
  • REPUDIATION – Automatic withdrawal of funds from the platform’s repudiation wallet as part of the dispute process (when the user has requested a chargeback).
  • REFUND – Reimbursement of a transaction to the user (pay-in refund), to a wallet (transfer refund), or of a payout (payout refund, only initiated by Mangopay).
  • SETTLEMENT – Transfer made to the repudiation wallet by the platform to settle a lost dispute.
CreditedWalletIdstringOptional

The unique identifier of the credited wallet. In the specific case of the Payout object, this value is always null since there is no credited wallet.

DebitedFundsobjectOptional
Information about the debited funds.
FeesobjectOptional
Information about the fees.
ResultCodestringOptional

The code indicating the result of the operation. This information is mostly used to handle errors or for filtering purposes.

ResultMessagestringOptional
The explanation of the result code.
IdstringOptional

Max length: 128 characters (see data formats for details)

The unique identifier of the object.

TagstringOptional

Max. length: 255 characters

Custom data that you can add to this object.

CreationDateintegerOptional

Unix timestamp (UTC) of the date and time the object was created.

InitialTransactionIdstringOptional
The unique identifier of the initial transaction being refunded.
InitialTransactionTypestringOptional

Returned values: PAYIN, TRANSFER, PAYOUT

The type of the initial transaction being refunded.

InitialTransactionNaturestringOptional

Returned values: REGULAR, REPUDIATION, REFUND, SETTLEMENT

The nature of the initial transaction being refunded, providing more information about the context in which the transaction occurred:

  • REGULAR – Relative to most of the transactions (pay-ins, payouts, and transfers) in a usual workflow.
  • REPUDIATION – Automatic withdrawal of funds from the platform’s repudiation wallet as part of the dispute process (when the user requested a chargeback).
  • REFUND – Reimbursement of a transaction to the user (pay-in refund), to a wallet (transfer refund), or of a payout (payout refund, only initiated by Mangopay).
  • SETTLEMENT – Transfer made to the repudiation wallet by the platform to settle the credit from a repudiation following a lost dispute.