---
title: "A provider rejects a charge."
method: POST
path: "payment.failed"
tags: ["payment.* events"]
---

# A provider rejects a charge.

`POST payment.failed` (webhook)

### When this fires

A payment provider rejects a charge: invalid card, insufficient funds, gateway risk, expired source. Emitted by Stripe, CeyPay, CoinPayments, Paystack, Razorpay and Skrill. PayPal does not emit `payment.failed`; a failed PayPal charge surfaces only through the subscription-level events.

### Caveats

- The paired subscription event differs by provider: Razorpay emits `subscription.past_due` alongside; CeyPay, CoinPayments and Skrill instead cancel the subscription and emit `subscription.cancelled`; Paystack emits nothing alongside; for Stripe, `subscription.past_due` arrives separately when Stripe next syncs the subscription's status. Do not assume a subscription event accompanies every `payment.failed`.
- A single billing cycle can produce multiple `payment.failed` events as the provider retries.

### Related events

- `payment.succeeded`: alternative outcome.
- `subscription.past_due`: paired subscription event for recurring failures.

## 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.failed', required: The event name, always `payment.failed` 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 id when one was created; `null` for pre-charge rejections.
    - `reason` string, required: Human-readable rejection reason, mostly free text from the provider (Razorpay sends the fixed slug `razorpay_halted`, Stripe falls back to `stripe_invoice_failed`). Not a stable enum: do not branch on its exact value.
    - `amount` string, decimal: **Stripe only.** Attempted amount in major units, as a decimal string. Omitted entirely by the other providers, never sent as `null`.
    - `currency` string: **Stripe only.** Uppercase ISO 4217 code. Omitted entirely by the other providers, never sent as `null`.

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