payment.* events

A provider rejects a charge.

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.
postWebhookpayment.failed

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.failed' required

The event name, always payment.failed 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.