Forum Replies Created

Viewing 1 replies (of 1 total)
  • Thread Starter salhidjemael

    (@salhidjemael)

    Hi Ginger,

    Thank you very much for your reply and for taking the time to test this.

    I have attached the requested webhook activity screenshot and I will also include the full System Report below.

    Regarding my previous message about the signing secret, I apologize for the confusion. I manually created a new webhook in Stripe while troubleshooting because I thought the original webhook might have been corrupted. I now understand that GiveWP manages the webhook signing secret automatically and that there is no manual setting for it inside GiveWP.

    Unfortunately, the issue is still present, even after updating to GiveWP 4.16.1.

    Here is everything I have tested so far:

    • Updated to GiveWP 4.16.1.
    • Reconnected Stripe.
    • Deleted and recreated the webhook.
    • Tested both old and newly created webhook endpoints.
    • Cleared all WordPress, LiteSpeed and Hostinger caches.
    • Verified the server time (correct).
    • SSL Labs gives the server an A rating.
    • WordPress and PHP are fully updated (PHP 8.2).
    • Stripe payments are always successful.
    • PaymentIntent objects are created correctly and include GiveWP metadata such as Donation Post ID, Sequential ID and Email.

    However, the donations are never completed inside GiveWP.

    The GiveWP logs consistently show the following error:

    Invalid Secure RouteRoute:Give\DonationForms\Routes\DonateRouteSignatureSignature:givewp-donate|1782767155

    At the same time, Stripe keeps retrying the webhook delivery and reports TLS delivery failures because the endpoint never returns a successful 2xx response.

    I also noticed that GiveWP shows the last successfully received Stripe webhook on June 23, even though Stripe has continued sending webhook events successfully since then.

    Based on everything I’ve tested, it looks like the webhook reaches WordPress, but GiveWP rejects the request before completing the donation because of the Invalid Secure Route validation.

    Do you think this could be related to the secure route signature validation rather than the webhook itself?

    If there are any additional debug logs or temporary patches I can apply, I’d be happy to test them.

    Thank you again for your help.

Viewing 1 replies (of 1 total)