-
chattymango Oct 4, 2018Hi, is there any progress regarding the seller API? I would particularly need to check if a person is really a buyer and also to restrict automatic updates only to people who have bought the item and to be abled to exclude people who received a refund. Thanks!
-
We are first going to implement a solution for being able to check if a user is indeed a buyer. We are currently busy designing this, but there are some privacy issues.
How would the sellers like to have this implemented? Any ideas are welcome.This post has been last edited at 2018-10-04 09:36:04 -
chattymango Oct 4, 2018Thank you!
I think that the check if a user is indeed a buyer could be done via the buyer's email address. We contact the API with the hashed email address and a software item ID and the result is information (perhaps JSON) like purchase date, license type and status (purchase initiated, purchase completed, refunded), or an error message if this email is unknown.
For the verification process for updates it would be necessary to send a purchase ID to the API that must match the item ID. This would also return a status, sth. like valid or invalid and the license type. Buyers would receive the purchase ID after the purchase or see it in the list of downloads and then they can copy it to the settings of the software that they bought. This must be non-public information (not the email) because otherwise it would be too easy to guess the license of other people.
This all assumes that every buyer can buy every item only once.
For the email check it would be necessary that the seller is authenticated so that he can see only information about buyers or purchases of his own items. For the update check it should be without authentication so that the software can check autonomously.This post has been last edited at 2018-10-04 11:49:55 -
Codeguru43 5 months agoPlease is there any update on this?