Hello @walzim
thank you for reaching out to us, we are here to help.
We are about to release our next version (1.6.2) next week and this could have a solution included for this issue you are seeing. It includes fixes on webhooks that can fix refund issues, also checkout logic that can prevent some duplicated issues. I think it would be best to test this first and if the issue is not resolved we should take a closer look at your setup and logs. Please make sure you activate logging in the plugin settings, so we will have examples available when we need them.
Kind regards,
Joost
I just wanted to add that I also saw this problem on a client’s website yesterday, 11/22 on version 1.6.1. A shop manager initiated the $195 refund via the WooCommerce order and we see two refund numbers in that order screen:
-Refund #7783 – November 22, 2021, 12:51 pm by “my admin username” for -$195.00
-Refund #7782 – November 22, 2021, 12:49 pm by “shop manager username” for -$195.00
And the amount refunded is listed as $390 in WooCommerce. But then in PayPal, the refund is correctly only -$195.00.
Hopefully version 1.6.2 fixes this.
thank you @6288media
please let us know if this issue still persists, so we can create a new bug for our developers to take a closer look.
Kind regards,
Joost
Thread Starter
walzim
(@walzim)
@joostvandevijver
Just wanted to say that so far the error does not occur again. But already before the update to 1.6.2. Strange
Hello @walzim
thank you for the update, please let us know if this issue occurs again, so we can update our bug (for my internal reference: PCP-440). For now, I have not been able to replicate this behaviour/issue, so I am still hoping the issue was fixed with the release of 1.6.2
Kind regards,
Joost
I’m still seeing this issue and using 1.6.4.
Issue is the same as reported by @6288media
Hello @commuter and @6288media
I checked our backlog and indeed see the bug still open, so it is correct that this issue was not resolved with the 1.6.2 release. I talked with the team and they informed me that this bug did unfortunately not get included in the previous releases, but it is still on our list with the highest priority.
I know this might look strange, but we have a list of critical items and pick them up by the number of reports we get on them. We are confident we will get to this one soon as well.
We are sorry that this took longer than we expected initially, but can assure you this has not been lost or forgotten about!
Kind regards,
Joost
As of today 1.8.0 test 1 version the issue is still on going.
I don’t get that you are resolving other small issues that should have very low priority.
You are not prioritizing the issues as you should.
Hello @thibotus01
We see that you are following the GitHub thread that is handling this case, so you should be aware that we currently believe this is not caused by our plugin but is most likely an issue in WooCommerce. We believe this because the exact same issue sometimes occurs with other payment plugins.
If the issue is caused by our plugin, the solution would be to resubscribe to the webhooks. If this does not resolve the issue, it is most likely caused by WooCommerce.
We will look into this further soon, but for now, we advise avoiding the issue by performing refunds from the PayPal interface if resubscribing the webhooks does not help.
Kind regards,
Joost
Hello,
this issue should be resolved with version 1.8.1 which was released yesterday. Please update the plugin and see if it resolved the issue for you. We will mark this thread as resolved. Please open a new thread if you need additional support or have any other questions.
Kind regards,
Joost
