Skip to main content

Webhook Test Events, Delivery Log and Re-sending

Partners can now send a test event to a webhook, browse every delivery made to it with the response their endpoint gave, and re-send a delivery that failed. Any 2xx status code now counts as a successful delivery.

Send test event​

From the webhook's actions menu in the Partner Portal, Send test event posts a sample event of a subscribed type to the endpoint and shows the status code, response body and response time — or the reason no response came back.

Test events have the same shape and headers as real events, are signed with the webhook's HMAC key over the same fields, and carry fake values (references starting with TEST). A test event is sent once and never affects payments.

Delivery log​

Deliveries lists every delivery for a webhook, filterable by status, event type, date range, and external transaction ID or merchant reference. Each delivery shows the body that was sent and every attempt with its response.

Re-send a failed delivery​

A failed delivery can be re-sent from its detail page. A re-send is a new delivery of the same event, signed with the webhook's current HMAC key, sent once straight away, and linked to the original in the log; the portal shows whether the endpoint accepted it. Your endpoint may receive an event it has already processed, so handle events idempotently.

2xx is success​

Previously only 200 was treated as success; 201, 202, 204 and other 2xx responses were retried. They are now recorded as successful deliveries.

See Testing, delivery log and re-sending in Delivery and retries.