What it is and why it matters
A Google Play payments profile records the entity behind payments and payouts, including legal name, address, tax details and payout method. It determines where app sales, subscriptions and in-app purchase revenue go and who bears tax responsibility, so it is central to account handover and app transfer.
Effect on different transfer routes
| Situation | Payments impact | Advice |
|---|---|---|
| New account without a profile | Minor | You set it up after takeover |
| Set up but not monetized | Entity bound; confirm changeability | Write on sheet; confirm change method |
| Monetized personal | Strongly tied to identity and tax | Owner transfer generally unavailable; evaluate app transfer |
| Organization within same org | Entity usually unchanged | Ensure new owner has payments permissions |
| App transfer | Target needs a working profile | Plan subscription and product continuity |
Rules change; follow the Console transfer wizard and official guidance.
Also useful in this topic cluster:
What to ask before buying
- Is there a profile now and who is the entity
- Must the buyer create or take over a profile after transfer
- Was a merchant payout account linked and has revenue accrued
- For same-org organization transfers, does the new owner have payments admin rights
- Are there pending tax or verification tasks
The seller should answer in writing and it belongs on the sheet. Vague answers, or repeated 'payments later', are risk signals.
What not to do
Do not swap the payments entity to make an account look cleaner and do not borrow someone else's identity or account to collect payouts. It may violate platform terms and tax rules and can freeze funds.
Never send bank cards, ID or tax numbers in chat. Provide data only inside official pages, operated by the person themselves — the same principle as no documents in the first message.
Post-transfer payments check
- Open the payments profile in Console and verify entity, address and status
- Confirm the payout method is yours, not theirs or a third party's
- Confirm no open tax or verification reminders
- For apps with subscriptions or products, check financial reports and settlement settings
- Archive screenshots in handover docs
If the entity is not who you expected, pause related publishing and payout actions and talk to the other side in writing.
Relation to official fees
A payments profile is not the registration fee. The one-time developer registration fee (publicly described as about US$25) is an official public figure and separate from any terms between you and a third party; see the fees guide.
Related reading:
Related
Related desks