can you explain the new update for: 4.2.2

I second this!

And a 3rd! Nothing in the change log?

This version is not working!
I was forced to disable payments through this plugin!

Hi there,

Thanks for reaching out!

> Would be nice to be able to execute refunds in the dashboard vs going to stripe.com, is there a reason this feature was removed?

You can read more about the general logic behind this decision in the following threads from our public repo:

https://github.com/woocommerce/woocommerce-gateway-stripe/pull/901
https://github.com/woocommerce/woocommerce-gateway-stripe/issues/900

In summary, it has to do with preventing shop owners from accidentally cancelling orders, generating a refund, and having to go back to the customer and have them re-purchase the item(s). Additionally, if a customer has a subscription product, for example, and decides to cancel their subscription, they shouldn’t be generated a refund for the most recently paid / cancelled order. This should only cancel the subscription in the future and not generate a refund from their previous payment.

Hope this makes sense!

Thank you for clarifying, that does shed some light.

Do you happen to have stats on how many stores use subscription models vs standalone purchases? I imagine there’s a good portion of stores that don’t use subscriptions so refunding prior payments is not a factor. It would be nice if this were an optional setting instead; “Allow refunds triggered directly from the admin” y/n, because then it covers both preferences.

Per the second link, adding a confirmation button when choosing “refunded” is a good solution to avoid the accidental clicks, while retaining the functionality.

Between those two things, it seems like everybody would be happy. But maybe that adds an unreasonable complexity to the code base?