Webhook event: payment.disputed

When it fires

payment.disputed is emitted when a payment is disputed (e.g. an indemnity claim). A redelivery of the same occurrence carries the same event id.

If your endpoint does not return a 2xx within the timeout, delivery is retried on an exponential backoff schedule — see Webhook delivery and retries. Design your handler to be idempotent so a redelivered event is safe to process twice.

Example delivery

{
  "id": "evt_PAYM9Z",
  "type": "payment.disputed",
  "created": "2026-07-05T12:00:00Z",
  "livemode": true,
  "api_version": "2026-07-01",
  "data": {
    "object": {
      "id": "pay_7M3X1",
      "status": "disputed",
      "dispute_reason": "indemnity_claim"
    }
  }
}

Handling it

A common handler will flag the account for review and pause dunning. Verify the signature, acknowledge with 200 within 10 seconds, then work asynchronously. Guard against out-of-order delivery using the created timestamp, and re-fetch the resource from the API if you need its live state.