794651 - [meta] implement Marketplace payment provider for navigator.mozPay()

Status: RESOLVED FIXED

(Marketplace Graveyard :: Payments/Refunds, defect)

Description

[Kumar McMillan [:kumar]]

When an app initiates payments with navigator.mozPay() and their JWT points to Marketplace, Marketplace should host the payment flow. Spec: https://wiki.mozilla.org/WebAPI/WebPaymentProvider

For UX flows and info: https://wiki.mozilla.org/Apps/ID_and_Payments

Comment 1

[Kumar McMillan [:kumar]]

This was built once before in bug 742056 and we can re-use the backend (and some frontend?) because the JWT interaction is the same

Comment 2

[David Lozano]

I don't know if this is the place for these comments (if not, just let me know)

After reviewing the UX flows, some comments:
- having to confirm the app installation in the last Gaia screen looks redundant for paid applications, as the user has previously acknowledged the operation with a PIN and clicked the Buy button. Don't know if it is feasible to skip this last step in v1, but the resulting UX would be better.
- more importantly, if the user clicks cancel in the last screen after having successfully paid for the app download, what happens if she clicks download again in the app details page? I guess we will follow the free app flow in order not to charge the user twice, won't we?
- finally, just to remember that it should be nice to be able to ask for the PIN right after presenting the payment details (I know this fully depends on the tech integration details)

Comment 3

[Kumar McMillan [:kumar]]

(In reply to David Lozano from comment #2)
> - having to confirm the app installation in the last Gaia screen looks
> redundant for paid applications, 

Yep, this is tricky to address so it will probably remain as is for V1

> - more importantly, if the user clicks cancel in the last screen after
> having successfully paid for the app download, what happens if she clicks
> download again in the app details page? 

she will be able to install the app immediately

> - finally, just to remember that it should be nice to be able to ask for the
> PIN right after presenting the payment details (I know this fully depends on
> the tech integration details)

We're working this out with the payment processor. It will probably remain as is for V1

Comment 4

[Jason Smith [:jsmith]]

Meta bugs do not block ship, as they are not quantifiable units in themselves for implementation work. Please nom/+ bugs that are actual units of work (aka the bugs under this bug could be candidates).