694685 - What do we do when refund token gets corrupt/invalid/lost?

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Public Pages, defect, P4)

Description

[krupa raj[:krupa]]

Attachment: screenshot

steps to reproduce:
1. Enroll an add-on into Marketplace after setting up third-party token.
2. Disable the third-party token associated with that account (from PayPal)
3. Load https://addons-dev.allizom.org/en-US/developers/addon/esperance-1/payments

What is the expected behavior then? Should we temporarily disable purchase of those add-ons till the developer enables it again?

Currently, Marketplace remains enabled and we don't show any warnings or error messages to the developer to enable it. See screenshot.

Comment 1

[Andy McKay]

The token isn't required for payments and its not actually required for refunds.

I think a cron that runs nightly and emails developers if their tokens are failing would be sufficient.

Comment 2

[Wil Clouser [:clouserw]]

Can you explain "not actually required"?

Frank Lee is a new UX guy that just started who can help us with questions like this if we can give him some context.  Ragavan: can you put this on your list?

Comment 3

[Andy McKay]

According to an email on the 15th August between fligtar and Paypal: "From what I remember of the call, if it's revoked, the refund would come entirely out of the developer's account, so it's definitely in their interest to keep the permissions or they'll be losing money."

Comment 4

[Wil Clouser [:clouserw]]

Thanks for filing this.  Due to resource constraints we are closing bugs which we won't realistically be able to fix.  If you have a patch that applies to this bug please reopen.

For more info see http://micropipes.com/blog/2014/09/24/the-great-add-on-bug-triage/