Google Play License Testing Setup: Configure Billing Testers

If your app uses Google Play Billing for in-app purchases or subscriptions, you need license testers — Google accounts that can test your billing integration without being charged real money. License testing lets you verify the entire purchase flow: product listing, checkout UI, payment processing, and receipt validation — all with test card numbers instead of real payment methods.

This guide walks you through configuring license testers in your Google Play Console so your testing team (or a service like TesterBee) can verify your billing implementation without real charges during the closed testing period. The setup takes under two minutes.

What is license testing and why do you need it?

License testing is a Google Play Console feature that lets designated Google accounts make test purchases in your app without incurring real charges. When a license tester completes a purchase flow, Google Play processes it exactly like a real transaction — including order IDs, purchase tokens, and receipt data — but does not charge any payment method.

You need license testers configured before your closed testing period begins if your app includes any of the following:

• In-app purchases (consumable or non-consumable products)
• Subscriptions (auto-renewing or prepaid plans)
• One-time unlock or premium feature purchases
• Any Google Play Billing Library integration

Without license testers, users who attempt a test purchase will either be blocked or charged real money — neither of which is acceptable. Adding your test team's Google Group (or [email protected] if you use TesterBee) lets testers fully verify your billing flow.

Step 1: Open Settings from the Play Console dashboard

Go to the Google Play Console home page and click Settings from the left sidebar navigation. This is the same settings area where you manage API access, developer account details, and payment profiles.

Step 2: Navigate to License testing

Once you are in Settings, look at the main panel area (not the left sidebar). Scroll down and click the License testing row from the list of settings options. This opens the license tester management panel where you can add Google Groups or individual Gmail addresses as authorized test purchasers.

Step 3: Add license testers and save

In the License testing panel, follow these steps:

1. Choose Google Groups as the tester type. Google Groups is the recommended method because it lets you manage testers as a group rather than adding individual emails.
2. In the email field, enter your Google Group's email address. (If you are using TesterBee to provide your testers, enter [email protected] here as shown in the screenshot).
3. Keep the License response dropdown set to RESPOND_NORMALLY. This ensures Google Play returns standard purchase responses during testing — exactly what your app expects in production.
4. Click Save changes to apply the configuration.

How to verify your license testing setup

After saving, verify that everything works:

1. Open the License testing page again — you should see your Google Group email (e.g., [email protected]) listed under your license testers.
2. If you want to test it yourself, add your own Gmail address as a license tester (temporarily), install your app from the closed testing track, and attempt a test purchase using a test card. The purchase should complete without any real charge.
3. Check that your app's purchase verification (backend receipt validation) correctly handles the test purchase tokens.

Common issues and fixes