We think we need to change Web Application Receipts [0]. We’d like to add in the ability for in-app payments to use receipts [1] so that in-app payments can be done without a developer needing a server, now that new receipt manipulation code has landed [2].
In this scenario there will be multiple receipts for an app, one for the purchase (if a paid app) and one for each in-app purchase. Currently however there is no way to distinguish what the receipt is for, the spec just shows that the receipt is for the an app on a domain (the product > url field) [3]. Both the verifying service and the app need to be able distinguish if the receipt is for an app purchase or one of multiple in app purchases. For the verifying service, we are going to extend the product > storedata field to include more store data. Since we had that space reserved, no big deal. For the app, we are planning on adding a new field to the product field, specifically a clientdata field to include some client specific data. It will just be a string, it will be up to the marketplace to decide what goes in there. In the case of Firefox Marketplace we are currently deciding if that should be a developer provided slug or a marketplace provided URL. Any feedback welcome. Andy [0] https://wiki.mozilla.org/Apps/WebApplicationReceipt [1] https://bugzilla.mozilla.org/show_bug.cgi?id=944480 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=757226 [3] https://wiki.mozilla.org/Apps/WebApplicationReceipt#the_product_field
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
