A unique identifier for this specific event. This ensures that each event can be
tracked and processed individually.
Describes the type of event. In this case, it signifies that a payment intent has
been successfully refunded.
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.
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.
Represents the current status of the payment intent. For this event, the status
will be
REFUNDED
.The refunded amount for the transaction, typically expressed in the smallest unit
of the currency. Here, 10000 represents 100.00 USD (because USD typically uses
two decimal places).
The currency used for the refunded transaction. In this case, it is United States
Dollars (USD).
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.