Webhooks
Payload
All our dispute webhooks follow this structure:
{
"source": "",
"id": "event_20240619XYZabcdefghij",
"type": "DISPUTE_ACTION_REQUIRED",
"subject": "dispute_abcDEF1234567890Ghijk",
"time": "2025-10-23T10:15:30Z",
"specversion": "0.0.1-SNAPSHOT",
"datacontenttype": "application/json",
"data": {
"eventId": "event_20240619XYZabcdefghij",
"disputeId": "dispute_abcDEF1234567890Ghijk",
"paymentChargeId": "charge_9ZyXwVuT76543210AbCd",
"merchantPaymentReference": "txp_*****"
}
}Configuration
Setting Up Your Endpoint
A webhook endpoint needs to be provided to PPRO.
Webhook Types
These are the core Dispute Events that can be received:
| Type | Details |
|---|---|
| DISPUTE_ACTION_REQUIRED | New dispute created |
| DISPUTE_ACCEPT_PROCESSING | You accepted the dispute |
| DISPUTE_CHALLENGE_PROCESSING | You challenged with evidence |
| DISPUTE_UNDER_REVIEW | Provider/Consumer reviewing the evidence |
| DISPUTE_WON | Dispute resolved in merchant's favor |
| DISPUTE_LOST | Dispute resolved in consumer’s favor |
Updated about 2 hours ago