Closed Bug 719201 Opened 13 years ago Closed 13 years ago

Add currency checking functions and cron job

Categories

(addons.mozilla.org Graveyard :: Developer Pages, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: clouserw, Assigned: andy+bugzilla)

References

Details

The marketplace supports different currencies but paypal's API does not support setting them.  From the spec:

> Finally, because of the nature of our primary/secondary receiver 
> relationship, developer PayPal accounts must be set up to accept
> each currency they wish to support, or the transaction will fail.
> We therefore need to encourage developers to support the currencies 
> they (and we) want, and keep an up-to-date record of those to 
> allow consumers to purchase with. To make things worse, there’s
> no API or redirect process for this currency addition.
 
The final stage of this account linking process will explain how to 
> add currency support, open the correct page in a new tab, and 
> ask the developer to come back when finished. When the developer
> continues our process, we’ll do a test API call for each 
> currency to determine which ones are supported.
 
> There should be a way for the developer to manually trigger this 
> check again later when they add currencies, and we should check 
> monthly to ensure our list is updated. 

This bug is to:
- figure out the backend for storing what currencies each user accepts
- figure out what API the spec is talking about to verify each currency
- implement the methods to run those calls
- create a cron job that will walk through each paypal account and verify the currencies are there.  Log the results.

This bug doesn't include the frontend markup for users to enter their currencies and stuff.  That will be a part of the submission flow and is getting UX'd right now.
Target Milestone: --- → 6.3.9
From my chats to Brandee, just calling the get paykey method with appropriate currency will tell us this information, so that's what I'm doing.
There's a few things going on here, key is that there's a waffle flag, set to off. So that by default it does not actually disable addons, we have to turn that off. All it does is email admins telling them how many failed. I bet that's going to get tedious soon.

https://github.com/mozilla/zamboni/commit/1b00fd
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.