Version - 2.4
{
"eventType": "DISPUTE.STATUS",
"version": "2.4",
"type": "DISPUTE",
"status": "CHALLENGED",
"primerAccountId": "acct_123456789",
"transactionId": "txn_987654321",
"orderId": "order_12345",
"paymentId": "pay_67890",
"paymentMethod": {
"type": "CARD",
"card": {
"network": "VISA",
"last4": "1234",
"expiry": "12/25"
}
},
"processor": "ADYEN",
"processorDisputeId": "dispute_123456789",
"receivedAt": "2025-09-23T13:00:00Z",
"challengeRequiredBy": "2025-10-07T13:00:00Z",
"reason": "Fraudulent transaction",
"reasonCode": "4800",
"processorReason": "Chargeback reason code 4800",
"amount": 1000,
"currency": "GBP",
"merchantId": "merchant_12345"
}
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 Adyen, Airwallex, Braintree, Checkout.com, PayPal, Stripe & Worldpay.
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.
Version - 2.4
{
"eventType": "DISPUTE.STATUS",
"version": "2.4",
"type": "DISPUTE",
"status": "CHALLENGED",
"primerAccountId": "acct_123456789",
"transactionId": "txn_987654321",
"orderId": "order_12345",
"paymentId": "pay_67890",
"paymentMethod": {
"type": "CARD",
"card": {
"network": "VISA",
"last4": "1234",
"expiry": "12/25"
}
},
"processor": "ADYEN",
"processorDisputeId": "dispute_123456789",
"receivedAt": "2025-09-23T13:00:00Z",
"challengeRequiredBy": "2025-10-07T13:00:00Z",
"reason": "Fraudulent transaction",
"reasonCode": "4800",
"processorReason": "Chargeback reason code 4800",
"amount": 1000,
"currency": "GBP",
"merchantId": "merchant_12345"
}
Version - 2.4
{
"eventType": "DISPUTE.STATUS",
"version": "2.4",
"type": "DISPUTE",
"status": "CHALLENGED",
"primerAccountId": "acct_123456789",
"transactionId": "txn_987654321",
"orderId": "order_12345",
"paymentId": "pay_67890",
"paymentMethod": {
"type": "CARD",
"card": {
"network": "VISA",
"last4": "1234",
"expiry": "12/25"
}
},
"processor": "ADYEN",
"processorDisputeId": "dispute_123456789",
"receivedAt": "2025-09-23T13:00:00Z",
"challengeRequiredBy": "2025-10-07T13:00:00Z",
"reason": "Fraudulent transaction",
"reasonCode": "4800",
"processorReason": "Chargeback reason code 4800",
"amount": 1000,
"currency": "GBP",
"merchantId": "merchant_12345"
}
Headers
An HMAC signature generated using the webhook payload and a shared signing secret. This is then converted to a base64 encoded string.
Body
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.
The type of dispute event. More information on what the type field represents can be found in Manage disputes
RETRIEVAL, DISPUTE, PREARBITRATION To see which statuses are applicable for a dispute type, and how we map status, please see Manage disputes.
OPEN, ACCEPTED, CHALLENGED, EXPIRED, CANCELLED, WON, LOST 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.
The 3-letter currency code in ISO 4217 format. e.g. use USD for US dollars.
Response
Return a 200 status to indicate that the data was received successfully