Multiple payment intents on renewal even after payment succeeded

  • Resolved dmcat

    (@dmcat)


    3 months, 4 weeks ago

    Hi there!

    We’re having some trouble with several payments where it appears the Stripe Standard for WooCommerce payments took subscription renewals and while in status “on hold” it kept creating payment intents over and over again for multiple days even after payment was received during the first intent. In Stripe I can see each person was charged a few times each day up until now (as I manually changed the status to complete). This means we’ll have to refund a lot of charges and lose out on a lot of processing fees. This issue only seemed to start in the last few days as we haven’t had an issue like this previously.

    The commonality between all of these is:

    1. They all paid with card via Stripe
    2. They were all paying their 3rd payment in a subscription
    3. They were all renewing around July 25-28

    We are using:

    • WordPress 6.6.1 (just auto-updated several days ago)
    • Woocommerce 9.1.2
    • Yith to manage subscriptions (but processed via Woocommerce for payment)

    Here’s a snip of just one day of order notes of it happening: https://snipboard.io/KGk1OE.jpg

    Grateful for any thoughts or support on this one!

Viewing 16 replies (of 16 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @dmcat

    Thank you for getting back to us with more details. The error logs you’ve shared indeed indicate an issue with the ‘id’ being called incorrectly, which is a result of directly accessing product properties.

    This common issue arises when outdated code or plugins are in use. WooCommerce has deprecated direct access to product properties since version 3.0. Instead, you should use WooCommerce’s inbuilt getter and setter methods.

    In your case, the issue might be coming from the plugin LearnDash or LearnDash WooCOmmerce integration. You need to check if there’s an update available for this plugin. If there isn’t, or updating doesn’t resolve the issue, reach out to the plugin’s developer with the error logs you’ve provided here, as they’ll be better equipped to address compatibility issues with WooCommerce.

    Furthermore, the 4-hour delay you mentioned might be due to the cron job times set by Yith, as you suggested. However, it’s still worth investigating further, as this is not typical for card payments.

    Your decision to test with a small edit in the webhook handler file in the plugin seems like a good approach. The webhook might indeed be the source of the issue, especially if Yith has extended some of the webhook handler functions for subscriptions.

    Please do share the results of your tests when you have them. We’re here to help you troubleshoot further if necessary.

Viewing 16 replies (of 16 total)
  • You must be logged in to reply to this topic.