I have the same issue. I get the following response from the logs (while the country is in place):
2022-05-05T05:24:48+00:00 DEBUG https://api.paypal.com/v2/checkout/orders/XXXXXXXXXXXXX
Response Debug ID: XXXXXXXXXXXX
Response: Array
(
[code] => 200
[message] => OK
)
2022-05-05T05:24:48+00:00 ERROR Refund failed: No country given for address.
Hi @tonyrwest,
Could you please enable Logging in the plugin settings and then try again to perform a refund?
If the same error @christopherplus mentioned is logged under WooCommerce > Status > Logs, then this may have been introduced in a recent update, so it would be worth giving it a try with the previous version 1.7.1 or 1.7.0. But we are not aware of how this error could be reliably reproduced.
For now, the log entry would be the most interesting thing to learn more about the cause of the error.
Thanks!
Kind regards,
Niklas
I also have this issue exactly
Who can I talk to? I don’t want to paste the log data here
Same issue with 1.7.0 (Log= “No country given for address” but it is)
If anybody wants to share their log files in a private message, you can reach us from here: https://paypal.inpsyde.com/docs/request-support/
Please include a copy of the WooCommerce system report and a link to this thread.
Here on the forums, instead of responding to this thread, we’d appreciate it if everyone could create their own threads so we can better keep track of your individual requests.
Thanks!
Kind regards,
Niklas
I’m still getting this error. Any update on this?
Hello all,
our developers further investigated the issue and created a fix for this issue. Please download and install this package and let us know if this resolves the issue.
We will include this most likely in our next release, but we still need to verify that this is a good fix, so we would appreciate your feedback on it.
Kind regards,
Joost
Thread Starter
trwst
(@tonyrwest)
The update seems to have worked for us.
Thank you for confirming this. We had 2 other cases also confirmed to be resolved when using this package, so we can assume this issue is resolved with this fix and will be added it to our next release.
I will mark this thread as resolved. Please open a new thread if you are still encountering this issue when you are using the package provided in my previous comment.
Kind regards,
Joost
