Why check all six together

Most disputes are not one big problem but several small mismatches: you can log in but the recovery email is not yours; the account looks fine but strangers sit in the member list; the app list differs from what you were told. Six-field checks turn these gray areas into explicit fields.

The six fields

FieldWhat to verifyIf misaligned
LoginYou can enter Play Console as agreedReal state cannot be verified
RecoveryRecovery email and phone are not solely theirsThey can recover it back later
Two-stepDevice or backup codes transferred and taken over by youYou cannot control the account alone
StatusVerification progress, policy state and restrictions can be shownRestrictions discovered after takeover
AppsEmpty or full list with package names and statusInherit unexpected apps and risk
MembersExtra members removed, you are owner, permissions alignedOld members still access the account

Every row should be verified by you before payment.

Handover acceptance sheet (each side keeps a copy)
1. Login: new owner signed in on own device [ ]
2. Recovery: recovery email and phone replaced [ ]
3. Two-step: old devices and backup codes removed, new ones generated [ ]
4. Status: account and policy status screenshots archived [ ]
5. Apps: app list and signing setup confirmed in writing [ ]
6. Members: all other users removed or downgraded [ ]
Date: ____  Buyer: ____  Seller: ____

Also useful in this topic cluster:

Login and recovery: the easily missed pair

Being able to log in is not owning the account. What matters is the recovery path: can the recovery email and phone be replaced with yours, and can you take over Google account security settings? If the recovery email stays theirs, they may reclaim the account during a security event or recovery flow.

So make 'replace recovery email and phone' an explicit step and re-login on your own device afterwards to verify. See the recovery and hijack risk notes.

Two-step and members: the last mile

Two-step verification decides who truly controls the account. Confirm the device or backup codes move to you, can be re-bound to a new device and that the old device is disabled afterward. For members, list everyone with permissions, remove the seller and unrelated people and then invite your team.

  1. Confirm your role is owner or the agreed role
  2. List all members and permissions, keep screenshots
  3. Remove the seller and unrelated people
  4. Invite your own admins and enable two-step verification
  5. Re-bind the verification device and invalidate old backup codes

Status and apps: put them in writing

Status covers developer verification, policy warnings and publishing restrictions. Apps require a list with package names, store links, status and signing. Neither can be undone after handover, so confirm in writing before paying.

  • Ask for Console account details and policy-status screenshots with sensitive data hidden
  • Check the app list against reality; pause on any mismatch
  • For accounts with apps, ask who holds the upload key

If something does not align

The rule is simple: pause, write down the difference, ask for a written answer and then continue or walk away. Do not skip checks because the chat has gone on long or the other side says it is fine.

Keep checking during the week after handover; see the first-week guide.

Related reading:

Related

Related desks