{
  "eventId": "whe_fooD944t4VUKkaDT",
  "eventType": "intent.failed",
  "eventTime": 1729608043615,
  "intentId": "in_fooBOwYsaK50AEfK",
  "status": "FAILED",
  "amount": 5000,
  "currency": "USD",
  "errorCode": "insufficient_funds",
  "metadata": {
    "orderId": "12345",
    "customerNote": "Deliver after 5 PM"
  }
}

{
  "eventId": "whe_fooD944t4VUKkaDT",
  "eventType": "intent.failed",
  "eventTime": 1729608043615,
  "intentId": "in_fooBOwYsaK50AEfK",
  "status": "FAILED",
  "amount": 5000,
  "currency": "USD",
  "errorCode": "insufficient_funds",
  "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 is failed.
​
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. This ID ties the event back to a particular transaction or payment process that triggered the event.
​
status
string
Represents the current status of the payment intent. For this event, the status will be FAILED.
​
amount
integer
The amount involved in the transaction, typically expressed in the smallest unit of the currency. Here, 5000 represents 50.00 USD (because USD typically uses two decimal places).
​
currency
string
The currency used for the transaction. In this case, it is United States Dollars (USD).
​
errorCode
string
A specific code indicating the reason for the payment failure. This helps identify whether the failure was due to user error or processing error. For a complete list of error codes and their meanings, see our Error Codes documentation.
​
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.