# Configure IAP Platform Settings

In this how-to, we will enable and configure Google Play Store in LootLocker so it can be used to handle in-app purchases.

### Prerequisites

* [A LootLocker account](https://lootlocker.com/sign-up)
* At least one created game in the [LootLocker Web Console](https://console.lootlocker.com/)
* A [Google Play Developer Account](https://play.google.com/console/about/)

### Configure IAP Settings in LootLocker

In the LootLocker Web Console, navigate to Settings and select In-App Purchases.

<figure><img src="/files/rrd5i4QhG6txhLod8EH9" alt=""><figcaption></figcaption></figure>

Select Google Play Store from the list of available providers.

### Configure Google Play Store Settings

Fill in the following fields:

* **Test Purchases:** Enables Google Play test (sandbox) purchases. Use this during development to validate purchase flows without charging real users.
* **Package Name:** The unique identifier for your Android app (e.g., `com.yourcompany.yourgame`). This must match the package name configured in your app and in Google Play Console.
* **Type:** The type of Google Cloud credential. This should be set to `service_account`, which is required for server-to-server communication with Google Play.
* **Project ID:** Your Google Cloud project ID associated with your app and Google Play Developer account.
* **Private Key ID:** The identifier for the service account private key. This is included in the JSON key file generated in Google Cloud.
* **Private Key:** The `.p8` private key from your Google Cloud service account credentials. Upload the key file here (Base64 encoded). This is used to authenticate requests to Google Play APIs.
* **Client Email:** The service account email address (e.g., `service-account@project-id.iam.gserviceaccount.com`). This account must be granted access to your app in the Google Play Console.
* **Client ID:** The OAuth 2.0 client ID associated with the service account.
* **Auth URI:** The OAuth 2.0 authorization endpoint. Typically: `https://accounts.google.com/o/oauth2/auth`
* **Token URI:** The OAuth 2.0 token endpoint used to obtain access tokens. Typically: `https://oauth2.googleapis.com/token`
* **Auth Provider x509 Cert URL:** The URL for Google’s OAuth 2.0 public certificates. Typically: `https://www.googleapis.com/oauth2/v1/certs`
* **Client x509 Cert URL:** The URL for the service account’s public certificate.
* **Universe Domain:** The Google Cloud universe domain. Typically: `googleapis.com`

{% hint style="warning" %}
These values are provided in the JSON key file when you create a service account in Google Cloud. You can copy them directly or upload the file where supported.\
The service account must be granted access in the Google Play Console under *Users and Permissions*, with permissions to manage in-app purchases and subscriptions.
{% endhint %}

Once all required fields have been filled in, click the Enable toggle to enable Google Play Store as a purchase provider for your game.

Click Save Changes to save your configuration.

### Conclusion

In this guide, we enabled Google Play Store for in-app purchases and configured the required settings in LootLocker. Next, you can [create purchasable catalog listings](/commerce/real-money-purchases/how-to/google-play-store/configure-catalog-listing-google-play-store.md) that can be purchasesd in-game.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lootlocker.com/commerce/real-money-purchases/how-to/google-play-store/configure-google-play-store-iap-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.