> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/help/knowledge-base/deploy-your-app-to-the-google-play-store.md).

# Deploy your app to the Google Play Store

## Overview

Use this guide to publish your **digital wallet application** on Google Play.

Pay special attention to application signing. The signing certificate impacts the **application binding key** used by NFC Wallet.

{% hint style="warning" %}
If you change the signing key after onboarding, NFC Wallet flows can fail on devices.

Align your Google Play signing setup with the key you registered with Thales.
{% endhint %}

## Prerequisites

Before you start:

* Ensure you have access to [Google Play Console](https://play.google.com/console/).
* Decide whether you publish an Android App Bundle (AAB) or APK.
* Confirm the **application binding key** you shared with Thales.
  * See [Compute the application binding key](/nfc-wallet-sdk-android/help/knowledge-base/compute-the-application-binding-key.md).

## Create the app in Google Play Console

1. Open [Google Play Console](https://play.google.com/console/).
2. Select **All apps** > **Create app**.
3. Set the default language.
4. Enter the app name as it should appear on Google Play.
5. Select whether the app is an **app** or a **game**.
6. Select whether the app is **free** or **paid**.
7. Add a contact email address for end users.
8. Complete the required declarations (for example, content guidelines and export compliance).
9. Select **Create app**.

## Set up store listing and compliance

Use the app dashboard to complete the required sections:

* Store listing details
* App content questionnaires
* App access and privacy declarations
* Target audience and content rating

Google blocks release creation until required items are completed.

## Create a release (closed testing)

1. In Google Play Console, select **All apps** > your app.
2. In the left menu, select **Testing** > **Closed testing**.
3. (Optional) Create a new testing track, then select **Create new release**.

### Configure app signing

Choose the option that matches how you want Google Play to sign the version installed by end users.

{% tabs %}
{% tab title="AAB (recommended by Google)" %}
If you use Google Play App Signing, ensure the **app signing key** matches the key you registered with Thales.

In **App integrity** > **App signing**, select **Export and upload a key from Java keystore**.

Follow the on-screen instructions to upload your signing key.
{% endtab %}

{% tab title="APK" %}
If you publish APKs, decide whether to use Google Play App Signing.

If you **opt out** of Play App Signing, the APK you upload is the APK installed by end users.

Ensure the APK signing key matches the key you registered with Thales.
{% endtab %}
{% endtabs %}

### Upload artifacts and start rollout

1. Upload your build artifacts:
2. Enter the release name in **Release details**, then select **Save**.
3. Select **Review release**.
4. Review warnings and errors, then select **Start rollout**.

Your release is now submitted for review.

After Google approves it, you can distribute it to testers (closed testing) or proceed to a production rollout.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.payments.thalescloud.io/nfc-wallet-sdk-android/help/knowledge-base/deploy-your-app-to-the-google-play-store.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.