Can a delivery be traced after the fact?
Event detail keeps the core metadata, the last delivery information, the linked order and transaction references, and the request and response payloads in a JSON viewer. The calls list records each attempt with its creation date, result, signature and timestamp. Resent events live in their own view, so a redelivery stays distinguishable from the original.
In detail
Yes. Every event generated on a transaction, checkout or batch flow is recorded in Payment Events, and every delivery attempt stays on record.
What the event detail keeps
- The core metadata of the event and the last delivery information.
- The linked order and transaction references.
- The request and response payloads, in a JSON viewer.
- The calls list, with each attempt's creation date, result, signature and timestamp.
- The webhook endpoint that handled the delivery.
From one event, your merchants move to the endpoint configuration to check settings, or to the order to see the full transaction context. Searches work by transaction, status, period or webhook, so an investigation starts from what the merchant knows.
When a delivery failed, the event can be resent from the table, the context menu or the event detail, individually or in a batch. The resend replays the original payload with its original signature, and the payment logic behind it is not re-executed: a refund that failed to notify a downstream system is notified again, not processed again.
Resent events live in their own view, so a redelivery stays distinguishable from the original. Your support team gets a complete history of what was sent, what came back and what was done about it, without relying on assumptions.