RefundTriggered

RefundTriggered fires when a completed order is reversed. This covers cancellations, refunds, and order deletions. Extensions typically bind this event to multiple platform hooks to catch all the ways an order can be undone.

The event ID is refund_triggered, and its fully qualified class is Siren\Commerce\Events\RefundTriggered.

What does this event carry?

Like TransactionCompleted, this event carries the Transaction model. The transaction record contains all the context needed to identify the conversions and metrics that need to be reversed.

How does the pipeline react?

Three core listeners react when a refund fires. CancelConversions cancels all conversions tied to the transaction. CancelRefundedTransactions marks the transaction record itself as refunded. SubtractRefundedValueFromMetrics adjusts the incentive and distribution metric totals so that collaborator performance numbers stay accurate.

Together, these listeners ensure that a refund cleanly unwinds the entire chain of records that the original sale created. For a user-level walkthrough of how refunds propagate through the system, see How Refunds Work.

For the full lifecycle of commerce events and how they connect to the rest of the attribution pipeline, see the Commerce Events overview.