project.payment_method.deleted

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.

Header Parameters

The signed JSON envelope posted to your endpoint.

Response Body