---
title: "Dispute Status"
method: POST
path: "/dispute-status"
tags: ["Dispute & Chargebacks Webhooks"]
---

# Dispute Status

`POST /dispute-status`

Primer notifies you with a `DISPUTE.STATUS` webhook that will provide information on retrievals, disputes (also known as chargebacks), and preabritration filings.

This notification is supported for processors Adyen, Braintree, Checkout.com & PayPal.

The `DISPUTE.STATUS` event can be used to proactively communicate with customers, issue refunds, send disputes to risk tools, or to proactively defend disputes.

The `DISPUTE.STATUS` event is currently in an open beta stage, as we continue to add more processors.

Learn more about [managing disputes at Primer](/docs/disputes/manage-disputes).

## Headers

- `X-Signature-Primary` string, required
- `X-Signature-Secondary` string, required

## Request body

- DisputeStatusWebhookPayload
  - `eventType` string, required — The type of event that triggered the webhook. This will have the value `DISPUTE.STATUS`. This indicates that a dispute notification was issued through a configured connection. Use these notifications to proactively communicate with your customer, issue refunds, or submit evidence to challenge disputes.
  - `version` string — The payload version
  - `type` 'RETRIEVAL' | 'DISPUTE' | 'PREARBITRATION', required — The type of dispute event. More information on what the `type` field represents can be found in [Manage disputes](/docs/disputes/manage-disputes)
  - `status` 'OPEN' | 'ACCEPTED' | 'CHALLENGED' | 'EXPIRED' | 'CANCELLED' | 'WON' | 'LOST', required — To see which statuses are applicable for a dispute `type`, and how we map `status`, please see [Manage disputes](/docs/disputes/manage-disputes).
  - `primerAccountId` string, required — A unique identifier for your Primer merchant account.
  - `transactionId` string — A unique identifier for the Primer transaction corresponding to this dispute.
  - `orderId` string, required — Your reference for the sale transaction that the dispute relates to.
  - `paymentId` string, required — A unique identifier for the Primer payment corresponding to this dispute.
  - `paymentMethod` object, required — The payment method information for the payment that is now disputed.
    - `paymentMethodType` string — [The list of available payment methods and their `PAYMENT_METHOD_TYPE` can be found here.](https://primer.io/docs/connections/payment-methods/available-payment-methods)
    - `paymentMethodData` object
      - `network` 'AMEX' | 'DANKORT' | 'DINERS_CLUB' | 'DISCOVER' | 'ENROUTE' | 'ELO' | 'HIPER' | 'INTERAC' | 'JCB' | 'MAESTRO' | 'MASTERCARD' | 'MIR' | 'PRIVATE_LABEL' | 'UNIONPAY' | 'VISA' | 'CARTES_BANCAIRES' | 'OTHER' — The list of available card networks.
  - `processor` 'ADYEN' | 'BRAINTREE', required — The payment processor that you submitted a payment to, and received a dispute notification from.
  - `processorDisputeId` string, required — An identifier for this dispute provided by the processor. This is shared across multiple dispute `type` and `status` relating to the same payment. e.g. as an `open` dispute that is later challenged will share a `proccessorDisputeId`.
  - `receivedAt` string, date-time, required — Date and time at which Primer received the processor's dispute event. Provided as an ISO timestamp in UTC.
  - `challengeRequiredBy` string, date-time, required — Time by which the merchant must challenge a dispute. This is provided by the processor, where available.
  - `reason` string — Primer's unified reason that explains why the dispute was raised. This should not vary across processors for the same dispute `reasonCode`, unlike the `processorReason`.
  - `reasonCode` string, required — The dispute reason code for a dispute. This will be the same code provided by the card schemes.
  - `processorReason` string — The dispute reason provided by the processor. This can vary across processors for the same dispute `reasonCode`, which is why we provide a unified field - `reason`.
  - `amount` integer, required — The disputed amount. Note: this is not always the same as the payment amount. This will be displayed in minor units. e.g. for $7, use `700`. Some currencies, such as Japanese Yen, do not have minor units. In this case you should use the value as it is, without any formatting. For example for ¥100, use `100`.
  - `currency` string, required — The 3-letter currency code in [ISO 4217 format](https://en.wikipedia.org/wiki/ISO_4217#Active_codes). e.g. use `USD` for US dollars.
  - `merchantId` string — The merchant ID registered at the payment processor used for this dispute.

## Response `200`

Return a 200 status to indicate that the data was received successfully

---

[API](https://skmtc.dev/primer/apis/primer-webhooks.md) · [All operations](https://skmtc.dev/primer/apis/primer-webhooks/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/primer/primer-webhooks/revisions/f4be9122322f/schema)