Webhooks 不会说谎。

签名、重放保护、重试,直到 2xx。

订阅发票/订单/退款事件。验证端点中的 HMAC-SHA256。 每次交付均经过 HMAC-SHA256 签名、加盖时间戳,并以指数回退方式重试,直到您的端点返回 2xx。

目录

九个事件。订阅全部或一个。

order.paid A buyer's checkout finalised. Settled on-chain.
order.refunded Refund pushed back to the buyer's wallet.
order.delivered Auto-delivery completed - key, file, or webhook handed over.
order.failed Checkout expired or rejected.
product.created Product published from API or dashboard.
product.updated Any field on a product changed.
payout.queued Payout request accepted, broadcast pending.
payout.confirmed Payout confirmed on-chain.
customer.created New buyer email registered in your shop.
标头

什么落在您的端点上

POST /your-endpoint
# Standard headers Sellix sets on every delivery
X-Event-Id:          evt_01J2PT83A5XKJZ5N6FM5YV9B2D
X-Event-Type:        order.paid
X-Webhook-Timestamp: 1779604200
X-Signature:         sha256=8f7a9a2b…
Content-Type:        application/json
User-Agent:          Sellix-Webhook/1.0

# Body - JSON, the resource that fired the event
{
  "id":   "evt_01J2PT83A5XKJZ5N6FM5YV9B2D",
  "type": "order.paid",
  "data": { "order_uuid": "…", "total_cents": 4900, … }
}
交互的

HMAC-SHA256 验证者

粘贴有效负载+秘密。我们使用 Web Crypto API 在您的浏览器中实时计算签名 - 我们的 SDK 在您的服务器上使用相同的算法。

在上面粘贴签名以进行检查。
执行

同样的支票,用您的语言


            

重试政策

  • Up to 8 attempts per delivery
  • Back-off: 1m → 2m → 5m → 15m → 1h → 6h → 24h
  • Any 2xx ends the chain; 4xx / 5xx retries
  • Endpoint dies for 48h straight? We disable it and email the owner.

重播和重复数据删除

  • Reject any timestamp more than 5 minutes off - replay protection.
  • Dedupe by X-Event-Id on your side. Same id twice = same event.
  • A replayed event should also return 200 - it's a feature, not a duplicate.