Podpisannye, s zashchitoi ot replay i povtorami do vashego 2xx.
Podpishites na invoice / order / refund events. Proveryaite HMAC-SHA256 na svoem endpoint. Kazhdaya dostavka podpisana HMAC-SHA256, imeet timestamp i povtory s exponential back-off do otveta 2xx.
order.paid
A buyer's payment was accepted.
order.failed
Payment or checkout processing failed.
order.refunded
The order was fully refunded.
delivery.completed
A line item was delivered successfully.
delivery.failed
A line-item delivery failed.
# Standard headers Sellix sets on every delivery X-Sellix-Event-Id: 7a2327ba-8655-45b4-a768-13e2112b2556 X-Sellix-Event: order.paid X-Sellix-Signature: 8f7a9a2b… Content-Type: application/json # The exact raw body covered by X-Sellix-Signature { "id": "7a2327ba-8655-45b4-a768-13e2112b2556", "object": "event", "event": "order.paid", "created_at": "2026-05-26T07:14:22Z", "data": { "order": { "uuid": "…", "total_cents": 4900, … } } }
Vstavte payload i secret. My schitaem signature v browser cherez Web Crypto API - tot zhe algoritm, chto v SDK.
6 attempts per delivery10s → 30s → 2m → 10m → 1hX-Sellix-Signature against the exact raw request body.X-Sellix-Event-Id. Retries keep the same id and body.200 - it's a feature, not a duplicate.