breeze Posted February 5, 2021 Report Posted February 5, 2021 After upgrading blesta to 5.0.2, the 'Stripe Payments' plugin has stopped working. There's always the same error after clicking pay: However, blesta actually thinks the payment is processed successfully, and customers even get their e-mail: But if we check the gateway logs, in one of the stripe requests we get this: Another customer is having the exact same issue, which the admins haven't responded with a solution yet. Help is much appreciated, Thank you. Quote
1 Paul Posted February 12, 2021 Report Posted February 12, 2021 Please note, there is a fix for 5.0.3 which should be out soon (hopefully next week). However, if you like you can manually patch your installation. See the details in the task at https://dev.blesta.com/browse/CORE-4165 to do so. Quote
0 Haris Posted February 5, 2021 Report Posted February 5, 2021 I don't think its related to version 502. tested it on 4.12 giving same result. or is it working for you before upgrades? Quote
0 Paul Posted February 5, 2021 Report Posted February 5, 2021 Is this only an issue during checkout on the order form, or does this also happen when a client makes a payment from the client area? Interestingly, some report no issues. We're investigating. Quote
0 Haris Posted February 6, 2021 Report Posted February 6, 2021 5 hours ago, Paul said: Is this only an issue during checkout on the order form, or does this also happen when a client makes a payment from the client area? Interestingly, some report no issues. We're investigating. Hi Paul, for me it only happens during checkout on from order form (all order form types). The invoice was generated but payment not captured. So the client needs to go to client area and pay the pending invoice. Card payment from the client area works fine even with stripe sandbox. I'm going to check the order form checkout using live mode if the same issue persists. Quote
0 breeze Posted February 8, 2021 Author Report Posted February 8, 2021 On 2/6/2021 at 12:30 AM, Paul said: Is this only an issue during checkout on the order form, or does this also happen when a client makes a payment from the client area? Interestingly, some report no issues. We're investigating. Hi, thanks for the reply. As the user above me commented, this only happens during the checkout in the order form. I think there is a compatibility issue with the plugin and stripe api responses. I tried to do something about it with no luck. Looking forward to an update. Quote
0 Michael Posted February 8, 2021 Report Posted February 8, 2021 Yeah as far as I'm aware it's just checkout I had this issue with a client of mine, adding a payment account meant that I could pay an invoice. Quote
0 Paul Posted February 12, 2021 Report Posted February 12, 2021 Just an FYI, we have created CORE-4165 and are working on this for a 5.0.3 patch release. Quote
0 kala Posted February 17, 2021 Report Posted February 17, 2021 Anyone else is facing the issue when trying to add a payment account? We have clients complaining about this when they try to add a payment account and there is no log I could find at Strip about this. We have Version 4.12.3 Quote
0 Paul Posted February 17, 2021 Report Posted February 17, 2021 12 hours ago, kala said: Anyone else is facing the issue when trying to add a payment account? We have clients complaining about this when they try to add a payment account and there is no log I could find at Strip about this. We have Version 4.12.3 That sounds like a completely separate issue from the one in this thread, should work fine on 4.12.3. Make sure you are forcing HTTPS, if your clients are connecting over http it will not work. Also, both your server and the client must support TLS 1.2+, so clients on old browsers and an old OS/Server will not work. Quote
Question
breeze
After upgrading blesta to 5.0.2, the 'Stripe Payments' plugin has stopped working.
There's always the same error after clicking pay:
However, blesta actually thinks the payment is processed successfully, and customers even get their e-mail:
But if we check the gateway logs, in one of the stripe requests we get this:
Another customer is having the exact same issue, which the admins haven't responded with a solution yet.
Help is much appreciated, Thank you.
9 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.