Webhooks
Endpoints that receive signed events, their deliveries and retries, and the inbound webhooks gateways send.
Webhooks covers both directions, in three tabs.
Endpoints
Your servers that receive signed events.
Choose New Endpoint.
Enter the address (
https://yourapp.com/hooks/payments), a description, optionally one app (otherwise every app of the organization), and the events you want (none ticked = all of them).Save. The signing secret (
whsec_...) is shown once, right after. Put it in your server's configuration.Use Test to send a
pingevent at once and see your server's answer.
Each endpoint shows its health (successes, failures, last status, last error) and how many deliveries are pending or exhausted. Rotate Secret issues a new secret: old signatures stop validating immediately, so deploy the new secret to your server first. Deleting an endpoint removes its delivery history too.
Deliveries
Every event sent to an endpoint, with attempts, next attempt, last status and last error. A delivery that does not get a 2xx answer within 15 seconds is retried after 1 min, 5 min, 30 min, 2 h, 6 h, 12 h, 24 h and 24 h. After eight attempts it is exhausted and waits for you: open it and choose Retry. The delivery page shows the exact payload, your server's last answer and the last 20 attempts.
Inbound
What the gateways sent to REM Payments: each request with its signature check, the events it carried and the result (processed, ignored, duplicate, invalid, failed). Replay runs a stored request again, which is safe: applying the same event twice changes nothing. Replay after fixing a wrong webhook secret on a gateway.
The events, their payloads and signature verification code are in the developer docs: Webhooks.
Last updated 18 Nov 2026