DEV Community: Arun kumar S

Paid Apps and In-App Purchases in a Google Play Closed Test: What Testers Pay

Arun kumar S — Sun, 18 Oct 2026 04:04:17 +0000

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

What Is 12Testers14Day? How It Helps You Get 12 Testers for 14 Days on Google Play

Arun kumar S — Sat, 17 Oct 2026 18:34:30 +0000

Disclosure: 12Testers14Day publishes this article and sells the service it describes.

If your new Play Console account won't let you publish to production until you've run a closed test, you've probably come across "12 testers for 14 days". This article covers what Google requires, why developers get stuck on it, and what 12Testers14Day (shown on the site as "12Testers for 14 Days") does about it. It also covers what the service can't do.

Google Play's closed-testing requirement

According to Google's Play Console Help article App testing requirements for new personal developer accounts, personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Until then, Production and Pre-registration stay disabled in Play Console. Once you meet the criteria, you apply for production access from the Dashboard and answer questions about your testing, your app and whether it's ready for production.

Some details are easy to miss:

Google describes this rule for personal accounts created after that date. Google's article doesn't apply it to organization accounts. Your own Play Console Dashboard shows whether it applies to you.
The count is taken when you apply. At least 12 testers must be opted in at that moment, and they must have stayed opted in for the previous 14 days.
Gaps break the streak. Google says testers who opt out before 14 days don't count, and someone who opts out and later opts back in needs 14 consecutive days.
Meeting the numbers doesn't end the review. Google says it may ask you to keep testing if you had fewer than 12 opted-in testers or if tester engagement was too low.

Why developers get stuck

On paper the rule is simple. In practice, solo developers and small teams tend to run into the same problems:

Finding 12 people with Android phones who will actually install a test build. Many developers don't have 12 willing Android users nearby.
Keeping all of them opted in for 14 days. If even one person leaves early, you can drop below 12 and have to extend the timeline.
Access problems. Common ones are the wrong Google Account, an opt-in link that isn't live yet, or a tester still enrolled in your internal test. Each of these stops someone from counting.
Feedback you can use. The production-access questions ask how you tested and what you learned. Testers who install and never open the app give you little to write about.

What 12Testers14Day does

12Testers14Day offers Google Play closed-testing help for Android developers. You keep your app and your Play Console account. The service organizes the testers and the testing window around Google's requirement.

According to the live site, the service:

Assigns real Android testers. The site says your app runs on real devices used by people, "not automated installs or passive accounts".
Builds in a buffer. Each package assigns about 14 testers for about 16 days, so one dropout or a late start doesn't automatically put you below Google's 12 × 14 minimum.
Shows participation and daily progress. You follow tester participation, access questions, daily progress and feedback from one shared workspace.
Collects structured feedback. Testers follow your instructions, try the journeys you name, and report what they find.
Helps with the production-access questions. The site provides templates and guidance for writing complete answers to Google's questionnaire. You can also try the free production-access questionnaire tool.
Delivers a closeout report. At the end you get an organized record of participation, observations and next steps. The site has an illustrative sample report, which is labeled as a sample, not a customer result.

How it works

The How it works page describes four steps:

Prepare. Choose a plan and submit your app details: the closed-test link, access instructions (including any login details testers need) and the journeys you want tested.
Connect. Follow the setup instructions for your closed test. On the home page, the service says it provides the tester list and setup guidance you need to configure the closed track. Keep the build available and answer any access questions.
Follow along. Use your workspace to track progress and answer questions during the window. If you publish a new build, let the service know.
Review. Read the closeout report, decide what to fix, and then apply for production access yourself in Play Console.

Packages and pricing

These prices are on the live pricing page as of October 17, 2026:

Package	Price (one-time)	Covers	Testers / days
Basic	$15	1 credit = 1 app submission	14 verified testers, 16 calendar days
Premium	$29	2 credits = 2 app submissions	14 verified testers, 16 calendar days per app
Enterprise / Custom	Ask the team	Multiple apps, dedicated coordination, custom workflow	Tailored

You buy packages, not a subscription. Agencies or teams with several apps can contact the team about a custom plan.

What 12Testers14Day doesn't do

It doesn't decide production access. Completing 12 testers for 14 days makes you eligible to apply. Google reviews your account, app, store listing, policy compliance and answers, and makes the decision itself. No testing service can promise approval.
It doesn't fix the app for you. Crashes, broken builds, login walls without test credentials, or policy problems can still cause trouble. Google says production review isn't a troubleshooting step.
It doesn't submit anything for you. You set up the closed track, publish the build and submit the production-access application.

If the service itself fails to deliver the agreed testing window, refunds follow the published service guarantee. That page explains what counts as a delivery failure and lists the exclusions (for example a wrong opt-in link, a closed track that isn't live, broken builds, or a Google rejection by itself).

How testers join your closed test

The service supplies the testers, but it helps to know how joining works. On your closed track's Testers tab, Play Console offers two access methods:

Email list. You add testers' Google Account addresses to a list in Play Console and attach it to the track.
Google Group. You enter a group address (yourgroupname@googlegroups.com). Google says only members can join, and they must join the group before opting in.

With either method, Google's test setup help says a tester counts only if they're in the track's tester configuration and have actively opted in through the opt-in link. Remember these basics as well:

The opt-in link only appears when the app's status is Published.
Testers need a Google Account or Google Workspace account.
Testers in your internal test aren't eligible for the closed test until they leave the internal test.

When a tester is blocked, work through the checks in Invite testers and fix access problems.

FAQ

Do organization accounts need 12 testers for 14 days?
Google's help article describes the requirement for personal accounts created after November 13, 2023. Check your Play Console Dashboard to see what applies to your account.

Does the service guarantee production access?
No. Google alone makes that decision.

Can I find testers myself instead?
Yes. Google recommends personal and professional networks and communities. The site also runs a free, self-managed tester community if you'd rather coordinate the test yourself.

What should I prepare before buying?
You need a closed track with a published build, a working opt-in link, test login details if your app requires sign-in, and a short list of the journeys you want tested. The closed-testing checklist covers these.

Get started

If you'd rather spend the next two weeks on your app than on recruiting testers, review the packages and pricing or read how a testing run works. Then register your app on 12Testers14Day.

Official references: App testing requirements for new personal developer accounts · Set up an open, closed, or internal test