payment.* events

A payment is initiated, awaiting provider confirmation.

When this fires

A subscriber initiates checkout and is redirected to the provider, but the charge is not yet confirmed (bank transfer, crypto settlement, hosted-checkout sessions).

PayPal carries neither session_id nor order_id: a PayPal payment.pending gives you only provider, plan_id, and subscriber_id, so it cannot be correlated to a specific checkout attempt. Absent keys are omitted entirely rather than sent as null; the one exception is Stripe's session_id, which is always present on the Stripe path but may be null.

Caveats

  • A pending payment is not yet a subscription. subscription_id is intentionally absent.
  • The same checkout may emit one payment.pending followed by either payment.succeeded or payment.failed. Correlate on session_id or order_id where the provider supplies one; for PayPal, fall back to subscriber_id plus plan_id.
  • Subscribers who close the provider page without completing will not produce a final outcome event; pending sessions can hang indefinitely.

Related events

  • payment.succeeded, payment.failed: terminal outcomes.
  • subscription.activated: fires alongside the payment.succeeded that completes a first checkout.
postWebhookpayment.pending

Headers

SB-Signaturestring required

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=.

SB-Event-Idstring required

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.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring required

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type'payment.pending' required

The event name, always payment.pending here.

created_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

Response

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

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.