Authorizations
Oauth 2.0 authentication
Path Parameters
The ID of the dispute for which to provide the supporting information.
1 - 255
Response
A successful request returns the HTTP 200 OK
status code and a JSON response body that shows dispute details.
The dispute details.
The ID of the dispute.
1 - 255
The date and time when the dispute was created, in Internet date and time format. For example, yyyy
-MM
-dd
T
HH
:mm
:ss
.SSS
Z
.
20 - 64
The date and time when the dispute was last updated, in Internet date and time format. For example, yyyy
-MM
-dd
T
HH
:mm
:ss
.SSS
Z
.
20 - 64
An array of transactions for which disputes were created.
1 - 1000
elementsThe reason for the item-level dispute. For information about the required information for each dispute reason and associated evidence type, see <a href="/docs/integration/direct/customer-disputes/integration-guide/#dispute-reasons">dispute reasons</a>.
MERCHANDISE_OR_SERVICE_NOT_RECEIVED
, MERCHANDISE_OR_SERVICE_NOT_AS_DESCRIBED
, UNAUTHORISED
, CREDIT_NOT_PROCESSED
, DUPLICATE_TRANSACTION
, INCORRECT_AMOUNT
, PAYMENT_BY_OTHER_MEANS
, CANCELED_RECURRING_BILLING
, PROBLEM_WITH_REMITTANCE
, OTHER
The overall status of the dispute, constant for all the parties involved at anytime during the dispute lifecycle.
OPEN
, WAITING_FOR_BUYER_RESPONSE
, WAITING_FOR_SELLER_RESPONSE
, UNDER_REVIEW
, RESOLVED
, OTHER
The amount in the transaction that the customer originally disputed. Because customers can sometimes dispute only part of the payment, the disputed amount might be different from the total gross or net amount of the original transaction.
The asset in the transaction that the customer disputed.
Policy that determines whether the fee needs to be charged, retained or returned while moving the money as part of dispute process.
The code that identifies the reason for the credit card chargeback. Each card issuer follows their own standards for defining reason type, code, and its format. For more details about the external reason code, see the card issue site. Available for only unbranded transactions.
1 - 2000
The outcome of a dispute.
The Teammate Adjudication details for the dispute.
1 - 10
elementsDEPRECATED The Money movement details for the dispute.
1 - 50
elementsThe movements of fund due to the dispute.
1 - 50
elementsThe stage in the dispute lifecycle.
INQUIRY
, CHARGEBACK
, PRE_ARBITRATION
, ARBITRATION
The channel where the customer created the dispute.
INTERNAL
, EXTERNAL
, ALERT
An array of customer- or merchant-posted messages for the dispute.
1 - 1000
elementsThe extended properties for the dispute. Includes additional information for a dispute category, such as billing disputes, the original transaction ID, and the correct amount.
An array of evidence documents.
1 - 100
elementsThe date and time by when the customer must respond to the dispute, in Internet date and time format. If the customer does not respond by this date and time, the dispute is closed in the merchant's favor. For example, yyyy
-MM
-dd
T
HH
:mm
:ss
.SSS
Z
.
20 - 64
The date and time by when the merchant must respond to the dispute, in Internet date and time format. If the merchant does not respond by this date and time, the dispute is closed in the customer's favor. For example, yyyy
-MM
-dd
T
HH
:mm
:ss
.SSS
Z
.
20 - 64
The merchant-proposed offer for a dispute.
The refund details.
The contact details that a merchant provides to the customer to use to share their evidence documents.
An array of all the supporting information that are associated to this dispute.
1 - 100
elementsThe allowed response options for the buyer/seller update actions.