Disclosure: 12Testers14Day publishes this article and sells Google Play closed-testing help.
If your app costs money, or sells one-time products or subscriptions, a closed test raises a practical question: will your testers be charged? Google's answer depends on the testing track and on whether each tester is a license tester. Getting this wrong can mean testers paying real money, or a 14-day test where nobody ever touches your purchase flow.
The short answer
Based on Google's Play Console Help and Android Developers documentation:
| Situation | Paid app install | In-app purchases and subscriptions |
|---|---|---|
| Internal test | Free for testers | Charged, unless the tester is a license tester |
| Closed or open test | Testers must buy the app | Charged, unless the tester is a license tester |
| License tester on a test track | See the note below | Test payment methods, no real charge |
Google's test setup article says: "Testers must purchase paid apps when participating in open or closed tests. For internal tests, testers can install paid apps for free." It also says internal testers pay for in-app purchases unless you add them to a license testers list.
Google's billing testing guide adds that users "incur actual charges for their test track purchases unless the user is a license tester."
Note on paid apps and license testers: Google's license testing article says your own publishing account can buy your app as a test purchase, and that license testers can buy one-time products and subscriptions without being charged. Before you promise testers a free install of a paid app in a closed test, try it with one license-tester account and check the price shown on the Play Store page.
Why this matters for the 12-tester requirement
If your personal developer account was created after November 13, 2023, Google's testing requirements article says you need a closed test with at least 12 testers opted in continuously for at least 14 days before you can apply for production access. (See our 12-testers requirement explainer for details.)
That has two consequences for monetized apps:
- A paid price is a barrier to opting in. Every closed tester has to buy the app. Fewer people will agree, and anyone who doesn't install can't give you much feedback.
- An untested purchase flow is a launch risk. If testers avoid your paywall because they don't want to spend money, your billing code ships with almost no real-device use.
Option 1: Keep in-app purchases testable with license testers
For a free app with in-app products or subscriptions, add your closed testers as license testers as well.
- In Play Console, go to Settings > License testing.
- Choose testers with an email list (up to 2,000 addresses per list) or a Google Group (no user limit, according to Google).
- Save your changes.
- Make sure the same people can receive your release. Being a license tester doesn't put someone on your closed track. They still need to be in the track's tester list and opt in through the opt-in link. Our guide to inviting testers and fixing access problems covers the common opt-in issues.
- Make sure your one-time products and subscriptions are published. Google says they must be published before they can be tested.
Once that's done, license testers see test payment methods at checkout. Google's billing guide lists several, including:
- Test instrument, always approves, for a successful purchase.
- Test instrument, always declines, for a failed payment.
- Slow test card, approves after a few minutes and Slow test card, declines after a few minutes, for pending purchases.
- A test instrument that simulates a user-initiated chargeback.
Things that behave differently for license testers
Tell testers about these so their reports make sense:
- Subscriptions renew fast. A monthly or weekly test subscription renews about every 5 minutes, and a yearly one about every 30 minutes. Test subscriptions renew at most six times, not counting free trials and introductory periods.
- Unacknowledged purchases are refunded. Google says a license-tester purchase is refunded after 3 minutes if your app doesn't acknowledge it. If testers report that "the purchase disappeared", check your acknowledgement code first.
- Resubscribe and pause are always on. Google says these features are always enabled for license testers even if you've disabled them in Play Console.
Google also recommends testing with some non-license-tester accounts, either occasionally or after large changes, so your app doesn't depend on test-only behavior.
Option 2: Decide what to do about a paid app price
If your app has an up-front price, you have a few choices. Each has trade-offs.
- Ask closed testers to buy it. This matches Google's rules, but expect fewer people to agree, and be clear with them about the cost before they opt in.
- Use internal testing for early paid-app checks. Internal testers install paid apps free, but an internal test doesn't count toward the 12-tester closed-testing requirement. Google also says people who opt in to internal testing aren't eligible for your closed test, even if they're on its tester list. Our internal vs closed testing guide compares the two.
- Think hard before making a paid app free. Google's pricing article says you can change an app from paid to free, but "once your app has been offered for free, the app can't be changed to paid." To charge again you would need a new app with a new package name. Moving to a free app with an in-app purchase or subscription is a separate product decision, not a testing shortcut.
A pre-test checklist for monetized apps
- [ ] Decide whether testers should make purchases, and write it in your tester instructions.
- [ ] Add every closed tester to License testing if you want purchases tested without real charges.
- [ ] Publish the one-time products and subscriptions you want tested.
- [ ] Confirm each tester is on the closed track's tester list and has opted in.
- [ ] Check that your app acknowledges purchases, so test purchases aren't refunded after 3 minutes.
- [ ] Give testers specific purchase journeys, such as "buy the monthly plan, cancel, then restore purchases".
- [ ] Run at least one check with a non-license-tester account before production.
Our free closed-testing checklist covers the rest of the setup.
FAQ
Do closed testers pay for in-app purchases?
Yes, unless they're license testers. Google says users are charged for test-track purchases unless they're license testers.
Do license testers count toward the 12 testers?
License testing and the closed-test tester list are separate settings. Google's requirement counts testers who are opted in to your closed test. A license tester who isn't on the track and opted in doesn't count.
Can testers use promo codes instead?
This article doesn't cover promo codes. Check Play Console Help for the current rules before relying on them.
Does a paid-app closed test affect production access?
Google decides production access based on your testing, your app and your answers. The price alone isn't something this article can predict. What helps is a test where testers actually use the app, including the paid features. See what tester activity looks like.
If you'd rather not recruit testers yourself
12Testers14Day provides Google Play closed-testing help: about 14 testers for about 16 days, as a buffer around Google's 12-tester, 14-day requirement. Packages are one-time ($15 Basic for one app, $29 Premium for two, per the pricing page on October 18, 2026). If your app is paid or you want testers to make test purchases, contact the team before you buy so they can confirm what's possible. You can also read how a testing run works.
Official references: Set up an open, closed, or internal test · Test in-app billing with application licensing · Test your Google Play Billing Library integration · Set up your app's prices · App testing requirements for new personal developer accounts
Top comments (0)