The event log lists every webhook Payve created for your account in the current environment. Use it to confirm an event arrived, or to find out why it did not.

Open the event log

Go to Settings → Webhooks and select the Event log tab. Each row shows:

Read the status

Use the filter buttons above the list to show one status at a time. Start with Failed and Dead when something is missing on your side. The retry schedule is in Delivery and retries.

Inspect one delivery

Select View on a row. The dialog shows:
  • Status and Attempts for this event.
  • What we sent: the exact request body Payve posted to your URL.
  • What your endpoint returned: the HTTP status and the start of the response body your server gave.
  • Error, when Payve could not reach your server at all.
Compare What we sent with what your server logged. If the bodies match and your signature check still fails, you are almost always signing parsed JSON, not the raw body. See Verify signatures.
Payve keeps the first 2,000 characters of your server’s response. Do not put secrets in webhook responses.

Common results and their causes

Find the event for one transaction

Every event carries the transaction in data. To match a row to a payment, compare data.public_id (for example pyt_9c2e41b7a05d3f68) in What we sent with the reference shown on the transaction’s own page.

Track events from your code

The same log is available through the API, so you can reconcile without opening the dashboard.
GET /v1/webhooks/events/{id} takes the numeric id from the list, not the evt_ id. Try both requests in the API reference.