project.* events

A payment gateway is removed from a project.

When this fires

A creator removes a payment method from the project:

  • Dashboard: the remove action on the project's Payment Methods page.
  • Bot: the main bot's payment-method menu, "disconnect" on a connected gateway.
  • REST: DELETE /v1/projects/{project}/payment-methods/{method}.
  • MCP: the delete_payment_method tool.

It does not fire when:

  • A gateway is switched off. That is project.payment_method.updated with changes.active, and the row stays.
  • A Stripe method is disconnected from its Connect account. The row is kept (unlinked and inactive) and that flow raises no event at all.
  • The row was already gone. Deleting twice writes nothing the second time and emits nothing.

The row is soft-deleted, not destroyed. Subscriptions sold through the gateway keep pointing at it for refunds and history, and if the creator sets the same gateway up again in the same mode, the same row is revived. Expect this id to come back to life, and remember there is no project.payment_method.created event to tell you when it does.

Caveats

  • active: true here means the creator removed a gateway that was live for new purchases. If you mirror the project's checkout options anywhere, this is the event to react to; a deactivation would have arrived as updated first.
  • Existing subscriptions are untouched. Their renewals, refunds and history keep referencing this gateway even though the row no longer appears in the project's payment methods list.
  • linked is not in the snapshot, and nothing about the gateway's credentials or connected account is ever sent.

Related events

  • project.payment_method.updated: every change to the gateway before this one, including switching it off.
  • project.deleted: a project going away takes its gateways with it without a per-gateway event.
postWebhookproject.payment_method.deleted

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'project.payment_method.deleted' required

The event name, always project.payment_method.deleted 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.