1046905 - developer visibility into in-app payment flow failure

Status: RESOLVED DUPLICATE of bug 1063140

(Marketplace Graveyard :: Developer Pages, defect)

Description

[(not reading bugmail) Nick Desaulniers [:\n]]

Sometimes, an app with IAPs has different developers or even different companies implementing the client and the server.  When the developer of the client has working code, but the server does not respond to the postbackURL, it can be very difficult for the client side developers to know what is going wrong.  This is because they don't (and shouldn't) have access to Mozilla's logs, and the server's logs.  How can we make this use case easier to debug?

My thoughts:
The client can decode but not modify a jwt.  If the jwt has a simulate field, expose a page that will only display simulated payment requests given an application key.  ie:

Insert your application key: [______]
Server logs:
...
...
400 server postbackURL (is your server set up to process postbacks? see: https://developer.mozilla.org/en-US/Marketplace/Monetization/In-app_payments_section/mozPay_iap#Processing_chargebacks_on_the_server)

Comment 1

[Kumar McMillan [:kumar]]

Great idea. We could add a status/explanation of the last couple simulation attempts to the Developer Hub in the in-app payments section.

Comment 2

[Kumar McMillan [:kumar]]

oops, we have a dupe of this