Confirm
1,158
edits
Changes
→Data Fields
A receipt encodes an affirmation by a payment processor that a particular user has completed a transaction to acquire a particular digital product. It contains the following fields:
* <tt>typ</tt>: MUST be the string one of <tt>"purchase-receipt"</tt>, <tt>"developer-receipt"</tt>, <tt>"reviewer-receipt"</tt>, <tt>"test-receipt"</tt>.
* <tt>product</tt>: A JSON object identifying the product the receipt covers and any store specific data.
* <tt>user</tt>: A JSON object containing an identifier that the issuing store can use to identify the user associated with this receipt.
* <tt>verify</tt>: (optional) A URL that can be used by an authenticated application to verify a receipt
* <tt>reissue</tt>: (optional) A URL that can be used to re-issue a new receipt
=== the typ field ===
The <tt>typ</tt> identifies the type of the receipt. Not all types of receipts need to be accepted.
* <tt>purchase-receipt</tt>: A receipt issued when a transaction is completed. This type of receipt should be accepted by the app at all times.
* <tt>developer-receipt</tt>: A receipt issued to the developer of the app. Usually they will be issued by the store for the use of the developer. This receipt may have a short expiry.
* <tt>reviewer-receipt</tt>: A receipt issued to the reviewer of the app. Usually they will be issued by the store for reviewers of the app. This receipt only needs to be accepted during the review period. This receipt may have a short expiry.
* <tt>test-receipt</tt>: A receipt issued to test the app during development. This receipt SHOULD NOT be accepted, except during development. This receipt may have a short expiry.
=== the product field ===
