Webhooks
Endpoints for payment events across all your merchants.
Partners do not register webhooks via the API. Share your HTTPS URL(s) and signing secret(s) with Orqpay (test and/or live). Platform admin configures delivery for you.
You can have multiple endpoints per environment. Each receives matching events for all of your merchants (fan-in), with its own secret and event groups.
When to fulfill
| Event | Action |
|---|---|
invoice.paid | Fulfill / credit your user |
Other invoice.* | Log or wait — do not treat as fulfillment |
Process each event once using the envelope id. Retries reuse the same id.
What’s in the payload
Each delivery includes:
partnerId— your partner accountmerchantId— which merchant was paidpaymentId— the payment to fulfill- amounts,
referenceId, and status fields
Full event list, event groups, and verify steps: Merchant webhooks.
Verify
X-Orqpay-Signature: t=<unix_seconds>,v1=<hmac_hex>Use the webhook secret Orqpay configured for that endpoint (orq_whsec_… when platform-minted) — not your orq_ps_… API signing secret.
Same verify pattern as merchants: HMAC over {timestamp}.{rawBody}, 5-minute window, raw body only.
Next
- Merchant webhooks — event groups, full table, Node example
- Payments