Bind the change to a verifiable boundary
Record the revision, repository, endpoint path, event type, event identity, payment-object identity, expected booking effect, duplicate-event result, reviewer, rollback owner, and post-rollback check. The receipt must separately name unmodified raw-body preservation, signature-header verification, the endpoint signing key or verification method, and the no-booking result of a failed verification; “webhook secured” is not a testable claim.
Stripe's webhook documentation describes its signature verification inputs and retry behavior; its payment-event example shows a provider-specific local test path. Neither source proves a repository has an intact route, correct secret, idempotent behavior, or booking policy.
Exercise the declared event
Use an approved non-production fixture. A maintainer should be able to identify what delivery is expected, whether its verification condition is met, what appointment effect is allowed, and what a repeat delivery must not change. For the duplicate check, preserve both the delivery's event ID and the event type plus underlying payment-object ID: a provider can deliver the same business event in distinct event envelopes.
node --test sites/odexing.com/evidence/P142/payment-webhook-change-receipt.test.mjs
This checker does not receive a network request, validate a live secret, deduplicate a real delivery, or authorize a merge.
Keep reversal human-owned
Stop if the source event, raw-body preservation, signature-header/key verification, failed-verification result, event or object identity, expected booking effect, duplicate-event result, reviewer, rollback procedure, or post-rollback check is unknown. Do not merge an agent's proposal because it resembles a familiar webhook pattern.
For authorization changes, see Gate an Agent-Generated Authorization Change Before Merge. For a pipeline boundary, see Gate an Agent-Generated CI Workflow Change Before Merge.
Does a receipt make a payment handler safe?
No. It makes one review boundary inspectable. Payment security, secrets, event ordering, provider delivery behavior, customer communication, and production monitoring require separate environment-specific evidence.