Webhooks

Webhooks let Paysio push events to your own server the moment they happen, so your systems react automatically instead of polling for changes. When a payment completes, a subscription renews, or an order ships, Paysio sends a request to a URL you provide. You set this up in Settings > Webhooks. As with API keys, managing webhooks needs an owner or developer role.

Creating an endpoint

An endpoint is a URL on your server that Paysio sends events to.

Enter the URL where you want events delivered.
Select the events you want to receive. Choose only the ones you will act on.
Create the endpoint. Paysio shows you a signing secret once. Copy it and store it safely, since you will need it to verify incoming events and cannot see it again later.

You can turn an endpoint active or inactive, edit its URL or event list, and delete it at any time from the same page.

Choosing events

You subscribe each endpoint to specific events, grouped by area:

Payments: completed, refunded, voided, failed, and disputed.
Payouts: created, updated, paid, and failed.
Subscriptions: created, scheduled, activated, renewed, cancel scheduled, cancelled, paused, and resumed.
Orders: fulfilled and cancelled.

Subscribing to only the events you need keeps your endpoint from being sent noise it does not use.

Verifying signatures

Because anyone could send a request to your URL, you should confirm each delivery genuinely came from Paysio. Every endpoint has a signing secret, and Paysio signs each event with it. Your server uses that secret to check the signature on an incoming request, and rejects anything that does not match. This is what stops a bad actor from faking events. The exact verification steps are in the developer docs.

Delivery history

Paysio keeps a record of what it sent to each endpoint. Expand an endpoint to see its recent deliveries, each showing the event type, the HTTP status code your server returned, how many attempts were made, and the response body. If a delivery fails, Paysio retries it, and the attempt count and responses let you see exactly what went wrong so you can fix your endpoint.

Next steps

This page manages where events go. For the shape of each event and its data fields, see the event payload reference in the developer documentation at /docs.