Multiple payments for same order
-
URGENT
Plugin has created 30+ payment charges for the same renewal on multiple orders.
This is a massive issue as we have to refund over £1300 pounds in the last 24 hours.
Its with YITH subscriptions, they say its your plugin thats the issue
-
I am also having this issue using Woocommerce Stripe Payment Gateway with YITH Subscriptions Premium
Latest versions of WP, WooCommerce, Stripe Gateway and YITH
Orders show the payment intent being created but the charge is not saved to the order despite being successful on Stripe. YITH then retires 10 minutes later and takes payment again (and again and again) until the order is manually updated to ‘Completed’
Yes, this is totally unacceptable and unbelievable at the same time.
We only caught this after the weekend, we have now had to refund £1000’s of pounds to people, we dont know if this has now made people overdrawn so we are now liable to posiible prosecution and legal action because of STRIPE woocommerce developers.
We are now looking at our legal obligations and standing to responsibility over the charges and any customers financial compensation.I’ve had great convo with YITH, they lay the fault with STRIPE for Woocommerce. Roll back to 8.4 and YITH do currently have a fix in the next version of their plugin to address the issue
Hello Christopher Sheppard, AlastairM
Thank you for contacting Woo support.
Could you share the exact message from YITH that explains how this is a fault with the WooCommerce Stripe Payment Gateway?
This information will help me understand the conflict between two plugins.
It will also help me create a report if there is a problem with the WooCommerce Stripe Payment Gateway plugin.Lastly, you mentioned:
Roll back to 8.4 and YITH do currently have a fix in the next version of their plugin to address the issue.Do you mean YITH is providing a fix for this or is it still something that needs to be fixed at the WooCommerce Stripe Payment Gateway side?
Looking forward to your response. ??
Best regards.
Hi @doublezed2
This is the response from YITH:
Hello there,
it seems there’s an issue with the?8.5.x?version of?WooCommerce Stripe Gateway.
We are already working on this issue but, in the meantime, we suggest to downgrade ti to version 8.4.x until the issue is solved.
Unfortunately, this is something we have no control over since, especially in the last period, they are making several changes to the plugin code without giving reasonable notice.
?
I’ll keep you updated when the issue is solved and you can upgrade back the plugin.I have asked for a full report from YITH and likewise I require a full report from you so we can understand how the plugin was able to generate 100’s of duplicate payments from our customers.
Our legal team need to understand how and why this happened, we are already being questioned about these payments from some customers as you would expect, and at the current time we cannot give them a plauseable explanation as we dont know why this happened.
Looking forward to your detailed response, please PM me the report.
Thanks
Christopher
I can confirm that rolling back to version 8.4 has resolved the issue for me.
My response from YITH implied the fault was in the Stripe for Woocommerce plugin but made no mention of YITH preparing a fix
Hi @cjsheps
For context, WooCommerce Stripe Payment Gateway version 8.5.0 brought a number of changes, some of them related with subscriptions.
I’ll keep you updated when the issue is solved and you can upgrade back the plugin.
It’s great to hear the team at YITH is already working on continuing compatibility. Feel free to update this thread when the update is available.
I have asked for a full report from YITH and likewise I require a full report from you so we can understand how the plugin was able to generate 100’s of duplicate payments from our customers.
Just to clarify, a payment plugin, like WooCommerce Stripe Payment Gateway, acts on signals/requests made by other e-commerce functionality, for example subscription products/services created with the YITH plugin.
Moreover, the WooCommerce Stripe Payment Gateway plugin is developed publicly on GitHub.
Further resources that might be useful: https://woocommerce.com/support-policy/
a plauseable explanation as we dont know why this happened.
Thank you for bringing this to our attention. Software, like in everything in life, evolves. The more “moving parts” in an e-commerce installation, the more delicate the upgrade process to each new version.
Therefore, it is recommended to test with a staging site, after making sure a recent backup is available.
Ultimately, the control, and responsibility, falls on the hands of the person/team that manages a site, though, as all functionality is chosen and implemented by them.
The issue appears to have happened because plugin updates were pushed to the live site, prior to making sure no functionality conflicts might arise.
I hope this is helpful! Please let us know if you have any further questions or concerns.
We will be happy to help you further.- This reply was modified 4 months, 1 week ago by anastas10s. Reason: added clarification
We have the same problem, just replying to follow this thread
Hey, everyone!
Please note that our dev team is already aware of a similar report here:
- https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2331
- https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2463
And a fix already proposed and waiting for review here:
- https://github.com/woocommerce/woocommerce-gateway-stripe/pull/2354
- https://github.com/woocommerce/woocommerce-gateway-stripe/pull/3300
If you need further help, and you are not the thread starter, as per forum guidelines, please open a new thread so we can assist you ??
Have a wonderful day!
- You must be logged in to reply to this topic.