Skip to main content
Beta version

Dispute Management API is in the Beta phase.

Dispute Management

Dispute Management

The Dispute Management API is an efficient way to automate and manage your disputes process. This is ideal for conducting near real-time retrieval operations for disputes data, including obtaining a list of disputes, accessing details of specific disputes, retrieving the status of multiple disputes, and obtaining issuer documents. Additionally, performing dispute-related actions such as challenging, fulfilling, and accepting.

Note
  • The Dispute Management API is compatible with all card brands that J.P. Morgan supports.
  • The Dispute Management API supports first chargeback and retrieval request dispute types. For support with any other dispute types, contact your relationship manager.

Availability

The Dispute Management API is available for use in the following regions:

  • United States
  • Canada
  • Europe
Note

Check with your relationship manager for any applicable restrictions.

How disputes work

Flow diagram of a typical dispute lifecycle
  1. Your consumer contacts the card issuer to dispute a transaction.
  2. The card issuer researches, confirms dispute eligibility, and submits the dispute to the payment brand.
  3. The payment brand electronically screens the dispute for technical compliance and forwards it to J.P. Morgan (Acquirer).
  4. We receive the dispute and perform one of the following actions:
    • Resolve the issue, return it to the payment brand (skip to step 6), and notify you.
    • Forward the issue to you for further analysis.
  5. You can then determine if the dispute is valid and perform one of the following actions:
    • If valid, send a response to us to accept the dispute.
    • If not valid, send the dispute back to us with supporting documentation to return to the issuer as a representment.
  6. We forward the item (accepted or represented) to the payment brand.
  7. The payment brand electronically screens the item for technical compliance and forwards it to the issuer.
  8. The issuer receives the item, reviews it, and performs one of the following actions:
    • If you accept the dispute, the consumer is notified accordingly.
    • If you respond with a representment and the issuer agrees, the consumer is notified accordingly.
    • If you respond with a representment and the issuer does not agree, the dispute continues and a second dispute is submitted (PRE_ARBITRATION). The cycle repeats.

First chargeback

Retrieval request

Documentation parameters