Siren

ConversionRejected

Fires when a conversion is denied due to refund or manual rejection.

WordPress plugin

Last updated: October 26, 2026

Not every conversion survives review. When a customer requests a refund or an admin manually rejects a conversion, the system fires ConversionRejected. This event triggers the cleanup of any obligations that were created during the conversion flow.

The event is identified as conversion_rejected and lives in the Siren\Conversions\Core\Events namespace.

What does this event carry?

The event carries a single Conversion model representing the conversion that was rejected.

use Siren\Conversions\Core\Events\ConversionRejected;

public function handle(Event $event): void
{
    $conversion = $event->getConversion();
}

What happens when it fires?

The RejectObligations listener handles the obligation cleanup. A draft or approved obligation for the rejected conversion becomes rejected. If the obligation is already in a payout that hasn’t been sent (unpaid or failed), the listener also takes it out of that payout. An obligation in a payout that is processing or paid is left as it is, because that money has already gone. This keeps rejected conversions out of future fulfillment runs.

The rejection flow is the mirror image of approval. Where ConversionApproved promotes obligations from draft to approved, ConversionRejected keeps them out of the fulfillment pipeline. See How Refunds Work for the full chain from refund through conversion rejection to obligation cleanup.

See the Conversion Events overview for how this event fits into the full conversion pipeline.

Your privacy choices

Account, checkout and chat you request work without optional tracking. Choose whether to allow these other uses on this website.

You can change or withdraw your choices at any time using “Privacy choices.” We remember your choice for 180 days. Read our privacy policy.