Accept payments webhooks

checkout_in_progress

The checkout_in_progress webhook is sent when the checkout lifetime reaches its expiration while the latest payment is awaiting buyer action or has been submitted for processing.

Banking payment methods are typical examples where this webhook can be sent, as the payment processing can take several days depending on the bank processing times.

postWebhookcheckout_in_progress

Headers

Getpaid-Trace-Idstring required

Example:96ce50247f87f540bb2d86771b3728b8

The trace identifier for the request. It is a good idea to log this and provide it with any support requests

Payload

idstring id required

The unique identifier of the event.

type'checkout_in_progress' required

The type of event.

version'v2' required

The version of the event type.

occurred_atstring date-time required

UTC timestamp in ISO 8601 format with milliseconds (RFC 3339). Always includes the 'Z' UTC indicator.

Example payload

{
  "id": "evt_4a4m2pjycdb1jbj68h1rvk9kcz",
  "version": "v2",
  "occurred_at": "2025-09-01T22:05:48.479Z",
  "data": {
    "id": "cko_4kf9v6xp00hzc99rdwr5m97wce",
    "reference": "ORD-202510-0232",
    "payment": {
      "id": "pay_4a4m2pjycdb1jbj68h1rvk9kcz",
      "estimated_update_before": "2025-09-01T22:05:48.479Z"
    }
  }
}

Response

Indicate success, the webhook will not be retried

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.