You have your 12 closed testers opted in. Now someone asks the question that stops a lot of first-time developers cold: "Should I test the payment flow with my own card?"
Do not. Google Play has a built-in answer for exactly this — license testers and test payment methods — and using them is the difference between a clean test of your in-app purchases and a real charge, a real refund request, and a mess in your order history.
A test account is not just a spare Gmail address. It is a Google account you control, added in the right places, that can install your closed-track build, make purchases that are never actually charged, and see exactly what a real tester sees — without touching real user data.
License testers are not the same as closed-track testers
These are two different lists, and mixing them up is the most common mistake.
- Closed-track testers are the people on your Testing > Closed testing track. They opt in with the opt-in link, install the build, and count toward your 12 testers for 14 days. They test the app.
- License testers are Google accounts you list in Play Console's license testing settings. They are the accounts allowed to make test purchases — in-app products and subscriptions — without being charged.
A tester can be on one list and not the other. If a closed-track tester tries to buy something and they are not also a license tester, Google Play treats it as a real purchase and charges their real payment method. If a license tester is not on the closed track, they cannot install the closed build in the first place.
So for any purchase testing, a person needs to be on both lists: closed track for the build, license testing for the payments.
Setting up license testers
Add license testers before anyone tries a purchase, not after the first charge appears.
- Use accounts you control. A license tester should be a Google account you or your team owns — a dedicated test Gmail, not a tester's personal account and never your main developer account. You need to be able to sign in to it, check its order history, and revoke it later.
- Add them in Play Console's license testing settings. Enter the exact Gmail address. Like the closed track, a mistyped address creates a different account that will not work, so copy-paste it.
- Give changes time to propagate. As with the closed track, license tester changes can take a while to reach every device. Add testers a day before you need them, and have them try a purchase only after the setup has had time to settle.
- Keep the list small and current. Remove accounts when testing ends. A license tester list that still contains old test accounts months later is an account that can still make test purchases against your app.
You do not need a separate license tester for every closed tester. You need license testers for the accounts that will actually test purchases — usually one or two accounts you control, used on test devices.
Test payment methods: what actually happens at checkout
When a license tester buys an in-app product in your closed build, Google Play shows test payment instruments instead of real ones. The purchase completes, your app receives the purchase, and no money moves.
- Test cards are labelled as test instruments. At checkout the license tester sees test payment methods — cards that are marked as test and will never charge a real bank account. The tester should pick one of those, not their own saved card.
- A test purchase still goes through your app's real purchase flow. Your app calls the same billing code, receives the same kind of purchase token, and should grant the item or subscription exactly as it would for a real buyer. That is the point: you are testing your code, not a demo mode.
- Test subscriptions renew on a compressed schedule. A test subscription does not run for a full month before renewing. It renews quickly — in minutes — so you can test renewal, expiry, and cancellation without waiting weeks. Do not be surprised when a "monthly" test subscription renews several times in an afternoon; that is expected behaviour for test purchases.
- If a tester sees their real card at checkout, stop. That means the account is not recognised as a license tester on that device, or they are signed in to the Play Store with a different account than the one you added. Do not complete the purchase. Check which account is signed in to the Play Store on that phone, and confirm that exact address is on the license tester list.
Never test a purchase flow by buying your own product with your own real card "just to see if it works." That creates a real order, a real charge, and a refund you have to process — and it tells you nothing a license tester would not have told you for free.
What testers can and cannot see
Test accounts see the app the way a real user would — with a few important limits.
- They see the closed-track build, not your production listing. A tester on the closed track installs the version you published to that track. They do not see production prices, production reviews, or anything from a track they are not on.
- They cannot see your Play Console, your sales reports, or other testers. Testers see only the store listing and the app. They have no access to your developer account, your revenue data, or your tester list. Never share developer-account access with a tester to "help them test" — that is not how testing works, and it is a security risk.
- They can see test prices and test purchase history for their own account. A license tester can check their own test orders in their Google Play order history. Those orders are marked as test purchases. They are not real charges and should not be refunded like real ones.
- They cannot test with real user data. Do not point a test build at your production database, your real users' accounts, or a live backend with real customer data. Test builds should talk to a test environment, with test accounts and test data. If a tester can see a real user's email, order, or personal information inside your app, your test setup is wrong — fix the environment, not the tester.
The rule is simple: a tester should be able to break the app, not your business. Give them a test account, a test build, and test data — and nothing else.
The test-account checklist
Before anyone on your team or your tester list tries a purchase, run through this:
- The test Google account is on the closed testing track, and the tester has opted in and installed the build from the opt-in link.
- The same exact account is on the license tester list in Play Console.
- The tester is signed in to the Play Store on their test phone with that exact account — not a personal account, not a work account.
- At checkout, the tester sees test payment methods, not their real card. If they see a real card, stop and fix the account first.
- The app is pointed at a test backend with test data — no real user accounts, no production database.
- After testing, remove the test account from the license tester list if it is no longer needed, and note which purchases were test purchases so they are never confused with real sales.
Five minutes of setup here saves you from the two worst outcomes in closed testing: a tester charged for a product they were supposed to test for free, and a test purchase that pollutes your real sales data.
Test accounts are part of the test, not an afterthought
Most developers set up the closed track carefully and then treat payments as something to check "later." Later usually means the day before they apply for production access — when a failed purchase flow is the most expensive thing to discover.
Set up one or two license testers the same day you set up the track. Test a purchase early, test a subscription renewal, test a cancellation. When the purchase flow works on a test account, you know it works for real buyers too — without ever charging anyone.
The part no tool does for you
Play Console gives you the track, the license tester list, and the test payment methods. What it does not do is find you 12 real people with Android phones and different Google accounts, get each of them opted in on the right account, keep them installed and engaged for 14 continuous days, and replace the ones who go quiet.
That is exactly what VerifiedTesters handles: 12 real testers on their own Android phones, opted in on your Play Console closed track and engaged for 14 continuous days, with free dropout replacement and a final report built for the production access form.
Set up your test accounts properly. Test the payments for free. Then let your 14 days count.
Top comments (0)