[rfc] [marketplace] [dev-webapps] User Stories for Payment Sandbox

[David Bialer]

Hi there,
Bill Maggs and I wanted to capture requirements for a developer to be able to test in app payments using a payment sandbox. This is based on some of the thinking that Kumar and others have done on using the 'simulate' parameter in a JWT to test, but isn't that specific to the method of testing.

Please review these user stories.


1. As a developer, I want to simulate an In App Purchase (IAP) process in any region of the world supported by FF Marketplace.  P1
2. As a developer, I want to be able to generate a secret key for a JWT to test my IAP.  P1
3. As a developer, I want to display the correct amount and currency unit for IAP for the region and price tier I have chosen. P1
4. As a developer, I want to simulate IAP on a production serverd. P1
(child) As a developer, I want to be able receive simulate a successful payment a with postbacks that show the success condition.
(child) As a developer, I want to be able to simulate an unsuccessful payment with error conditions (i.e. Item unavailable, Payment denied (reason), Payment Cancelled, etc)
(child) As a developer, I want to receive simulate chargebacks with all possible error conditions.
5. As a developer who wants to implement their own IAP (not FFX),  I would like clear instructions for me and my payment provider to test an alternative moz.pay implementation in my own sandbox by using our WebPayment API. P1

6. As a developer, I want a tool to check that my payment JWT is formatted correctly. P2
7. As a developer, who wants to use FF Marketplace Payments for IAP, I want to be able to test IAP on my app without a lengthy registration process on Bango or having to set up a bank account. P2
8. As a developer, I want to be able to simulate IAP in FF OS Simulator by setting my location or other changing other regional settings. P2
9. As a developer, I want to be able to be able determine the correct amount and currency (symbol) to display on my "Buy" button, given a price tier, based on the location of the device. P1

Thanks for your time in reviewing this,
David

[Maria Sandberg]

[+ Tony and Bram] - Not sure if they are on the dev lists.

---
Maria Sandberg
UX Designer, Fx Marketplace
Mozilla Corporation

> _______________________________________________
> dev-marketplace mailing list
> dev-mar...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-marketplace

[Bram Pitoyo]

All this product requirement makes sense, but just to ask a few clarification:

1. Is the IAP simulator a webapp that we will need to create and design for?
2. We have a wealth of Marketplace developer tools. How will this
simulator fit within the existing DevHub structure? How is it
accessed? Are there feature overlaps that already exist in other tools
that we can take advantage of?

[Bram Pitoyo]

> […] a possible new tool that will validate a payment JWT. Also
> possibly some part of the dev dashboard that will allow developers get
> keys. This may be needed for other services later - like Push Messaging.
> […]

This service could easily be tied in with the submission flow.

For example, if you check the “in-app payment” box, or if we detect
the use of Push API in your app, then we can show you the test key
generator and the JWT validator on devhub. Otherwise, you will see the
normal interface.


On Tue, Feb 5, 2013 at 6:05 AM, David Bialer <dbi...@mozilla.com> wrote:
> See below

>
> ----- Original Message -----
>> All this product requirement makes sense, but just to ask a few
>> clarification:
>>
>> 1. Is the IAP simulator a webapp that we will need to create and
>> design for?

> It should use the Firefox OS simulator. The in-app payments will need some work on the Dev Dashboard to
> a: get a payment key (or possibly test key that doesn't require a bank acccount registration)
>
> It will require simulator work to:
> a. simulate location
> b. possibly simulate network
>
> It will require work on the production payment server to accept the simulator commands proposed by Kumar and return success and error codes.
>
> It may require work to have a JWT validator

>
>
>> 2. We have a wealth of Marketplace developer tools. How will this
>> simulator fit within the existing DevHub structure? How is it
>> accessed? Are there feature overlaps that already exist in other
>> tools
>> that we can take advantage of?

> Yes see above. Mostly the simulator. But a possible new tool that will validate a payment JWT. Also possibly some part of the dev dashboard that will allow developers get get keys. This may be needed for other services later - like Push Messaging. So we should think about it as Value Added services on a per application basis.

[David Bialer]

An International Content Rating System PRD is open for comments.
https://docs.google.com/a/mozilla.com/document/d/1Dqg-U-zdinUwG3DO94SBmUf0irtwqw5A_YxIW60-qhU/edit#heading=h.xzjndkrswa6n

or accessible from the Marketplace Wiki page: https://wiki.mozilla.org/Marketplace#Content_Rating

It is based on work previously scoped by Justin Scott and further enhanced to include more details about an International Content Rating capability that is being pioneered by the Entertainment Software Ratings Board (ESRB). They have a very nice ratings tool that allows developers to self-generate a rating and certificate, that would output different international ratings (Brazil, Europe, North America, others), and enable developers to receive ratings for different regions of the world without a lot of hassle, paperwork, or delay.

While ratings support is not scheduled to deploy until Q3 or Q4, I am strangely excited about this, so wanted to get the PRD going so our integration work can start in Q2.

I have more details on the technical integration for those who are interested.

A demo is available here: https://autoratingtool.esrb.org/iarcdemo3/.

Please excuse my typos in the document.

Thanks in advance to those who wish to contribute to this,
David