What counts as delivered
Retry schedule
Each failed attempt schedules the next one.
After the ninth failure the event is marked
dead and Payve stops trying.
Retries are sent by a scheduled job, so an attempt goes out at or shortly after its time, not to the second.
What stays the same across retries
- The event
id. - The body.
What changes on each retry
X-Payve-Timestampand thetinX-Payve-Signature. Each attempt is signed afresh, so a retry always passes a five-minute timestamp check.
Delivery statuses
See what happened
List deliveries and inspect one:GET /v1/webhooks/events/{id} takes the numeric id and returns the exact request Payve sent and the response your server gave.
Payve keeps the first 2,000 characters of your server’s response so you can debug a rejected
delivery. Do not put secrets in webhook responses.
lastError values you may see:
Send an event again
From the dashboard. Open Settings → Webhooks, find the delivery and select Retry. This re-sends the same event with the sameid.
From the API. You can ask Payve to send a fresh event for a finished transaction:
If your endpoint was down
- Fix the endpoint.
- List deliveries with
status=failedandstatus=dead. - Retry them from the dashboard, or fetch each transaction with a
GETand reconcile from its status.

