ConversionRejected

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. Any obligations associated with the rejected conversion are updated to reflect that they will not be fulfilled. This prevents rejected conversions from appearing in future fulfillment runs and ensures collaborators are not paid for transactions that were reversed or deemed invalid.

The rejection flow is the mirror image of approval. Where ConversionApproved promotes obligations from draft to pending, ConversionRejected ensures those obligations never reach 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.