Marketplace/BokuPayments: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Boku: http://boku.com/ == UX == == Bugs == * Put [boku] in whiteboard. * [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanc...") |
|||
| Line 22: | Line 22: | ||
=== Developer sign up === | === Developer sign up === | ||
In solitude: | |||
* Add in an API to check the status of user given a Boku account number. | |||
* Store the Boku merchant number in solitude, related to the developer account. | |||
* Add in APIs to lookup Boku account details for a developer from zamboni and webpay. | |||
In the developer hub: | |||
* Change the Django models to allow assignment of multiple payment accounts to an app {{bug|969041}} | * Change the Django models to allow assignment of multiple payment accounts to an app {{bug|969041}} | ||
* When creating a payment account, allow developers to choose | * Alter settings to allow multiple payment providers. | ||
* When creating a payment account, [https://www.dropbox.com/s/3s2en1l4ppwy90v/Screenshot%202014-03-20%2012.27.16.png allow developers to choose] between providers. | |||
* Alter the API to speak to solitude APIs when creating accounts. | |||
* Alter the price tier screen to show carrier or payment provider. | |||
==== Extra points ==== | ==== Extra points ==== | ||
* Implement full developer payment choice in the hub, as specced in podio, tracking {{bug|963203}} | * Implement full developer payment choice in the hub, as specced in podio and mocked out by Bram, tracking {{bug|963203}} | ||
=== Payment choice === | === Payment choice === | ||
Revision as of 19:36, 20 March 2014
Boku: http://boku.com/
UX
Bugs
- Put [boku] in whiteboard.
- List of bugs
Boku API
Payment API
Marketplace changes
This is a list of the changes that we'd need to make to the Marketplace. This is a non-exhaustive brain dump that was quite exhausting to do, but serves as a jumping off point for bugs, still to be filed.
Some of these points are broken into two parts. The minimum we need to do and what we'd like to do.
Developer sign up
In solitude:
- Add in an API to check the status of user given a Boku account number.
- Store the Boku merchant number in solitude, related to the developer account.
- Add in APIs to lookup Boku account details for a developer from zamboni and webpay.
In the developer hub:
- Change the Django models to allow assignment of multiple payment accounts to an app bug 969041
- Alter settings to allow multiple payment providers.
- When creating a payment account, allow developers to choose between providers.
- Alter the API to speak to solitude APIs when creating accounts.
- Alter the price tier screen to show carrier or payment provider.
Extra points
- Implement full developer payment choice in the hub, as specced in podio and mocked out by Bram, tracking bug 963203