Orsunpay Com Webhooks

generated: '2026-11-06'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.orsunpay.com/webhooks.md
sources:
- https://docs.orsunpay.com/webhooks.md
- https://docs.orsunpay.com/webhook-events.md
- https://docs.orsunpay.com/api-reference/webhooks/refund-failed-event.md
- https://docs.orsunpay.com/api-reference/webhooks/refund-succeeded-event.md
description: OrsunPay delivers webhook events to a merchant‑configured HTTPS endpoint. Each delivery includes an `OrsunPay-Signature` header containing
  a timestamp and HMAC‑SHA256 signature computed with the merchant’s signing secret. Deliveries are retried with exponential backoff for roughly
  31 hours on non‑2xx responses or network failures; events are sent at least once and may arrive out of order, so deduplication must use the
  signed body’s `id`.
events:
- event: transaction.updated
  description: A sale or payout changed status.
- event: refund.succeeded
  description: A refund completed successfully.
- event: refund.failed
  description: A refund failed.
- event: test.ping
  description: A synthetic delivery the merchant triggers to test its receiver; it is not redeliverable and is excluded from endpoint‑health failure
    counts.
- event: cashier.wallet.effect_requested
  description: 'Cashier only: the operator wallet must apply a credit or capture for a cashier operation.'
delivery:
  signature: OrsunPay-Signature header with format `t=<Unix timestamp>,v1=<64 hexadecimal characters>`; HMAC‑SHA256 over the ASCII timestamp,
    a period, and the exact raw body bytes using the merchant’s signing secret.
  retries: Exponential backoff for approximately 31 hours on non‑2xx responses or network failures; deliveries are at‑least‑once and may arrive
    out of order.
docs: https://docs.orsunpay.com/webhooks.md