Skip to main content

​
Event Overview

Event Type: PAYMENT_DISPUTED Category: Dispute
Description: A dispute (chargeback) has been raised or its status has changed This webhook is triggered whenever a dispute or chargeback is raised against a payment, or when the status of an existing dispute changes. Use it to keep your records in sync with the latest chargeback lifecycle state and to act before the response deadline.
The envelope reads PAYMENT_DISPUTED. The X-Webhook-Event header and the top-level event_type are PAYMENT_DISPUTED for every dispute event. The dispute itself is under data, and data.event_type says whether it was just raised (DISPUTE_CREATED) or its status moved (DISPUTE_UPDATED).

​
Merchant Action Required

When you receive a PAYMENT_DISPUTED event, respond before the deadline:
  1. Log in to the EximPe Dashboard.
  2. Open the Chargebacks section.
  3. Locate the dispute using the chargeback_id from the payload.
  4. Upload your supporting documents and submit your response before the reply_before time.
If no response is provided before reply_before, the dispute is automatically closed in the customer’s favour (chargeback_status → CLOSED_CUSTOMER_FAVOUR) and the disputed amount is debited from the merchant.

​
Payload Schema

​
Field Specifications

​
string
required
Always "PAYMENT_DISPUTED" for this webhook event
​
string
required
UTC, no timezone suffix, e.g. "2026-06-11T18:31:02.417755". Parse tolerantly — fractional seconds can be absent.
​
string
required
API version of your account, e.g. "3.0.0"
​
string
required
Unique ID of this event (a UUID, not an ordering counter). A retry resends the same value; use it to de-duplicate.
​
object
required
The dispute. Its fields are listed below.
​
string
Whether the dispute was just raised or its status changed. One of "DISPUTE_CREATED" and "DISPUTE_UPDATED".
​
string
required
Order ID associated with the disputed paymentExample: "OD3842521856"
​
string
required
Payment request ID against which the dispute was raisedExample: "PR1795628984"
​
string
required
Unique identifier for the dispute/chargebackExample: "CB9442851393"
​
string
required
Type of dispute raisedExample: "CHARGEBACK"
​
number
required
Amount under dispute, in the payment currencyExample: 721
​
string
required
Current status of the dispute. One of:Example: "CLOSED_CUSTOMER_FAVOUR"
​
string
required
Timestamp when the dispute was raised, in ISO 8601 formatExample: "2026-06-09T03:53:48+00:00"
​
string
Deadline by which the merchant must submit a response/evidence, in ISO 8601 format. May be null for disputes that are already in a closed stateExample: "2026-06-11T18:30:00+00:00"
​
string
Human-readable reason for the disputeExample: "Goods or Services Not Provided / Not Received"