Another Stripe Checkout failure

Hi,

On a website I'm managing, Stripe checkout fails with the message "Please wait while redirecting to Paiement par carte bancaire for processing payment..."
The page is freezed and Stripe page is not opened.
I updated to 4.1.2 version, but the problem was not solved.
Whet can I do?

Thanks!
(Robert for Patrice)

Hello

It is very likely it causes by something on your site. Usually, it causes by :

1. Template has compress Javascript option. It tries to compress javascript. As Stripe uses external JS provided by Stripe, it does not allow loading local js, and it will causes the error. So if your template has that option, try to turn it off, then check it again

2. Or plugin like JCH Optimize or JSpeed. it tries to compress js code, too. If you use these plugins, try to disable it to see if it solves the issue. If Yes, maybe you can find a way to disable these plugins for that page only

If you still cannot figure out, submit a support ticket sending us super admin account of the site and link to the page which I can register for the event. I will check to see what's wrong and get it sorted

Tuan

Thanks Tuan!

The template was using JS minifying. I deactivated it and changed on Litespeed Cache to exclude Events Booking;
Stripe payment works fine now.

Best regards,
Robert

Great. Happy to hear that and thanks for the update, Robert

Tuan

Hi Tuan,

Did I miss an option?
When a Stripe payment is successful, the event registration is not validated and the email for the owner of the site is not sent, Validation must be done manually. Is this normal? I haven't found a setting for this validation.

Thanks,
Robert

Hi Robert

Usually, this happens because Stripe Webhook was not configured properly. So please follow instructions at eventbookingdoc.joomservices.com/basic-s...eckout#configuration , configure webhook properly, then check it again. It should work well

If not, submit support ticket and we will check it further

Regards,

Tuan

Thanks Tuan!

I just checked the Stripe account "www" was missing in the website address.
It seems it works now.

Best regards,
Robert