Three separate settings, three separate places
What you need to take over lives in three layers. The Google account holds the login email, password, recovery email, recovery phone and 2-step verification. Play Console's Users and permissions page controls who can act on the developer account and in what role. The Google payments profile holds contact details, address, payment method and tax information. They do not affect each other: adding yourself as an admin does not remove the old recovery phone, and replacing the payment method does not secure the login. Before ordering, ask the seller which layers are included in the handover and who controls each one today.
Add your own admin first, then touch anything else
If you receive Google account credentials, sign in to Play Console, invite an email you will keep long term under Users and permissions, grant account-level admin rights, then sign in with that new email and confirm you can open settings, the app list and the user management page. This gives you an access path that does not depend on the delivered credentials. Until it works, do not change the password or remove anyone, or a login challenge could lock you out of both routes. Also read the owner and roles actually shown in the Console rather than relying on a verbal description.
Replace recovery options one at a time and verify removal
If any recovery email, phone number, 2-step method or backup code still points to the seller, they can still reset the account. Replace them one by one, and after each change test sign-in and recovery in a private window or on another device. Check that the recovery email and phone are yours, 2-step verification is bound to your authenticator or device, old backup codes are void and new ones issued, and the signed-in devices and third-party access lists contain nothing you do not recognize. Several security edits in a short window may trigger extra verification; what Google shows at that moment governs.
Payments profile: separate fields you can swap from fields tied to identity
The payment method, billing contact email and notification settings are typically what you replace after taking over. The developer name, account type (individual or organization) and the legal name and address used in verification are tied to the account's identity checks and are not simply editable to your own details; changes generally trigger re-verification, so do not attempt them without knowing the rules. A workable test: if a field answers who pays and who gets notified, change it; if it answers who this developer is, stop and confirm the original verified entity with the seller and the platform's current guidance. If the account has paid apps or in-app purchases, review the merchant and payout settings separately; with no revenue use case, there is no urgency to touch them.
Verify with a checklist, and stop on verification you cannot explain
Check five things: you can sign in to Console independently with admin rights; recovery email and phone are yours and the old ones are gone; 2-step verification and backup codes are reset; the developer contact email receives a test message; the payments profile shows your payment method and notification email. If any item fails, do not continue editing. If the platform asks for documents that do not match the account's verified entity, do not improvise materials or retry repeatedly. Stop and ask the seller for the original registration details. Account status after handover depends on platform policy and review at that time, so the more specifically the handover scope and after-sales boundary are agreed before ordering, the better.
FAQ
Should I change the password immediately after buying?
Not as the first step. Invite your own email in Play Console and confirm admin access first, then replace recovery options one by one, and update the password last. If a verification prompt appears midway, you still have a working access path.
Can I change the developer name and verified details to my own?
These fields are tied to identity verification, and whether they can be changed and what verification is required depends on the platform's current page. Confirm the account type and verified entity fit your use case before ordering, rather than hoping to change them afterward.