{
  "eventId": "6762a9f4a6a3327c34cdce48",
  "eventType": "intent.disputed_won",
  "eventTime": 1734519284711,
  "intentId": "67629e77c20feb77fc4cbd0b",
  "metadata": {
    "orderId": "12345",
    "customerNote": "Deliver after 5 PM"
  }
}

{
  "eventId": "6762a9f4a6a3327c34cdce48",
  "eventType": "intent.disputed_won",
  "eventTime": 1734519284711,
  "intentId": "67629e77c20feb77fc4cbd0b",
  "metadata": {
    "orderId": "12345",
    "customerNote": "Deliver after 5 PM"
  }
}
​
eventId
string

A unique identifier for this specific event. This ensures that each event can be tracked and processed individually.

​
eventType
string

Describes the type of event. In this case, it signifies that a payment intent has been successfully won the dispute in favor of the merchant.

​
eventTime
integer

The timestamp when the event was generated, typically in milliseconds since the Unix epoch (January 1, 1970). This value can be used to track when the event occurred.

​
intentId
string

A unique identifier for the specific payment intent that was refunded. This ID ties the event back to the transaction or payment process that triggered the refund.

​
metadata
object

A collection of key-value pairs that were provided when the object was created. These metadata values are echoed back in the response, allowing you to store and retrieve custom information such as context-specific attributes, references, or tags. This can be useful for correlating records in your system or attaching meaningful context to transactions.

Was this page helpful?