Legacy webhook events reference

Transaction Created

Any transaction for the store — a new transaction, a subscription renewal, a customer info update, or a customer-initiated subscription cancel (which sets a future subscription end date). All of these generate a transaction, so all are sent to the endpoint

Transaction Captured / Refunded / Voided

Relies on beta transaction editing functionality, enabled per store. Fires when an existing transaction is manually captured, refunded, or voided — through the transaction report section of the administration, or through the API. The Captured event here applies to a previously uncaptured transaction (verified or authorized) that is then manually captured. The original transaction would already have triggered Transaction Created; this event reflects the change in payment status

Subscription Cancelled

Fires when a subscription actually ends, on its end date. Subscriptions made inactive directly via the administration or API do not trigger this event. Customers completing a sub_cancel checkout also don’t trigger it — that sets the subscription’s end date to tomorrow or the next transaction date (depending on store settings) and instead triggers a Transaction Created event, with a transaction_type of subscription_cancellation and the new subscription_end_date set on the subscription product

</parameter>