Hot Fix: Resolved issue with some Stripe gateways not recording incoming recurring donation renewals.

[glaubersilva]

Resolves #7076

Description

The webhook events used by the Stripe Element were using the exit in the wrong place and it was preventing the events from the legacy codebase from running.

This PR fixes this problem.

Affects

Stripe renewals in donations/subscriptions created with v2 forms.

Testing Instructions

1. Using the latest version of GiveWP and the Recurring Donations add-on, make a recurring donation on a V2 form
2. Spoof a renewal in Stripe by resetting the billing cycle: https://somup.com/c06tcOBP02
3. The renewals should be recorded on the Give side.

Pre-review Checklist

• Acceptance criteria satisfied and marked in related issue
• Relevant @unreleased tags included in DocBlocks
• Includes unit tests
• Reviewed by the designer (if follows a design)
• Self Review of code and UX completed

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1205823108730572

[jonwaldstein]

@glaubersilva looks great thanks!

[JasonTheAdams]

@glaubersilva @jonwaldstein Am I following the logic here that basically we're no longer exiting if the v3 form system did not process the event, which gives the v2 system the opportunity to process it?

[jonwaldstein]

@glaubersilva @jonwaldstein Am I following the logic here that basically we're no longer exiting if the v3 form system did not process the event, which gives the v2 system the opportunity to process it?

Correct, we found the exit statement needed to be called conditionally - only if Stripe Payment Element processed the event. The original purpose of the action was for Stripe Payment Element to take over the request when need be (because it lived in the seperate next gen repo). In this scenario we don't want both webhook logics to run - it should be either the legacy Stripe webhook or new one.

We weighed many different options together and this was the simplest way to resolve the current issue at this time. When we have a little more time to dedicate to this, we would like to explore creating some kind of proper proxy up the chain and/or merging the logics so they can truly be handled separately to avoid conflict and confusion.

[rickalday]

Passed manual QA tests.