777007 - Process refund for purchased B2G app

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Payments/Refunds, defect, P1)

Description

[Kumar McMillan [:kumar]]

To initiate a refund for a B2G app, Marketplace should call nav.pay() with a refund request. Spec: https://wiki.mozilla.org/WebAPI/WebPayment#Refunds

Marketplace will pass in its own chargeback URL as part of the request. When a refund notification is received from BlueVia, all normal receipt processing should take place (receipt issued, tracked, etc), then Marketplace will notify the developer by posting to the stored chargeback URL on record for that developer. That is, the chargeback URL the developer signed up with through the developer pages.

Comment 1

[Kumar McMillan [:kumar]]

Notifying the dev through a chargeback URL is optional since they might not have set up that URL. We can probably punt on notifications to keep this simple.

Comment 2

[Kumar McMillan [:kumar]]

This is how nav.pay() is currently implemented for purchases: https://github.com/kumar303/zamboni/commit/eb3cbf3b

We'll need to add a similar frontend/backend dance on mkt's purchase history page when the user clicks 'refund.' If it's easier, let's split up bugs for frontend/backend.

The frontend will call nav.pay() according to spec (see link above). Like purchasing, it will need to poll to wait for the chargeback notification.

The chargeback notification will need to verify the JWT signature and process the refund (invalidate receipt, etc).

Comment 3

[Kumar McMillan [:kumar]]

well, the polling might be different in the refund case. When the user clicks the refund button on our site maybe we just say "your refund is pending..."

Comment 4

[Kumar McMillan [:kumar]]

For reference, this is how the app install postback URL was implemented https://github.com/kumar303/zamboni/commit/04aa011e#L5R80 The chargeback is pretty much the same thing just with refund processing.

Comment 5

[Andy McKay]

Back end: https://github.com/mozilla/zamboni/commit/aacaa0