---
title: "A payment is initiated, awaiting provider confirmation."
method: POST
path: "payment.pending"
tags: ["payment.* events"]
---

# A payment is initiated, awaiting provider confirmation.

`POST payment.pending` (webhook)

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

## 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` 'payment.pending', required: The event name, always `payment.pending` 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.
    - `provider` string, required: Provider slug.
    - `plan_id` string, uuid, required: Plan being purchased.
    - `subscriber_id` string, uuid, required: Subscriber's project-scoped user id.
    - `session_id` string, nullable: **Stripe only.** Checkout session id; defensively `null` if the created session carried no id. Absent (not `null`) for all other providers.
    - `order_id` string: Paystack, Razorpay, Skrill, CeyPay, CoinPayments. Absent for Stripe.

## 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)