Error while attempting refunds via order via stripe

Hi there!

I understand that you are facing an issue while processing the refund.

As a first step, can you check on the status of your webhook in Stripe. Head to WooCommerce → Settings → Payments → Stripe and then select the Settings.

There in the Account details do you see that your webhook is enabled and that the most recent webhook was successful? The info here may help confirm that your webhook is working as needed. Any errors with the webhook will display similar to the screenshot below:

If webhook is enabled, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:
System Status Report?which you can find via WooCommerce > Status

Also, please enable the Stripe error log by going to WooCommerce > Payments > Stripe > Settings, scroll down to the Advanced tab, and check the Error Log option. Then, go to WooCommerce > Status > Logs, open the log file related to Stripe payments, copy the error log.

Please use?https://pastebin.com/?or?https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further ?????????????????????????????????????????????????????????????

https://pastebin.com/8KbYGSpT

strange i tried a dollar refund and now it worked i guess if i have the issue again ill let you know
last time there was nothing in any of the logs that i looked at that gave me any clue
the webhooks weren’t setup but I fixed that and it didn’t help (at least not immediately)

Thanks for the update! I’m glad to hear the refund worked this time. If the issue happens again, feel free to reach out, and we’ll be happy to take another look.

Since there were no clues in the logs and fixing the webhooks didn’t help immediately, it’s possible that there was a delay in processing or a temporary issue with communication between your site and the payment gateway. If the issue happens again, I’d also recommend clearing your site and browser cache to rule out any caching-related conflicts.

Since the issue seems resolved for the moment, I’ll go ahead and mark this ticket as solved.

If you run into the issue again or need any further assistance, feel free to reach out, we’re happy to help!