Webhook Signature
- Secured with HMAC-SHA256 signature.
- Sezzle-Signature header contains a hash of the webhook body, generated using the merchant private key.
- Always verify the signature matches the webhook data to confirm it originates from Sezzle.
Webhook Event Payload
- Options
- Template
Unique identifier for the webhook event.
Timestamp (ISO 8601) when the event was generated.
Type of the eventAvailable options:
customer.tokenized, order.authorized, order.captured, order.refunded, dispute.merchant_input_requested, dispute.deadline_approaching, dispute.closed.customer_win, dispute.closed.merchant_win, dispute.closed.neutralType of data associated with the event.Available options:
customer, order, disputePayload data specific to the event type. See options in the applicable accordion below.
Examples per Event
customer.tokenized
customer.tokenized
order.authorized
order.authorized
order.captured
order.captured
order.refunded
order.refunded
Note on the
source field:- If the value is
"dashboard", it’s initiated from the merchant dashboard - If the value is
"gateway", it’s via the gateway API
dispute
dispute
The following applies to the following webhooks:
dispute.merchant_input_requesteddispute.deadline_approachingdispute.closed.customer_windispute.closed.merchant_windispute.closed.neutral
Webhook Acceptance and Retries
- Considered delivered upon receiving an HTTP 200 Status OK response.
- Non-200 responses trigger retries:
- Multiple attempts in the first hour.
- A few attempts throughout the day.
- Final attempts one day and three days later, spanning five days total.
- If the final retry fails, the webhook subscription is deleted for all events.
- To resume receiving webhooks, recreate the webhook.
- Webhooks may not arrive in chronological order, as new ones can be sent before retries of older ones.
- Retried webhooks use the current merchant private key for signing, so the signature may differ from the original if the key has changed.