---
title: "A provider confirms a successful charge."
method: POST
path: "payment.succeeded"
tags: ["payment.* events"]
---

# A provider confirms a successful charge.

`POST payment.succeeded` (webhook)

### When this fires

A payment provider confirms a successful charge against a subscriber. Fires for both initial checkouts and recurring renewals.

### Caveats

- For first-time paid checkouts, `subscription.activated` is the matching subscription-level event, not `subscription.created`, which never fires for paid purchases.
- Renewals pair `payment.succeeded` with `subscription.renewed`.
- Card numbers, PAN, and CVV are never included in payloads.

### Related events

- `subscription.activated` (first payment), `subscription.renewed` (renewals): paired subscription events.
- `payment.failed`: alternative outcome.

## 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.succeeded', required: The event name, always `payment.succeeded` 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.
    - `subscription_id` string, uuid, required: Subscription identifier.
    - `plan_id` string, uuid, required: Plan the subscription is on.
    - `subscriber_id` string, uuid, required: Subscriber's project-scoped user id.
    - `provider` string, required: Provider slug.
    - `external_payment_id` string, nullable, required: Provider charge / invoice / transaction id. `null` when the provider's success payload carried none.
    - `amount` string, decimal, required: Charged amount in major units of `currency`, formatted as a string.
    - `currency` string, required: ISO 4217 currency code.
    - `billing_reason` string, required: Always present. Subscriby derives `subscription_create` (first successful payment) or `subscription_cycle` (renewal) from the subscription's payment history; for Stripe, the invoice's own `billing_reason` is passed through when present, so values such as `subscription_update` or `manual` can also appear.

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