Write what you need to do first
A developer account is not a standard product. Personal, organization, fresh, aged, empty or with apps all carry different risks and uses. The most common mistake is asking 'how much' without saying what app, which payout country or whether finance, health or VPN categories are involved — and ending up with a mismatched account.
Write three sentences: app type, target country and whether you need an organization entity. For restricted categories read the finance, health and VPN guide first; for personal publishing read the closed testing guide.
Nine checks
- Entity type: personal or organization, matched to your app category
- Registered country: consistent with payout and tax needs; usually not switchable later
- Create date: personal accounts after 13 Nov 2023 usually still need closed testing
- Apps: empty or with apps; with apps requires a full list and store links
- Permissions: after handover you are owner, not only admin
- Payments profile: can it move to your name
- Recovery: can recovery email and phone be replaced with yours
- Policy history: warnings or takedowns, answered honestly in writing
- Order of events: verify against the written sheet, then pay and hand over
If the other side says 'I would rather not say' on any item, treat it as a signal and pause. Writing the list down gives you a reference if problems appear later.
Also useful in this topic cluster:
What not to send in the first message
- Any password, verification code or recovery code
- ID, passport or bank card photos
- Login screenshots from your current accounts
- Payment before the details are discussed
- Any process that asks you to hand over credentials so someone can 'take a look'
A sensible first message contains only specs: country, type, fresh or aged, empty or with apps, app category. See the guide on why the first message carries no documents.
Inquiry template
Buying a Google Play developer account
Entity: personal / organization
Country:
Fresh / aged:
Empty / with apps:
App type and category:
Preferred handover: owner transfer / other
Organization verification needed: yes / no
A filled template lets the other side quote verifiable conditions instead of 'whatever'. If unsure which entity to choose, read the personal vs organization guide.
Verify on your own device
Verification belongs on your own device and network: you log into the Console and compare account type, create date, app list and user permissions against the written spec. Do not do critical steps in a remote desktop or screen share controlled by the other party.
Only after verification do you move to payment and final handover. Agree on order of payment, cool-off periods and permission steps in advance.
When to walk away
- They refuse to state account type, date and apps in writing
- They promise guaranteed review, never banned or instant takedown
- They demand payment before any detail
- They ask for credentials to your own accounts
- They cannot explain who owns the recovery email and phone
A safe deal is one both sides are willing to write down. Willingness to put it in writing shows they know the account's state.
Related reading:
Related
Related desks