Hello @wosiwosiuk
We’ve seen a few similar cases recently, and so far nothing suggests the PayPal Payments plugin is at fault. However, we are investigating this issue and comparing reports from affected users to help identify the root cause. The logs and update timeline don’t indicate a plugin issue.
In some logs we noticed that the order is first created and then patched with
"custom_id": "76279",
"invoice_id": "paypal-76279"
Then it is captured. After that, another patch happens with:
"custom_id": "76280",
"invoice_id": "paypal-76280"
Most likely this is because, for some reason, another WooCommerce order was created. The PayPal plugin doesn’t control order creation — it only processes payment after WooCommerce generates the order. Since this also happens with other gateways, it’s unlikely something we can patch on our end.
Kind Regards,
Krystian
Hello @wosiwosiuk
WooCommerce reached out to us today, pointing toward the Sucuri plugin as a likely factor. I would recommend to disable it temporary.
Kind regards,
Krystian
@inpsydekrystian Thank you, will try that and give a feedback
Hello @wosiwosiuk
I just went through a few more system reports from affected users, and while around 90% of them do have the Sucuri plugin installed, your setup doesn’t. That’s why the earlier comparison didn’t point directly to the plugin itself. Some users now suspect it might be related to Sucuri’s DNS-level firewall rather than the WordPress plugin specifically.
If you confirm any connection with Sucuri on your end, feel free to share that info as well. If not, then temporary disable some of firewall related plugins.
Kind Regards,
Krystian
We also use sucuri firewall on our end.
would it be advisable to disable firewall ?
Hello @wosiwosiuk
I wouldn’t recommend disabling it completely. Did you contact Sucuri already or have any further answers or resolutions on this issue?
Thanks for your input.
Kind Regards,
Krystian
Yes, the issue persists even after disabling the firewall.
Same issue, our customer was charged 4 times. We do not use Sucuri.
So far, we have been able to manage this issue and no duplicate since we rolled back elementor to 3.26.4. I’m not sure if everyone facing this issue also use elementor, but it’s obviously not from Sucuri.
@inpsydekrystian – We’ve also been having this issue for several weeks now, but with a site that’s on WP Engine (which uses Cloudflare) and doesn’t have any Sucuri or Elementor plugins installed.
I see that your plugin released two new major updates in the last few weeks, which makes the timing seem related. Are you sure there’s nothing new that might be causing this?
We’re going to roll back this plugin to 2.9.6 for now and disable the PayPal button on all pages except the checkout page to see if it helps.
-
This reply was modified 1 year, 1 month ago by
SiteBolts.
Hello @sitebolts
Just a quick note — please consider creating your own topic for this, as forum rules don’t allow for thread hijacking, and moderators might remove your message. Having a dedicated topic also helps us track and troubleshoot your case more effectively.
Now, regarding the issue itself — based on what we currently know, there are no confirmed signs that the recent updates to the PayPal Payments plugin are causing this problem. If the issue started after March 16th, it is most likely not related to our plugin.
However, if it began earlier than that, please do let us know the exact timing. In that case, we can check if there was anything introduced on our side that could have caused it.
Kind Regards,
Krystian
