Confirmed users
1,158
edits
Apps/WebApplicationReceipt: Difference between revisions
Jump to navigation
Jump to search
Apps/WebApplicationReceipt (view source)
Revision as of 23:53, 11 September 2013
, 11 September 2013→Interaction with the verify URL
No edit summary |
|||
| Line 124: | Line 124: | ||
* <tt>status</tt>: A string, containing one of the values "ok", "pending", "refunded", "expired" or "invalid". | * <tt>status</tt>: A string, containing one of the values "ok", "pending", "refunded", "expired" or "invalid". | ||
* <tt>reason</tt>: An optional field, normally only populated when a receipt is invalid, this will give you a reason it failed. | |||
Application-level authentication on the verifyURL request is not strictly required, as the possession of a receipt proves that the application is already part of a trusted message flow. | Application-level authentication on the verifyURL request is not strictly required, as the possession of a receipt proves that the application is already part of a trusted message flow. | ||