Confirmed users
491
edits
Apps/WebApplicationReceipt/GenerationService: Difference between revisions
Jump to navigation
Jump to search
Apps/WebApplicationReceipt/GenerationService (view source)
Revision as of 20:35, 28 March 2012
, 28 March 2012→System Overview
m (→Action Items) |
|||
| Line 22: | Line 22: | ||
Alternatively, the developer can POST the receipt to a URL specified in the receipt (the verify_url). This is a service, hosted by Marketplace, which will: | Alternatively, the developer can POST the receipt to a URL specified in the receipt (the verify_url). This is a service, hosted by Marketplace, which will: | ||
# Verify the receipt and certificate chain | |||
# If verification succeeds, retrieve the business state of the receipt (one of okay, refunded, rejected, invalid) (XX language check here) | |||
# Report back the verification of the receipt and the business state of the receipt. | |||
(NB to Marketplace team: If there is going to be a developer-facing API to query the state of individual receipts by user ID, it will need to have a developer-facing authentication piece. This system does not require authentication; possession of the receipt is considered sufficient to find out the user's status). | (NB to Marketplace team: If there is going to be a developer-facing API to query the state of individual receipts by user ID, it will need to have a developer-facing authentication piece. This system does not require authentication; possession of the receipt is considered sufficient to find out the user's status). | ||