Aucune description
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
APPLE c9d5bdcd60 va il y a 1 an
..
.sample.json va il y a 1 an
DetectingFraud.unity va il y a 1 an
DetectingFraud.unity.meta va il y a 1 an
FraudDetection.cs va il y a 1 an
FraudDetection.cs.meta va il y a 1 an
README.md va il y a 1 an
README.md.meta va il y a 1 an
User.cs va il y a 1 an
User.cs.meta va il y a 1 an
UserWarningGooglePlayStore.cs va il y a 1 an
UserWarningGooglePlayStore.cs.meta va il y a 1 an

README.md

README - In-App Purchasing Sample Scenes - Google Play Store - Fraud Detection

This sample showcases how to provide to the Google Play Store your user’s identifiers to help prevent fraud using the Google Play Store extension.

Instructions to test this sample:

  1. Have in-app purchasing correctly configured with the Google Play Store.
  2. Configure a product.
  3. Set your own product’s id in the InAppPurchasing game object > Fraud Detection script > Gold Product Id field or change the goldProductId field in the FraudDetection.cs script.
  4. Build your project for Android and make sure the GooglePlayStore is selected*.
*You can change the currently selected store under Services > In-App Purchasing > Configure and changing the Current Targeted Store field.

Google Fraud Detection

To help prevent fraud, it is useful to provide to Google the in-app account and/or profile identifiers of your user. This helps Google map the user’s Google Play account to their in-app account.

The account and profile ids must not contain personally identifiable information such as emails in cleartext. To prevent this, Google Play recommends that you use either encryption or a one-way hash to generate an obfuscated identifier to send to Google Play.

For more information see Google’s documentation on the subject.