Confirmed users
65
edits
Apps/WebApplicationReceipt: Difference between revisions
Add an explicit list of supported URL schemes
RyanTilder (talk | contribs) (Add an explicit list of supported URL schemes) |
|||
| Line 31: | Line 31: | ||
The <tt>product</tt> field identifies the digital good whose sale is represented by the receipt. It is a JSON object structure, containing the following fields: | The <tt>product</tt> field identifies the digital good whose sale is represented by the receipt. It is a JSON object structure, containing the following fields: | ||
* <tt>url</tt>: A URL representing the root of a domain, without a trailing slash (e.g. <tt>"https://someapp.com"</tt>), is conventionally defined to represent "a web application"; URLs rooted further inside the site are conventionally defined to represent "in-application purchases", and can use whatever path scheme is convenient to the developer and issuer of the receipt. | * <tt>url</tt>: A URL representing the root of a domain, without a trailing slash (e.g. <tt>"https://someapp.com"</tt>), is conventionally defined to represent "a web application"; URLs rooted further inside the site are conventionally defined to represent "in-application purchases", and can use whatever path scheme is convenient to the developer and issuer of the receipt. Currently the following URLs schemes are supported: http://, https://, and app://(for packaged apps) | ||
* <tt>storedata</tt>: A string that uniquely identifies this app for the verifier of the receipt. | * <tt>storedata</tt>: A string that uniquely identifies this app for the verifier of the receipt. | ||