Payve delivers each event at least once. If your server does not confirm receipt, Payve tries again, up to nine times over about three days.
At-least-once means you will sometimes receive the same event more than once. Your handler must be safe to run twice. See Handle events safely.

What counts as delivered

A 4xx other than 408 or 429 stops retries for that event. Do not answer 400 or 401 for an event you want to receive again. If your handler has a temporary problem, answer 500 or 503.

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-Timestamp and the t in X-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 same id. From the API. You can ask Payve to send a fresh event for a finished transaction:
A resend from the API is a new event. It has a new id, so an event-id check will not recognise it as a duplicate. Its data is also a shorter summary with camelCase field names. Make your handler safe by also checking the transaction’s own state before acting. See Resent events.

If your endpoint was down

  1. Fix the endpoint.
  2. List deliveries with status=failed and status=dead.
  3. Retry them from the dashboard, or fetch each transaction with a GET and reconcile from its status.
Do not rely on webhooks alone. Run a periodic job that fetches any transaction still pending or processing after longer than you expect, and reconcile daily against a statement.