---
title: "A charge settled for a member whose checkout had stalled."
method: POST
path: "checkout.recovered"
tags: ["checkout.* events"]
---

# A charge settled for a member whose checkout had stalled.

`POST checkout.recovered` (webhook)

### When this fires

The payment ledger recorded a successful charge for the member, through any door and on any rail, while one of their checkouts stood stalled. Every open checkout of the member closes on that charge; the event fires for each one that had stalled, with the charge and the membership it became, and the passage that was running when they came back. The passage itself ends as `sequence.converted` through the same charge.

### Caveats

- The charge need not be for the stalled plan: a member who stalled on the monthly plan and bought the annual one is recovered all the same.
- A member who holds a live membership before the window passes never stalls, so never recovers; their checkouts close without an event.

### Related events

- `checkout.stalled`: the stall this recovers.
- `payment.succeeded`: the charge.
- `sequence.converted`: the passage ending as a win on the same charge.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'checkout.recovered', required: The event name, always `checkout.recovered` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `checkout_id` string, uuid, required: The ledger row `checkout.stalled` named.
    - `subscriber_id` string, uuid, required: The member's project-scoped user id.
    - `plan_id` string, uuid, nullable, required: The plan the stalled checkout was for; the charge may have bought another.
    - `provider` string, required: The rail the stalled checkout opened on, not necessarily the one that settled.
    - `surface` 'portal' | 'bot', required: Where the stalled checkout started.
    - `payment_id` string, uuid, required: The charge that completed it.
    - `subscription_id` string, uuid, required: The membership the charge belongs to.
    - `enrollment_id` string, uuid, nullable, required: The passage that was running when the member came back, or `null`.
    - `stalled_at` string, date-time, required: When the stall was counted.
    - `recovered_at` string, date-time, required: When the charge settled.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: 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.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)