A Google Play merchant account is a payments profile, and you get one shot at linking it.
A Google Play merchant account is a payments profile in the Google payments center, attached to your Play Console developer account. Google's help page says that to sell paid apps and in-app purchases on Google Play you need to set up a profile in the Google payments center. The same page says the two can be linked only once, and that after they are linked they cannot be unlinked or changed. That is the whole reason this page exists. One form, filled in on a Tuesday afternoon, decides the country you sell from and the bank account you can be paid into. Every figure below was read on Google's own help pages on 21 October 2026. The registration fee and the rest of the bill are in the cost to publish an app.
What follows is what the profile actually is, when Google says you need one, which locations can register as a merchant and which cannot, and what the form asks for. Then the four decisions in this flow that you cannot take back.
Start hereThe short version
One profile, one country, one link you cannot undo.
Two accounts are in play and people mix them up. The Play Console developer account is the one you publish from. The payments profile, in the Google payments center, is the one you are paid through. You can run the first on its own for as long as your app is free. The moment you want money, Google wants the second, and it bolts the two together permanently.
Two numbers decide whether this is even open to you. On Google's supported locations table, read on 21 October 2026, 214 locations were listed and every one of them was marked as supporting developer registration. 163 were marked as supporting merchant registration. So there are 51 places where you can publish an app on Google Play and cannot register to sell one. That gap is the fact to check first, before you pick a company address or open a bank account.
What is a Google Play merchant account?
It is a payments profile, and the older name has not quite died. Google's help page is titled Link a Google Play developer account to your payments profile. It opens by telling you that to sell paid apps and in-app purchases on Google Play you need to set up a profile in the Google payments center. It then says the profile is linked to Play Console automatically once you create it, and that you can manage app sales, view sales reports and receive payments from sales from there. Nowhere in that paragraph is the phrase merchant account. A few lines later, in the steps, it tells you to click Set up a merchant account now. The button kept the old name. Searching for one term and reading a page about the other is the normal experience here.
The two help pages also disagree about where the thing lives, and both were live when we read them on 21 October 2026. The linking page routes you through Download Reports, then Financial, then Set up a merchant account now. The page titled Create a payments profile sends you to the Payments settings page instead, reached from Settings, then Payments profile, and has you click Create payments profile there. That second page links straight out to a live Payments settings address in the current console, which the first one does not. We have not signed in to confirm which route a new account sees, so if one of them gives you no such screen, try the other rather than assuming your account is missing something.
One note on both pages saves people a wasted hour. If you have set up a payments profile or a Merchant Center account at any point before, with the same Google account, it is already linked to Play Console and there is nothing for you to create. Check before you start a second profile, because the link is the part you cannot unwind.
When does Google say you need a payments profile?
When money is involved, and not before. A free app needs a Play Console account and the US$25 one-time registration fee, which Google's Get started with Play Console page says you can pay with MasterCard, Visa, American Express, Discover in the United States only, or Visa Electron outside it. Prepaid cards are not accepted. Nothing in those signup steps mentions a payments profile. Read on 21 October 2026.
The profile turns up as soon as you price something. Google's page Set up your app's prices gives three steps for a paid app and puts the payments profile first, ahead of checking the allowed price range per country and entering the price. The in-app product page and the subscriptions page both open their availability sections with the same sentence: if you are in a supported location for merchant registration, you can use Google Play's billing system. Both then tell you to set up a payments profile. One profile covers paid downloads, one-off purchases and subscriptions, because all three run through the same billing system.
Subscriptions are where the billing system stops being plumbing and starts being product design. Two mechanics are worth reading before you build the paywall rather than after: the subscription free trial rules each store enforces, and what happens to a lapsed payment during the subscription grace period. Both decide how much revenue you keep from a card that fails on a Sunday night.
One sequencing mistake is permanent, and it has nothing to do with the profile itself. Google's pricing page says a paid app can be made free. It then says that once an app has been offered for free, the app cannot be changed to paid, and that charging for it means creating a new app with a new package name. So a free launch with a plan to charge later is not a plan. Decide before the first release, or keep the paid version as its own listing.
Check yours
Do you need a payments profile yet?
Tick what you plan to do. Each answer names the Play Console help page it comes from, read on 21 October 2026.
Nothing ticked. A Play Console account on its own publishes free apps and never asks you for a payments profile.
Which countries can register as a merchant?
Google publishes this as one table, called Supported locations for developer and merchant registration, with a tick or a cross per location. We read every row of it on 21 October 2026. There were 214 locations. All 214 were ticked for Google Play developer registration and not one was crossed, so the developer side of that table currently excludes nobody on it. 163 were ticked for merchant registration. 51 were crossed. The page carries no last updated date of its own, which is why the date above is the date we read it and not a date Google published.
These were the 51 locations marked as not supporting merchant registration on that date. If your business address is one of them, Google says it may not be able to pay you for your sales by any other means, so this is a question to settle before you incorporate anywhere.
Afghanistan, Andorra, Angola, Antarctica, Aruba, Barbados, Bermuda, Bosnia and Herzegovina, British Indian Ocean Territory, British Virgin Islands, Burkina Faso, Cameroon, Cape Verde, Chad, Comoros, Congo (Republic), Djibouti, El Salvador, Ethiopia, Falkland Islands, Faroe Islands, Gabon, Georgia, Gibraltar, Greenland, Iraq, Kosovo, Kyrgyzstan, Liechtenstein, Madagascar, Macau, Monaco, Montenegro, Morocco, Nauru, Nepal, Papua New Guinea, Rwanda, Samoa, San Marino, São Tomé and Príncipe, Senegal, Seychelles, Solomon Islands, South Sudan, Sudan, Tajikistan, Timor-Leste, Tonga, Tuvalu, Vatican City.
The third column of that table is the developer default currency, and the legend says it comes from the location of your payments profile. USD was the default for 100 locations and EUR for 25, with the remainder spread across local currencies. A footnote marked 17 rows and says developers in those countries will be paid in USD or EUR depending on their location. Two of those rows, Latvia and Malta, show USD with the footnote attached rather than the euro you might expect from a eurozone address. One row is inconsistent in Google's own table: Iraq is crossed for merchant registration but still lists USD, where the other 50 crossed rows carry the star that the legend defines as not supporting merchants.
There is a second restriction hidden in the legend, and it is about your buyers rather than you. Google notes that even where your location supports merchant registration, Google Play customers must themselves be in a supported location to purchase apps. Selling from a supported country does not mean every country can buy. If your prices also need to make sense on the other store, Apple runs a different structure for the same job, which the app store pricing tiers page takes apart.
Play Console Help, supported locations for developer and merchant registration, read 21 October 2026
What does the payments profile form ask for?
Business paperwork, mostly, and two fields your customers will read. Google's Create a payments profile page asks for the legal name of your business as you want it to appear on the profile, and warns that this is shown to your customers and on your receipts. Then your legal business address as it appears on official documents. Google says it needs a valid physical address on file and does not allow a PO box. Have the paperwork open before you start, because the page tells you to make sure your business information is available.
Next a primary contact: an authorised representative of your company who Google can contact with questions about the profile, with an email address and a phone number that the page marks as optional. Then the public business information, which you can either enter or match to your public merchant profile. Your business website. The category of products you sell. A customer support email. And the business or product name that will appear on your users' credit card statements, where Google's own tip is to pick something people will recognise so chargebacks stay low. Then you submit.
The payout side has its own rules, set out on the Google payments center page Enter merchant bank account information. The account has to be able to receive an electronic funds transfer or a wire transfer. It has to be in the same country or region where the merchant account is registered. And it has to be denominated in that country's currency for an electronic funds transfer, or in USD for a wire. Merchants based in the European Economic Area are the one documented exception: they may nominate an account reachable by SEPA in any EEA country, and the page tells them to contact support to do it. Bank verification, where it applies, is limited to electronic funds transfer countries.
A small sign of how closely these pages are maintained: the step that points you at Payments settings prints the word Settings as Settins on the live page. Harmless on its own. Worth remembering when a figure on a help page looks a year out of date, because these pages are not freshly proofed and most of them carry no last updated stamp at all.
The four decisions here you cannot take back
Each row is a quotation from the page named in the last column, read on 21 October 2026. The middle column is what Google documents as the way out, where it documents one at all.
| The decision | What the page says | If you need it changed | Which page |
|---|---|---|---|
| Linking Play Console to a payments profile | They can be linked only once. After they are linked, they cannot be unlinked or changed. | Sign up for a new developer account with a new payments profile, pay another registration fee, and transfer the apps across. | Link a Google Play developer account to your payments profile |
| The business location country on the profile | You cannot change your business location country. | Nothing is documented on that page for changing it. The public merchant profile and the payments profile details can be edited later. | Create a payments profile |
| Offering the app for free first | A paid app can be made free. Once an app has been offered for free, it cannot be changed to paid. | Create a new app with a new package name and set a price on that one. | Set up your app's prices |
| The country your bank account sits in | The account must be in the same country or region where the merchant account is registered. | No change is documented. Merchants based in the EEA may nominate an account reachable by SEPA in any EEA country, by contacting support. | Enter merchant bank account information |
Where this lands if a builder generated your app
Nothing about the payments profile changes because an AI wrote the code. The profile belongs to your business, holds your legal name and address, and is linked to a developer account you registered. No tool can fill it in for you and none should offer to, because the legal name on it is the name on your receipts.
Newly is an AI app builder. You describe an app in plain English and it writes a real React Native and Expo project that you own. It uploads iOS builds to TestFlight, publishes to Google Play internal testing and builds a standalone Android APK. It has two-way GitHub sync, so the project is never trapped. It does not submit to the App Store for you, because Apple requires the owner of the content to submit. It is $25 a month, with no free tier.
The practical overlap is the internal testing track. You can get a build onto real phones there and settle what the product is before you ever open the payments form. That ordering is worth keeping. Ship free to internal testing, decide whether this app charges at all, and only then fill in a form whose country you cannot edit afterwards.
Questions people ask about Google Play merchant accounts
It is a payments profile in the Google payments center, linked to your Play Console developer account. Google's help page Link a Google Play developer account to your payments profile says that to sell paid apps and in-app purchases on Google Play you need to set up a profile in the Google payments center, and that once you create one it is linked to Play Console automatically. You then manage app sales, view sales reports and receive payments from sales. The words merchant account survive in Play Console as the label on the button, Set up a merchant account now. Read on 21 October 2026.
Build it first, then decide what it charges
Get the app onto a phone, work out whether anyone will pay for it, and open the payments profile with your company documents on the desk. The country on that form outlives the app.
Start building