Webhooks

Developers

The endpoints we call when an event happens at your end — a completed payment, a failed payout, an opened dispute.

Without an endpoint, your integration has to poll the platform. With one, outcomes are pushed to you, signed.

Adding an endpoint

An https URL, and the list of events you care about. No event ticked = all of them.

The signing secret is shown once only, at creation.

Rotating a secret without breaking anything

It is a two-step manoeuvre, and that is deliberate:

1. Rotate adds a second secret. Both are valid — your endpoint has time to accept the new one.
2. Promote makes the new one the only valid secret.

Only promote once your endpoint can accept the new secret. Deliveries signed with the old one stop being verifiable immediately.

A promoted secret is no longer readable here. Lost, it is rotated — it is not recovered.

Checking

Send a test event makes a real delivery to your active endpoints and shows the response code and the duration. If nothing is subscribed to the event, the screen says so rather than letting you think it succeeded.

Pause stops deliveries without deleting the configuration.

The delivery-by-delivery detail is in Developer logs; the message format is described in the Webhooks guide.

— /dashboard/webhooks