Skip to main content

Google Account Setup and Requirements for Your Android Branded App

Learn how to set up your Google Developer Account, invite Swapcard, and configure permissions and service account keys to publish and manage your Android branded app efficiently.

Updated yesterday

Table of Contents

  1. Before you start

  2. Setting up your Google Developer Account

  3. Inviting Swapcard to your Developer Account

  4. Granting permissions

  5. Creating and uploading a Service Account Key

  6. Managing multiple apps

  7. Common mistakes to avoid


1. Before you start

⚠️ Important: Swapcard can work with organizational Google Developer Accounts.

Personal developer accounts (registered under an individual’s name) are not supported.

To publish your branded Android app on the Google Play Store, your organization must have an active Google Play Developer Account.

This guide walks you through account setup, access management, and creating a service account key to allow Swapcard to manage your app submission and updates.


2. Setting Up Your Google Developer Account

If your organization doesn’t already have one, visit the Google Play Console and register as an organization.

Steps:

  1. Create or use an existing Google Account owned by your organization (not a personal one).

  2. Pay the one-time registration fee of $25 USD.

  3. Complete organization verification:

    • Provide your legal entity name, address, and website.

    • Wait for verification approval (status must show as Verified before continuing).


3. Inviting Swapcard to Your Developer Account

Once your developer account is verified:

  1. Log in to your Google Play Console.

  2. On the left side of the page, select Users and Permissions.

  3. Click Invite new user.

  4. Enter the email: android@swapcard.com

  5. Assign the Admin role and click Invite user.

If you prefer not to give full Admin access, you can:

  • Create the app skeleton first (under your account).

  • Then grant Swapcard App-level permissions to that specific app with the ability to edit and publish.

Both methods work, but Admin access ensures a smoother submission process.


4. Granting Permissions

When assigning access (just for app-specific), make sure these permissions are enabled:

  • View app information and performance

  • Edit store listing

  • Manage releases

  • Manage Play Games Services (optional but recommended)

  • Manage production, testing, and tracks

  • Manage Play Integrity

Confirm that Swapcard’s account has access to create and edit releases, otherwise the submission will fail during upload.


5. Creating and Uploading a Service Account Key

To allow Swapcard to manage apps on your Play Store account, you'll need to create a service account key. This guide will walk you through the steps to create the project, enable APIs, create the key, and invite the service account to manage your Play Store apps.

Click on the arrow below to display the instructions 🔽

Step 1: Create a Google Cloud Project

  1. Go to the Google Cloud Console:

  2. Create a New Project:

    • Click on the project drop-down at the top of the page.

    • Click on New Project.

    • Enter a name for your project (e.g., "Swapcard Play Store Management").

    • Select your billing account if prompted.

    • Click Create.

Step 2: Enable APIs

  1. Enable the Google Play Android Developer API:

    • In the Google Cloud Console, navigate to the APIs & Services > Library.

    • Search for "Google Play Android Developer API".

    • Click on Google Play Android Developer API and then click Enable.

Step 3: Create a Service Account

  1. Navigate to the Service Accounts Page:

    • In the Google Cloud Console, go to IAM & Admin > Service Accounts.

  2. Create a Service Account:

    • Click + Create Service Account.

    • Enter a service account name (e.g., "swapcard-service-account").

    • Click Create and Continue.

  3. Grant the Service Account Access to the Project:

    • Select the role Owner for the service account.

    • Click Continue and then Done.

Step 4: Create a Service Account Key

  1. Navigate to the Service Accounts Page:

    • In the Google Cloud Console, go to IAM & Admin > Service Accounts.

  2. Generate a Key:

    • Find your service account in the list.

    • Click on the three dots on the right side of the service account row and select Manage keys.

    • Click Add Key > Create New Key.

    • Select JSON and click Create.

    • The JSON key file will be downloaded automatically. Keep this file safe, as you will need it to configure access.

    • Upload JSON Key to Event Studio:

      • Go to Studio > Applications.

      • Click on the relevant app, then go to General > Mobile Settings.

      • Upload the Service Account JSON file in the dedicated input field.

  • Verify Permissions: Go back to the Google Play Console and ensure that the service account is listed under Users and Permissions with the Admin role.

Step 5: Invite the Service Account to the Play Store

⚠️ Please make sure to follow these steps carefully. Even though you have already invited the Android Swapcard account, this task still needs to be completed because, in this case, you need to invite the service account email from 👉 Step 3.

  1. Go to the Google Play Console:

  2. Invite the Service Account:

    • Navigate to Settings > Users and permissions.

    • Click on Invite New User.

    • Copy the email address generated on your Google Cloud Console.

    • Assign the role Admin

    • Click Send Invite.

That's it! You've successfully created a service account key and invited it to manage your Play Store apps on behalf of Swapcard. If you have any questions or run into any issues, please contact our support team for assistance.


6. Managing Multiple Apps

If your organization plans to publish multiple branded apps under the same developer account, you can reuse the same Service Account Key for all of them.

✅ There is no need to generate a new key for each app, as long as:

  • The key is active.

  • The linked project is still valid.

  • Permissions haven’t been revoked.


7. Common Mistakes to Avoid

⚠️ Using a personal developer account: Only organizational accounts can be used.

⚠️ Missing Service Account Key: Without the JSON file uploaded to Studio, automatic updates can’t run.

⚠️ Unverified organization: Ensure your organization verification is marked as “Verified.”

⚠️ Incorrect permissions: Confirm Swapcard has publishing access for the app.


8. After Setup

Once access and the Service Account Key are configured, Swapcard will:

  • Build your Android app

  • Upload the app to your Play Console

  • Handle release management and version updates

  • Monitor publishing and review status

💡 Status definitions in Studio:

In Review: Google is reviewing your app.

Published: App is live on the App Store.

Outdated: A new version is needed or awaiting publication.

Tip: If your app stays “Outdated” longer than expected, verify if a release is still waiting for approval in your Play Console.

Did this answer your question?