pixelborder

Hi Lorenzo,

Sorry, I wasn’t keeping an eye on this.

I’m not the plugin author so I couldn’t speak with any authority on the events, however I think the main reason it didn’t work for me was because I didn’t include all of those events listed above – I only added a couple.

I don’t know if you can add all events, but I’d say it’s worth a shot. Just don’t miss those ones is what I should have said in hindsight.

Sure, no problem.

There were a couple of different parts to it. I’m not sure how far along you are with it all. But here’s what I did:

WooCommerce > Settings > Payments > Stripe credit cards > API Settings

You’ll be able to hook up your Stripe account. There’s a Webhook url that you’ll need to copy for the next step.

https://yourwebsite.co.uk/wp-json/wc-stripe/v1/webhook

Head over to Stripe, make sure you’re in the right mode for your needs (Live or Test) and go to:

Developers > Webhooks > Add endpoint

Your endpoint URL is that webhook url from above, the one you copied from WoooCommerce.

Select events and add only the following events:

source.chargeable
charge.succeeded
charge.failed
payment_intent.succeeded
charge.refunded

Click add endpoint.

Head back over to WooCommerce:

WooCommerce > Settings > Payments > Stripe credit cards > Local Gateways > Klarna

Make sure it’s enabled.

You should be able to see transactions going through your Stripe account now. You can head back to the webhook to see what events it has tracked.

Let me know if you need any more help

That’s brilliant, thank you very much!

I’ve stripped out the code above from the functions file and altered the offending line in the custom.js file and it works perfectly.

Thank you Marius, I think I follow.

So it’s more likely a result of a plugin or theme having been unprepared for the 4.5 update?

I suspect it has a lot to do with our theme (Divi) needing an update. We’re waiting on authorisation to upgrade it. I’ll remove the above code when the theme is updated and hopefully that will fix the issue properly.

That worked perfectly, thank you!

Do you think this is something that will likely get rectified as WordPress become aware of the issue?