Skip to main content

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 (e.g., amount, date, time, etc.)
  • Status of the dispute in the dispute lifecycle
  • Recommendation on how to resolve the dispute

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
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. Chargeback happens for 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.
disputeStatus

The label for the current stage of a case in the dispute resolution process

Allowed values:

  • NEW - Dispute case received.
  • NEEDS_RESPONSE - Dispute pending documents from you.
  • NEED_ADDITIONAL_INFORMATION - More information requested by J.P. Morgan.
  • ACCEPTED - You accepted the liability.
  • CHALLENGED_JPMC - Dispute challenged on your behalf by J.P. Morgan.
  • UNDER_ISSUER_REVIEW - Dispute has been returned to the issuer for review.
  • CHALLENGED_MERCHANT - Dispute challenged by you.
  • CHALLENGE_DENIED - Case can not be challenged due to no representation rights per network rules.
  • CLOSED - Dispute Cycle complete.
  • EXPIRED - Dispute has expired as due date has passed.
outcome

The outcome of a dispute. For chargebacks this will indicate the financial outcome for you after the dispute is solved. For retrieval requests, this will indicate whether the request have been fulfilled or not.

Allowed Values:

  • PENDING - Final decision/result pending.
  • LOST - You lost dispute and a debit was done on your account for the total dispute amount.
  • WON - You won dispute and your account has been credited back for the total dispute amount.
  • PARTIALLY_WON - You won a partial amount of the disputed funds, and their account has been credited with this portion.
  • FULFILLED - You have fulfilled the retrieval request
  • NOT_FULFILLED - You have not fulfilled the retrieval request.
disputeCategoryCode

The category of the dispute based on the reason code.

  • AUTHORIZATION - Disputes occur when transactions are processed without proper authorization, often due to missing authorization codes or exceeding authorized amounts.
  • CONSUMER_DISPUTE – Dispute raised when consumers challenge transactions due to dissatisfaction with goods/services or unrecognized charges.
  • FRAUD - Involve 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.
issuerDocumentCode

If this is set to 1, expect an issuer document arrival in next few days depending on payment brand. You can check the issuer document availability using our "documents" API endpoint.

Allowed values:

  • 0 - No Chargeback Documentation Provided by issuer.
  • 1 - Supporting document will be provided by issuer.
  • 2 - No Documents required by issuer.
  • 3 - Documents are required by issuer.
  • 4 - Non Receipt of required documents by issuer.
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 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 other related disputes items including data such as:

- disputeId

- disputeType

- disputeValue

- disputeReason

- disputeInitiatedDate

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.merchant.jpmorgan.com/api/v1/disputes/8342472317

Response:

Json
{
  "requestId": "7cf837c4-4dbd-4575-bfce-de2330d6410b",
  "disputeDetails": {
    "disputeType": "FIRST_CHARGEBACK",
    "disputeId": 8342472317,
    "acquirerReferenceNumber": "92681174334685940494146",
    "bankIdentificationNumber": null,
    "disputeValue": {
      "amount": 123,
      "currencyCode": "USD"
    },
    "saleRefundCode": "S",
    "isCurrencyConversion": false,
    "disputeCategoryCode": "PROCESSING_ERROR",
    "disputeReason": {
      "reasonCode": "34",
      "reason": "Point of Interaction Error"
    },
    "disputeReasonDetailed": "Point of Interaction Error",
    "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• Retail: Provide itemized sales slips for each transaction indicated in the issuer documentation\n • Card Not Present: Provide itemized invoice/folio of each transaction indicated in the issuer documentation \n•Credit was issued prior to first chargeback, including posting date and credit receipt.",
    "issuerMemo": null,
    "messageToMerchant": null,
    "disputeInitiatedDate": "2025-06-16",
    "disputeReceivedDate": null,
    "responseDueDate": "2025-06-17",
    "disputeStatus": "NEW",
    "outcome": "PENDING",
    "paymentMethod": {
      "paymentMethodCode": "MC",
      "paymentMethodName": "Mastercard",
      "maskedAccountNumber": "588083XXXXXX8819"
    },
    "issuerDocumentCode": null,
    "transactionDataDetailed": {
      "transactionData": {
        "merchantOrderNumber": "RATE VHFW VI",
        "transactionTimestamp": "2025-05-16T00:00:00Z",
        "transactionAmount": 123,
        "transactionCurrency": "USD"
      },
      "transactionTypeCode": "2"
    },
    "authorizationDataDetailed": {
      "authorizationTimestamp": "2025-05-16T00:00:00Z",
      "authorizationIdentifier": "743646",
      "authorizationReferenceNumber": null,
      "authorizationResponseCode": 100,
      "authorizationAmount": 123,
      "authorizationCurrency": "USD",
      "cavvResponseCode": null,
      "secureIndicator": null,
      "terminalNumber": null,
      "posEntryMode": null
    },
    "fraudNotificationServiceDate": null,
    "merchantDataDetailed": {
      "merchantData": {
        "companyId": "580423",
        "merchantId": "446975",
        "companyName": "9172-4658 QUEBEC INC.",
        "merchantName": "Google                   "
      },
      "merchantCategoryCode": "3415",
      "merchantCountryCode": "US",
      "merchantRegionCode": "0"
    },
    "merchantAccountId": null,
    "relatedItems": [],
    "isReversed": false,
    "caseTimeline": [
      {
        "eventName": "NEW",
        "eventDate": "2025-06-16 18:39:13",
        "eventDetailText": "Dispute Received"
      }
    ]
  },
  "traceId": "80c2721e-2aa8-415b-aa6a-b604cc38e850"
}