Stripe causing double payments

#45

So glad that powerful minds are working on this. I’ve just been threatened with legal action by a member who was still being charged when I thought I’d cancelled their trial subscription. It turns out that two subscriptions were made for the same s2_plan_ identification. I’ve calmed the person down, but I’d have been angry too, if I was them and being charged twice!

I hope this will get sorted out super quickly as it’s causing major on-going problems and is losing us reputation and actual money and actual members.

#46

Any updates to this. It would also be good if there was a way to block duplicate payments - e.g. payment for the same amount within XX minutes. That also happens sometimes and since April stripe does not refund the fixed payment fee anymore in Europe just like paypal - so it’s more annoying than before.

#47

I can’t speak for @clavaque but I got caught up with client needs and EOY tax filing. I won’t get a chance to look at this again for 2 weeks.

#48

Undoubtedly related, I’m seeing payments in Stripe which are status “Retrying”, and have tried over multiple days (eg. 24 apr, 27 apr, 2 may) and each time they’re saying “failed” but the person is still an active member on the site.

#49

image
image.png1074×540 31.2 KB

#50

Thanks for the update Tim. All the issues relate to a failed payment attempt. If the user puts in their card info properly and the card is valid then the transactions work fine. If the person puts in their details incorrectly or the card is not valid then we see the problems.

1 Like
Double subscriptions on Stripe
#51

@clavaque Are there any plans to make a new version of stripe-utilities.inc based on onepresstech’s advice, or do you believe that the [200422a-stripe-utilities.inc.zip] file will solve the problem? Thank you for working on this issue!

#52

Would love a status update on this please??

#53

@clavaque appears to have gone into hibernation again. I’ve been flat out with client deliverables and haven’t got back to trying to fix this in the absence of a fix from @clavaque.

I haven’t forgotten this issue though since it is still a problem I need to fix or get fixed for my clients sooner rather than later.

So many things to do in life…so little time.

#54

Anyone have thoughts on how to go about next steps with this? It’s becoming a huge issue.

#55

At the risk of stating the obvious…someone has to take the initiative and test / reproduce / fix the bugs. I’ll get around to it if no one else does but only after I get through my client deliverables. So I’m not going to be able to fix it for 3-4 weeks.

#56

Tim, do you have any insight into the future of s2Member? The lack of a fix on this major issue makes me concerend that this plugin does not have a future.

#57

No idea. Only @clavaque knows.

#58

Frustration… obviously not your fault though onepresstech as I presume you’re just a user of the software like us? As paid-up members we need these major issues which cost us money and reputation fixed quickly. @clavaque needs to get onto this urgently!

#59

@onepresstech, thanks. As said by @madeglobal, this is obviously not frustration towards you. I thought maybe you had a better way to connect with the plugin owners since I have seen you on here a lot.

@onepresstech (or anyone else), have you tested the 200422a-stripe-utilities.inc.zip update enough to confirm with some confidence there are no issues? It seems like this is a decent fix for most of the issues I am having but I am always a little concerend with adding in new code that is not part of a tested update.

@clavaque, can you please update us on this? As well as give us some idea on the future of S2Member? Avoiding a fix to this issue seems to point to no future development and it would just be good to know that.

1 Like
#60

Just to repeat something I mentioned before, double payments are not exclusive to Stripe. I use PayPal with s2Member Pro and I have seen two double payments go through in the past 24 hours.

I’ve been seeing occasional double payments for years, although they are usually months apart. The fact that it has happened twice within the past 24 hours has me a bit concerned.

I find it very frustrating that this plugin, which seems to be the best plugin of its kind, gets such little support. My business relies on this plugin, and yet I always feel like I’m on the Titanic heading for the iceberg. And there never seems to be anyone steering the ship.

1 Like
#61

@coreyalderin - I have not tested the 200422a-stripe-utilities.inc.zip update but @clavaque knows what he is doing so I would trust it. My previous comment is that this patch will reduce some of the occurrences but not all the occurrences and the transactions it fixes is actually as a side-effect. It’s like putting a band-aid on a wound that keeps bleeding. It helps but does not fix the problem.

@madeglobal - Yup…I’m just a user like you and the others :slight_smile:

@Cralamarre - I share your sentiment…which is why I am active on the forum helping and fixing where I can. I have clients that are using this plugin and I have to see it gets fixed or I have to fix it myself. I just don’t have the bandwidth to fix this myself at the moment. The code is actually quite oblique so reverse-engineering it, reproducing the errors, provably fixing the errors and not creating side-effect errors is actually a significant time investment.

#62

I got a response to a private message to @clavaque today. He indicated he has been going through a tough time over the past few months but that things are starting to go back to normal. I would expect you will start to progressively see more of him in the forum but maybe not for another couple of weeks. I don’t know more than that.

#63

I’ve been testing the 200422a-stripe-utilities.inc.zip update. It’s definitely better than before. We are seeing about 1/4 the number of duplicate charges compared to before, but it still happens and is a serious issue.

#64

Good to know. As I said previously:

The fix Cristian provided in the zipfile above adds support for failed message retry protection which alleviates our problem as a benign side-effect but only if the final successful payment occurs within 24 hours of the failed payments. If the failed payment subsequently succeeds more than 48 hours later then the aggregated payment bug will still occur.