01
Type first
Name personal, organization, already-has-an-app, or pre-Nov-2023 before we talk papers.
Aligned with Google Play Console
Pick a personal or organization account, finish identity checks, run closed testing when Google asks for it, then upload an App Bundle and request production. Dev388 writes the path in English first; your browser language is used when we support it.

01
Name personal, organization, already-has-an-app, or pre-Nov-2023 before we talk papers.
02
Fees, tester counts, and document lists come from the live Play Console page — not a screenshot from last year.
03
We consult on Telegram. This site does not list inventory, a price grid, or a checkout.

Personal
Solo builders. New personal accounts usually need device verification and a 12-tester × 14-day closed test before production.

Organization
Companies and teams. Expect a D-U-N-S number, matching legal name, and shared Console permissions.

With an app
Keep the package name, signing, and store listing in sync. Watch 2026 target API and verification mail from Google.

Before Nov 2023
Often called an account with an existing production app. The 12×14 personal-test gate does not apply the same way — verification and policy still do.
Personal, organization, an account that already has an app, or a personal account opened before 13 November 2023.
Keep one Google account, a card Google Payments accepts, and matching names. Organizations need a D-U-N-S number.
Agreement, one-time fee, identity, then store listing, tracks, App Bundle, and the production request.
Telegram @dev388: account type, payments-profile country, and the Console screen that froze. Do not send passwords.
Personal, organization, already has an app, or opened before 13 November 2023.
Package name and whether production is already green. That changes the 12×14 gate.
The country on the Google Payments profile should match the developer profile.
A screenshot of the Console page that froze. Never passwords or backup codes.
Personal
Organization

Personal vs organization, the $25 Play registration fee, and the documents Console actually asks for.

Store listing, tracks, App Bundle, and the production checklist.

Title, short and full description, screenshots, and localized copy.

Read a policy rejection, fix what Google named, resubmit without guesswork.

Payments profile, users and permissions, and the fields that stall a first release.

Staged rollouts, tracks, and day-to-day release hygiene.
Written for the real Console, not a slide deck.
Every fee and test gate is labeled as Google’s, not ours.
Steps you can hand to a teammate without rewriting.
Built for teams shipping outside one language.

Guides
The Console wizard is short. What stalls people is picking the wrong account type or paying with a card Google Payments declines.…

Guides
Use the same legal name on the ID, the payments profile, and — for organizations — D-U-N-S. A nickname in one field and a passport name in another is a common freeze.…

Guides
Google asks for at least twelve people who opted into the closed track and stayed opted in for fourteen consecutive days. Then you request production from the dashboard. Testers wh…

Guides
Billing is a Console job first. The library in the app only talks after merchant status is accepted.…
It is the login that opens Play Console. With it you create apps, run test tracks, and publish on Google Play. Personal and organization types take different documents.
Google’s Play developer registration is a one-time fee, commonly USD 25, billed through Google Payments. It is not an annual Play fee. Always match the amount on the current Console checkout.
Solo makers usually pick personal. Companies, shared permissions, and many finance or health apps fit organization — and that path typically needs D-U-N-S.
Personal accounts created after 13 November 2023 generally must run a closed test with at least 12 testers opted in for 14 consecutive days, then request production access. Organizations are not on that same personal gate.
Finish the payments profile and merchant details in Console, create one-time products or subscriptions, then call Play Billing Library from the app. A free app can still sell in-app items.
Account type, whether an app is already live, payments-profile country, and a screenshot of the Console screen that stopped. Never send passwords or backup codes.
Personal accounts opened before 13 November 2023 are not on that same production gate. Verification and Play policy still apply. Confirm the create date in Console, not a guess.
No. This desk is Google Play Console. Apple Developer has its own personal and organization path. If you need both, say so on Telegram so the papers stay separate.
No. Dev388 is a Play Console desk. We name the type, the papers, and the screen you are on. Inventory shops are a different product.
Bring your Google account, a card Google Payments accepts, and — for an organization — a D-U-N-S number. We will tell you which path you are on.