Closed Bug 746689 Opened 10 years ago Closed 10 years ago
When an instant refund goes wrong
We should tell the developer why the refund failed. For example when Krupa and I tested it was due to currencies, in this case the developer needed to add a bit of money. We should also give the user a bit more feedback.
Most of the time when a refund goes wrong, it will be an instant refund and due to currency balance. This is an issue because there's much the end user can go do, it's up to the developer to fix this. At the moment the buyer can't do much about it. We've got a model (Refund) that lists all the refunds pending. What I'd like to do is: - add a new status to the model, refund-failed. - when a refund fails add this to that model - mail the developer telling them a refund failed and if its a currency issue the problem that occurred, see bug 747057 - make a new tab in the refund page for failed refunds - allow the developer to (once they've corrected the paypal issue) come and click that failed refund and allow it to go through - alter the failed message to say something geninue like "we've told the developer and they'll go sort it out, honest guv" * * real text may vary.
Summary: When a refund goes wrong → When an instant refund goes wrong
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
This was done for AMO but it hasn't been updated on Marketplace, so we should do that: https://github.com/mozilla/zamboni/commit/0f07bc9f#commitcomment-1357317
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Putting in next week's milestone since we already have a patch.
Target Milestone: 2012-05-17 → 2012-07-05
This code was, in fact, updated in Marketplace: see mkt/developers/views.py in the referenced commit.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → INVALID
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.