Optimization Protection

Retrieve detailed dispute information

To obtain additional information to assist you in your dispute management process, you can send a GET request to the /disputes/{disputeId} endpoint to retrieve detailed information on a given dispute, such as:

Transaction specifics (amount, date, time, etc.)
Status of the dispute in the dispute lifecycle
Resolution recommendation for the dispute

For pre-arbitration availability, refer to pre-arbitration availability.

Important request fields

Important required request fields
Request field name	Description	Required	Location
`disputeId`	Unique identifier of a dispute provided by J.P. Morgan.	Y	Path parameter
`platform-id`	Use this ID to identify the platform sending the API request.	N	Header
`merchant-id`	Unique processing entity identifier	Y	Header
`request-id`	Unique request identifier provided by the requestor in the request header.	Y	Header

Important response fields

Important disputeDetails response fields
Response field name	Description
`isReversed`	Indicates whether the dispute is reversed.
`disputeReasonDetailed`	Textual detailed description of the chargeback reason for the disputed case. Chargeback is the monetary value of the transaction amount that is reclaimed from you. Chargebacks happen for a variety of reasons and some common reasons are customer dispute, fraud, processing error, and authorization issues.
`messageToMerchant`	Provides textual information of the instruction from the dispute analyst to assist you to resolve the dispute. This is a free form field.
`disputeType`	Category of an inquiry or disagreement related to a payment transaction on a consumer payment account. Allowed values: `FIRST_CHARGEBACK` - This is the initial stage where the consumer disputes a transaction. The consumer contacts their bank or credit card issuer to report an issue, such as fraud, a billing error, or a product/service problem. `RETRIEVAL_REQUEST` - A retrieval request, also known as a "soft chargeback" or "request for information," is a preliminary step in the dispute process where the consumer's bank requests additional information about a transaction from you. This request is typically initiated when a consumer questions a transaction on their statement but has not yet formally disputed the charge. `PRE_ARBITRATION` - Pre-arbitration occurs after you challenge a chargeback and the issuer disagrees with the representment. Each pre-arbitration exists as a separate dispute record with a reference to the related chargeback.
`responseDueDate`	Due date for challenging the dispute, in YYYY-MM-DD format. For pre-arbitration, refer to the pre-arbitration response due date.
`disputeStatus`	The label for the case's current stage in the dispute resolution process. Valid status values depend on the dispute type. Refer to the specific dispute type page for supported statuses and lifecycle transitions.
`outcome`	The outcome of a dispute. For chargebacks, this indicates your financial outcome after the dispute is resolved. For retrieval requests, this indicates whether the request was fulfilled. For pre-arbitration, this indicates whether liability was accepted or contested.
`disputeCategoryCode`	The category of the dispute based on the reason code. `AUTHORIZATION` - Dispute occurs when transactions are processed without proper authorization, often due to missing authorization codes or exceeding authorized amounts. `CONSUMER_DISPUTE` – Dispute raised when consumer challenges a transaction due to dissatisfaction with goods/services or unrecognized charges. `FRAUD` - Involves unauthorized transactions, typically due to stolen card information or identity theft. `PROCESSING_ERROR` - Result from mistakes in transaction processing, such as incorrect amounts or duplicate charges.
`issuerDocumentExpected`	If this is set to true, expect an issuer document arrival in next few days depending on payment brand. Allowed values: `true` - The issuer provides chargeback documentation. `false` - The issuer does not provide chargeback documentation.
`issuerDocumentReceived`	If this is set to true, an issuer document was received from the payment brand. Allowed values: `true` - We received the issuer documents. Check the issuer document availability using our Get dispute documents endpoint. `false` - We did not receive the issuer documents.
`transactionId`	Use this ID to identify the transaction that is being disputed.
`submitterPlatformId`	Use this ID to identify the facilitator of the transaction that is being disputed.
`potentialRemedies`	Provides textual information about the recommended actions and supporting documentation required to address and resolve a dispute. This includes providing a detailed letter of explanation about the transaction, evidence of any corrective actions taken, and relevant documentation to substantiate the validity of the transaction. Examples of supporting evidence may include transaction receipts, proof of delivery, authorization logs, and any correspondence with the consumer. The attribute serves as a guide for you to compile necessary information to effectively challenge a dispute and demonstrate compliance with transaction terms and conditions.
`caseTimeline`	Provides a chronological timeline of all events that occurred in a specific dispute case. Each event in the list has an `eventName`, `eventDate` and `eventDetailText`.
`transactionDataDetailed`	Contains detailed information about a sale or refund transaction, including data such as: `transactionData` `transactionTypeCode`
`authorizationDataDetailed`	Contains detailed information about transaction authorization, including data such as: `authorizationTimestamp` `authorizationIdentifier` `authorizationReferenceNumber` `authorizationResponseCode` `authorizationAmount` `authorizationCurrency` `cavvResponseCode` `secureIndicator` `terminalNumber` `posEntryMode`
`relatedItems`	Contains information about related dispute records. For a pre-arbitration case, use relatedItems to identify the associated chargeback dispute and any other related dispute records.

HTTP method: GET

Endpoint: /disputes/{disputeId}

Scenario: Get additional details about a dispute by providing the dispute case id.

Since this is a GET request, there is no request body. The URL for a server request looks like the following:

Plaintext

https://api.payments.jpmorgan.com/commerce/v1/disputes/82895

Response:

Json

{
  "requestId": "e2176959-3596-40b4-bfbf-a4c1681d4c36",
  "disputeDetails": {
    "disputeType": "FIRST_CHARGEBACK",
    "disputeId": 82895,
    "acquirerReferenceNumber": "55432865189100456272466",
    "disputeValue": {
      "amount": 4,
      "currencyCode": "USD"
    },
    "saleRefundCode": "S",
    "isCurrencyConversion": false,
    "disputeCategoryCode": "PROCESSING_ERROR",
    "disputeReason": {
      "reasonCode": "59",
      "reason": "NO-SHOW, ADDENDUM OR ATM DISPUTE"
    },
    "disputeReasonDetailed": "No Show, Addendum or ATM Dispute",
    "potentialRemedies": "Provide a letter of explanation detailing the transaction and any attempts to remedy the dispute in addition to providing evidence of the following: \n• Credit was issued prior to first chargeback, including posting date and credit receipt\n• Folio/sales slip showing transaction was not a no show charge or an addendum to a previously valid transaction\n • Proof business has no record of a cancellation from the cardholder\n • Proper disclosure was given to cardholder that there would be a no-show fee if reservation was not cancelled before 6 p.m. local time on the day of the reservation period \n• If transaction involves loss, theft or damage, provide proof of card present\n•Credit was issued prior to first chargeback, including posting date and credit receipt",
    "disputeInitiatedDate": "2025-07-10",
    "responseDueDate": "2025-07-28",
    "disputeStatus": "EXPIRED",
    "statusUpdateTimestamp": "2025-07-10T16:02:31Z",
    "issuerDocumentCode": 1,
    "issuerDocumentExpected": false,
    "issuerDocumentReceived": false,
    "paymentMethod": {
      "paymentMethodCode": "MC",
      "paymentMethodName": "Mastercard",
      "maskedAccountNumber": "520470XXXXXX9500"
    },
    "transactionDataDetailed": {
      "transactionData": {
        "merchantOrderNumber": "KkQgei5VJJg94ofLkvXTEC",
        "transactionTimestamp": "2025-07-08T04:00:00Z",
        "transactionAmount": 4,
        "transactionCurrency": "USD",
        "transactionId": "adaf45c4-03c4-49ca-881c-d300bcd0b050",
        "submitterPlatformId": "2567582045"
      },
      "transactionTypeCode": "7"
    },
    "authorizationDataDetailed": {
      "authorizationTimestamp": "2025-07-08T00:00:00Z",
      "authorizationIdentifier": "tst301",
      "authorizationResponseCode": 100,
      "authorizationAmount": 4,
      "authorizationCurrency": "USD",
      "secureIndicator": false,
      "terminalNumber": "9",
      "posEntryMode": "81"
    },
    "merchantDataDetailed": {
      "merchantData": {
        "companyId": "25887313631",
        "merchantId": "997241028650",
        "companyName": "Barker Mobility Equipments",
        "merchantName": "LA-US Safetech Fraud"
      },
      "merchantCountryCode": "USA"
    },
    "relatedItems": [],
    "isReversed": false,
    "caseTimeline": [
      {
        "eventName": "NEW",
        "eventDate": "2025-07-10 16:00:33",
        "eventDetailText": "Dispute Received"
      },
      {
        "eventName": "NEW",
        "eventDate": "2025-07-10 16:00:33",
        "eventDetailText": "Dispute Received"
      },
      {
        "eventName": "EXPIRED",
        "eventDate": "2025-07-10 16:02:31",
        "eventDetailText": "Dispute has expired as due date has passed"
      }
    ]
  },
  "traceId": "5dc20f52-8b33-454a-be69-e971accb8ecb"
}

Get dispute documents endpoint

Pre-arbitration availability

Pre-arbitration response due date

Retrieve detailed dispute information

Important request fields

Important response fields

Related