Difference between revisions of "In-App Purchase"
m |
m |
||
| Line 11: | Line 11: | ||
| Google strongly recommends to verify who the user who did the purchase, by adding and generating extra information about the purchase (aka [https://developer.android.com/google/play/billing/billing_best_practices.html#payload Developer Payload]). | | Google strongly recommends to verify who the user who did the purchase, by adding and generating extra information about the purchase (aka [https://developer.android.com/google/play/billing/billing_best_practices.html#payload Developer Payload]). | ||
| − | It's also recommended to have an "own secure server | + | It's also recommended to have an "own secure server" to track of purchases. |
|} | |} | ||
==See Also== | ==See Also== | ||
*[[Android]] | *[[Android]] | ||
[[Category:Dev]] | [[Category:Dev]] | ||
Revision as of 22:53, 9 February 2017
Comparison of In-app Purchase APIs.
| Feature | Apple's Store Kit (IAP) | Google Play |
|---|---|---|
| User Validation | Apple doesn't require a developer to implement any user validation.
A developer should always trust the Store Kit about the fact of who made a purchase. |
Google strongly recommends to verify who the user who did the purchase, by adding and generating extra information about the purchase (aka Developer Payload).
It's also recommended to have an "own secure server" to track of purchases. |
