benecaster_donation_webhook_rejected

Fires inside POST /benecaster/v1/listener-support/donations when webhook signature verification fails — after the 403 signature_invalid response is prepared but before it is sent. The donation row is NOT written. A single debug log line is also written: [benecaster] webhook verification failed for platform=<canonical> from IP=<hash> (the IP address is hashed — raw addresses are never logged).

Use this action to route rejection alerts to Slack, log to an external security service, or trigger rate-limiting or blocklist logic.

This action only fires when a secret was configured for the platform and that secret check failed. Requests from platforms without a configured secret are accepted silently — they do not fire this action and do not fire _verified.

The rejection action deliberately omits the failure reason. The debug log line records that verification failed, but neither this action nor its parameters reveal which part of the signature check failed. Consumers that need to bucket failures by cause should parse the [benecaster] webhook verification failed … line from debug.log instead — exposing failure details through a PHP action would make it easier for an attacker iterating against the endpoint to learn what they got wrong.