Skip to main content
Webhooks notify your systems when payments change state. You can receive them two ways: per-payment via a webhook_url, or project-wide via a dashboard endpoint.

​
Endpoints

Register one or more webhook endpoints for the project and choose which events each should receive (or all of them). Orqex then POSTs those events to your endpoint. Each endpoint is created with its own signing secret (whsec_…), shown in the dashboard so you can copy it into your handler. Every delivery to that endpoint is signed with this secret via the x-orqex-signature header — see verifying authenticity.

​
Delivery logs

The dashboard keeps outbound webhook logs: each delivery, its response status and body, and how many attempts it took. Failed deliveries are retried automatically (up to five attempts). Use the logs to debug your handler.

​
Per-payment webhooks

Setting webhook_url when you create a payment intent or checkout delivers that payment’s events to the given URL, in addition to any project endpoints.
Per-payment webhooks (sent to a webhook_url) are not signed — only project endpoints are. For per-payment deliveries, re-fetch the payment from the API to act on its authoritative status. See Webhooks.