-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refine failed refund notes #601
Comments
Please check if this can happen on Square, PayPal Checkout, Amazon and let's come up with a common, consistent strategy (and Stripe extension too) since merchants tend to install more than one payment gateway (hopefully ours) fyi @bmccotter @LCmry |
There are many questions on this issues we'd need to resolve first before proceed with implementation. AFAIR it's tricky one due to the async nature of refund failures and unreliable delivery of forwarded hooks, or in the case of successful refund there won't be any following hooks at all. Anyway, more in-depth exploration is necessary here. |
I believe that this issue has enough context, and it can be moved from the Engineering review queue to the Ready of prioritization. If additional feedback or research is needed, the dedicated person can be assigned to this issue to perform additional research or reach out to the people who will have more context. This is the part of the Gamma backlog porter duty to reduce the number of the issues in the Engineering review column. |
@htdat can you please check it and see if it is still relevant, then we can loop in product and design for the next steps. |
I could have been fixed by #3965 |
I tested with the latest version 6.2.2 - screenshot, and notes are still the same as what James mentioned above. Moving this issue to "Product review" queue.
PR #3965 is to remove |
We have some basic handling of failed refunds added in #411.
After issuing a refund, the refund can fail at a later date. For example, the card used for the purchase could have expired. To handle this we send a refund failed webhook which adds a note to the order:
@RadoslavGeorgiev and @vbelolapotkov rightly pointed out that the notes don't make complete sense after a failure has occurred. We tell the merchant that the refund was successful, and then the next note says it wasn't.
There are also some questions about how we want to handle this more generally:
The text was updated successfully, but these errors were encountered: