payment.pending
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_idis intentionally absent. - The same checkout may emit one
payment.pendingfollowed by eitherpayment.succeededorpayment.failed. Correlate onsession_idororder_idwhere the provider supplies one; for PayPal, fall back tosubscriber_idplusplan_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 thepayment.succeededthat completes a first checkout.
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.
Request Body
application/json
The signed JSON envelope posted to your endpoint.
TypeScript Definitions
Use the request body type in TypeScript.
The envelope every event is delivered in.
Response Body
Example Requests
/payment.pendingHow is this guide?