• Resolved T4ng

    (@schwipps)


    Hi,

    Since updating to 9.3.0, new orders notes say: “Order status changed from Pending payment to Processing.” But these orders’ status actually remain as “Pending payment”.

    I didn’t have the logs activated until now, so just activated them, thus no idea where this comes from.

    We use this plugin for years, we didn’t change anything to our setup.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    I understand your concern. Currently, the Stripe for WooCommerce payment plugin has the latest version 9.0.0. Can you please clarify exactly which plugin you updated to version 9.3.0?

    Also, could you confirm whether this issue occurs for all pending orders or only for specific ones?

    If the issue happens with all pending orders, could you please create a staging site for testing purposes? On the staging site, deactivate all plugins except WooCommerce and the Stripe payment gateway plugin, and check if the issue persists.

    Additionally, could you share a screenshot of the order notes for the affected orders? This will help us better understand the problem.

    You can use the following tool for screenshot: https://snipboard.io

    Also, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

    • System Status Report?which you can find via WooCommerce > Status > Get system report > Copy for support.
    • Fatal error logs?(if any) under WooCommerce > Status > Logs.

    Once we have more information, we’ll be able to assist you further.

    Thread Starter T4ng

    (@schwipps)

    Hi,

    My bad: we use the 9.0.0 version.

    We don’t get so many orders on this website, but the two that have come in since the Stripe plugin update are the only ones in this situation.

    This website is a bit complex/difficult to duplicate, so I can’t pass it over.

    Howver, I have a true local copy on my computer, with the same exact plugin, configuration, and a today-fresh copy of the database. And I don’t face thds issue here.

    Therefore, I suspect :

    • a temporary issue on Stripe’s side (is this possible – What is triggering the actual status change?)
    • a caching issue
    • a CDN issue (no CDN on the local copy)

    Any thoughts?

    Plugin Support Mahfuzur Rahman(woo-hc)

    (@mahfuzurwp)

    Hi @schwipps,

    Hi,

    Thank you for the details! This issue is likely related to Stripe webhooks or caching:

    1. Check Stripe Webhooks:

    ? Ensure the webhook URL (https://yoursite.com/?wc-api=wc_stripe) is correctly set in your Stripe dashboard.

    ? Check the webhook logs in Stripe (https://dashboard.stripe.com/webhooks) to see if events for these orders were delivered or failed. Re-send any failed events.

    2. Clear Caching:

    ? Clear any site or server-side caching, as it may block webhook communication or prevent status updates from reflecting correctly.

    If the issue persists, please share your System Status Report (WooCommerce > Status > Get system report > Copy for support) and any fatal error logs (WooCommerce > Status > Logs). This will help us investigate further.

    Thread Starter T4ng

    (@schwipps)

    Hi,

    I did it all.

    I checked live webhooks from the Stripe platform. They’re all fine.

    So I move the live website to Stripe test mode, purged caches and placed 2 orders.

    Both moved from “Pending payment” to “Processing” status with no issue.

    So by now, no explanation.

    I guess I have to wait for another real order to get a better idea of what’s going wrong here.

    Thread Starter T4ng

    (@schwipps)

    Mmh, actually, there might be something wrong. from the WooCommerce > Settings > Payement > Stripe > Settings > Account details [live], I get the following message: “Warning: The most recent live webhook, received at 2024-12-29 13:42:26 UTC, could not be processed. Reason: The webhook was not signed with the expected signing secret. (The last live webhook to process successfully was timestamped 2024-12-24 20:44:24 UTC.)?“

    But it doesn’t really make sense since we didn’t touch anything about the Stripe setup for over a month, while we were still able to receive orders with no issue. Until that status issue occured.

    In the meatime, I also found this topic. There actually a couple of these, about the same issue.

    So for now what I did is click dismiss on WooCommece > Settings > Payment > Woopayment ==> click the 3 dots button > Dismiss (although it wasn’t activated).
    This seems to remove the entry from this menu (not the WooPayment main menu entry, but that whole of another story…).

    Let’s see what happens.

    Plugin Support Jonayed (woo-hc)

    (@jonayedhosen)

    Hi @schwipps ,

    Thanks for sharing the detailed breakdown of your findings!

    It seems the payment order status is correctly appearing when you process payments through Test Mode. Based on your description and the thread you shared, the error message you’re encountering is likely due to a recent update. This could point to an issue with the payment gateway or with the server processing the webhook, which might be triggering the errors.

    To address this, I recommend re-authenticating your Stripe account and reconfiguring the webhook by following this guide: Stripe Webhooks Setup and Configuration.

    Once done, try placing a test order in Live Mode to confirm if everything works as expected.

    Let me know how it goes or if you have any other questions!

    Thread Starter T4ng

    (@schwipps)

    Hi,

    I received another order in the meantime, which went fine.

    Today, there’s no webhook error message anymore:

    Still, I reconfigured the webhook.

    It’s still not clear what happened, but I hope this problem is behind me now.

    Plugin Support Mahfuzur Rahman(woo-hc)

    (@mahfuzurwp)

    Hi @schwipps,

    Thank you for the update! I’m glad to hear your recent order went through fine and that the webhook error message is no longer appearing.

    Reconfiguring the webhook was a great step, as it ensures the correct signing secret is in place. The error you mentioned typically occurs if the signing secret used by Stripe doesn’t match the one saved. It’s possible that the issue was resolved when you reconfigured it.

    If the problem arises again or you notice any irregularities, feel free to share additional details, and we’ll gladly assist further.

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.