You can run the required closed test on an app that has in-app purchases or subscriptions, and the rules are the same: at least 12 testers opted in continuously for 14 days. The extra work is practical. Testers need a way to reach your paid features, reviewers need to see them, and if the app itself is paid, Google says closed testers "must purchase paid apps".
This article covers what changes for monetized apps and how to plan around it. Google's billing setup is detailed and changes over time, so check Google's own documentation before you configure products.
What's the same as any closed test
Monetization doesn't change the testing requirement. For personal developer accounts created after November 13, 2023, you need a closed test "with a minimum of 12 testers who have been opted in continuously for at least 14 days" (App testing requirements).
It also doesn't change the application. You'll still apply from the Dashboard with Apply for production, and Google will still ask whether testers used all features.
Paid apps: testers have to buy them
If your app has an upfront price, the testing setup page is clear: closed and open testers "must purchase paid apps", while internal testers install them free (Set up a test).
That creates a real cost for every tester. Options developers use:
- Don't plan to go free now and paid later. Google says that once an app has been offered for free, it can't be changed to paid; charging would need a new app with a new package name (Set a price for your app). If you want a paid app, keep the price and plan how testers will cover it.
- Promo codes. A Product Expert community guide describes using 100% promo codes so testers don't pay. That's a community workaround, not official guidance, so treat it as likely rather than guaranteed.
- Reimburse testers yourself, outside Google Play.
If you plan to use a testing service, ask how it handles paid apps before you order.
In-app purchases and subscriptions: plan how testers reach paid features
A free app with purchases inside is easier, because anyone can install it. The question is what happens when a tester hits the paywall.
Google's application form asks about "tester engagement (whether testers used all features...)". If your core value sits behind a subscription and testers can't get past it, your answers will be thin.
Ways to make paid features testable:
- A free tier that shows the core experience. Testers can use the main features without paying, and you test the purchase screen itself separately.
- A free trial, if your subscription offers one. Testers can explore premium features during the trial, but tell them clearly how to cancel before it renews if a real payment method is involved.
- Test accounts you control. Give testers login credentials for an account that already has premium access on your backend. This is the same pattern you use for reviewers.
Whatever you choose, tell testers in plain words what they can test and what you don't expect them to buy.
License testing is a separate thing
Google Play also has a license testing setup, which is designed for testing purchase flows during development. It's managed separately from your closed track's tester list, and adding someone as a license tester isn't the same as having them opted in to your closed test. Only closed testing opt-ins count toward the 12 testers. We cover the differences in a separate article.
Let reviewers see the paid features
Google lists four policy areas to check before applying for production access, and the first is "app content and features (including monetization)". Another is test credentials: "provide valid, working login credentials in Play Console so reviewers can fully test your app's features."
If premium features are tied to an account, a reviewer account with premium access is the clearest way to show them. Put the details under Policy and programs > App content, in the sign-in details (app access) section, and make sure the account doesn't expire during review. Giving testers and reviewers access explains how to set this up.
Make sure the store listing is honest about what's free and what's paid. Store listing accuracy is one of the areas Google tells you to check.
Countries matter for purchases too
Testers can only get your closed test in countries you've selected for the track. Country availability for testing tracks is "synced with production by default", and you can unsync it under the track's Countries/regions tab. If your testers are in Indonesia, the closed track must include Indonesia.
For monetized apps, also check that your products are actually available to buyers in the testers' countries. A tester who sees an error at checkout gives you feedback about the wrong problem.
What to ask testers to check
For a monetized app, useful feedback includes:
- Is it clear what's free and what's paid?
- Does the paywall appear at a sensible moment, or does it block basic use?
- After premium access is unlocked, do the paid features work?
- Does access survive closing the app, updating it or switching devices?
- Are prices and subscription terms easy to understand?
Collect the answers in one place so you can summarize them in your application. Collecting useful feedback from closed testers has a simple process.
What not to do
- Don't give testers anything in exchange for ratings or reviews. Google prohibits "incentivizing feedback", and testers can't leave public reviews on test versions anyway.
- Don't show reviewers a different app from the one users get. Google states that "techniques to evade app reviews are not allowed."
- Don't assume purchases made by closed testers are free. Unless you've set up a testing method, they may be real charges.
Key takeaways
- The 12-tester, 14-day rule is the same for monetized apps.
- Closed testers must purchase paid apps; plan for that cost.
- Make paid features reachable for testers and reviewers.
- License testing is separate and doesn't count toward the 12 testers.
- Include Indonesia on the closed track if your testers are there.
Our production access guide shows how to describe tester engagement in the form. If your app is free with in-app purchases, GoPlayTester can supply 12+ real testers for the 14 days; for paid apps, ask us first. Google makes the final decision on every application.
