checkout.stalled
A checkout stayed open past the project's window.
When this fires
The hourly sweep found a checkout started more than the project's window ago (checkout_stall_hours, 1 hour by default) with no charge settled for the member and no live membership held, and had not counted a stall for that member in the last day. The row is stamped, the event goes out, and the member enters every running sequence on the stalled_checkout trigger with the plan they were buying, so the step's button reopens that plan; enrollment_id names the first passage opened, or is null when the project runs no such sequence.
Caveats
- A member who starts a checkout three times inside a day stalls once; the two later rows are stamped without an event.
- A stall says nothing about why. Stripe's session may have expired, the member may have changed their mind, or the gateway may have refused the card; the ledger only knows no charge settled.
Related events
payment.pending: the start of the checkout.sequence.enrolled: the passage the stall opened.checkout.recovered: how it ends well.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.
How is this guide?
Last updated on