> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reyapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Your Google Play Developer Account

> Sign up for a Google Play Developer account so you can publish your Rey app to Google Play. Walk through enrollment, identity verification, and the one-time 25 USD fee.

Before you can publish to Google Play, you need an active **Google Play Developer account**. This is the account that owns your app listings, release tracks, and Play Console access. Enrollment costs a **one-time 25 USD fee** and typically takes a few days to be verified.

You only need to do this **once** — all future apps you publish through Rey use the same account.

## Prerequisites

* A **Google account** with two-step verification enabled. Create one at [accounts.google.com](https://accounts.google.com) if you don't have one.
* A **credit or debit card** to pay the one-time 25 USD registration fee.
* Government-issued **photo ID** for identity verification.
* If enrolling as an organization: your **legal business name**, address, and a **D-U-N-S Number**.

## Choose an account type

Google offers two account types. Choose based on how you want your app to appear on Google Play.

<AccordionGroup>
  <Accordion title="Personal">
    Your legal name appears as the developer on Google Play. Best for solo developers, indie makers, and side projects. Identity verification typically completes within a few days.
  </Accordion>

  <Accordion title="Organization">
    Your company or legal entity name appears as the developer. Required if you want a company name (e.g. “Rey Labs, Inc.”) on your Play Store listing. Requires a [D-U-N-S Number](https://developer.apple.com/support/D-U-N-S/) and can take longer to verify while Google confirms your business details.
  </Accordion>
</AccordionGroup>

<Tip>
  If you're not sure, start as a Personal account. You cannot convert a Personal account to an Organization later, but you can create a separate Organization account and transfer apps.
</Tip>

## Enroll in the Google Play Developer program

<Steps>
  <Step title="Sign in with your Google account">
    Go to [play.google.com/console/signup](https://play.google.com/console/signup) and sign in with the Google account you want to use for the developer account.
  </Step>

  <Step title="Choose your account type">
    Select **Personal** or **Organization**. If you choose Organization, you'll be prompted for your legal entity name and D-U-N-S Number.
  </Step>

  <Step title="Enter developer details">
    Provide your public developer name (shown on your Play Store listing), contact email, phone number, and website if you have one.
  </Step>

  <Step title="Verify your identity">
    Upload a government-issued photo ID and, for Organizations, business verification documents. Google reviews these before activating your account.
  </Step>

  <Step title="Pay the 25 USD registration fee">
    Enter your payment details and complete the one-time purchase. Unlike Apple, this is not a recurring fee.
  </Step>

  <Step title="Wait for approval">
    Personal accounts are typically verified within a few days. Organization accounts may take longer while Google confirms your business details. You'll receive an email when your account is active.
  </Step>
</Steps>

<Warning>
  Google requires all new personal developer accounts to complete **closed testing with at least 12 testers for 14 days** before you can publish to production. Plan for this timeline before your launch date.
</Warning>

## After enrollment

Once your account is active, you can:

* Sign in to the [Google Play Console](https://play.google.com/console) to manage your apps.
* Continue to [Register a Package Name](/publishing/app-stores/play-store/register-bundle-id) so Google has a unique identifier for your Rey app.
* Then [Register Your First App](/publishing/app-stores/play-store/register-first-app) in the Play Console.

<Tip>
  You can invite Rey team members to your Play Console under **Users and permissions**. Use the **Admin** role for owners and **Release manager** for anyone submitting builds.
</Tip>