For weeks, the PeerPlay tester page has said that Pro testers get paid to PayPal once their balance reaches $5. This week that stopped being a promise. On October 27 and 28, 2026, I sent the first two payouts.
They are small: $5.05 each, $10.10 in total. But they are real money, sent to two real people who opened paid apps on their own phones day after day so that developers could get through Google Play's closed testing requirement. Here is exactly how it went, including the part that didn't work the first time.
The two payouts
The first request was paid on October 27 at 16:22. The tester was testing on a Samsung Galaxy S20+ running Android 12. The whole $5.05 came from testing.
The second was paid on October 28 at 19:35, to a tester on an Infinix phone running Android 14. Their $5.05 included $2.00 from referrals, for developers they referred to PeerPlay. The rest came from testing.
In my admin panel that adds up to two requests, two paid out, nothing pending, and $10.10 in total. I sent both with a short note: "Peerplay payout. Tnx for testing."
How a tester gets to $5
On PeerPlay's paid (VIP) campaigns, a Pro tester earns $0.05 for every day they test an app. Testing means opening the app from PeerPlay and using it for about 30 seconds. If they test on 12 of the 14 campaign days, including day 13 or 14, they also get a $0.30 bonus once day 14 has ended. That is up to $1.00 per app per campaign.
So $5 is not a click-and-collect amount. It means several paid apps tested day after day, often in parallel. That is exactly what the developers paying for those campaigns need: people who are still there on day 14.
How a payout actually happens
There is no automatic payout robot behind this yet. When a tester's balance reaches $5, they request a payout from their profile in the app. The request lands in my admin panel, next to the PayPal email the tester gave when they applied as a Pro tester and the physical device they test on.
I check the request, copy the PayPal address and send the money by hand from my own PayPal account. Then I mark the request as paid. It is slow compared to a fully automated system, but at this stage it means I look at every payout before it goes out, and I would rather catch a mistake than automate one.
It also means I see the same thing the developers paying for campaigns care about: every payout is tied to a real device and a real tester, not to an anonymous account.
The payout that bounced
One of the two payouts didn't go through on the first try. PayPal declined it because the tester's account had reached its receiving limit. Some PayPal accounts can only receive a certain amount until the owner confirms more details. Nothing was wrong with the payout itself. The tester lifted the limit in their PayPal account, and the second attempt went through.
If you are a tester, check this before you request a payout. Open your PayPal account and make sure it can receive money, especially if it is new or you have never been paid into it before. It saves a day of back and forth.
What it cost on my side
I'm in Serbia, so I paid from a card in Serbian dinars. Each $5.05 payout cost me RSD 556 through PayPal's own conversion, and PayPal notes that its rate includes a currency conversion fee. For a tester the amount is the same $5.05. For me, the conversion is a small extra cost on every payout, and I'll take it into account as payouts grow.
Why this matters to developers
When a developer buys a paid campaign, part of that money is supposed to reach the testers. These two payouts are the first proof that it does. The testers were on ordinary phones, a Samsung from a few years ago and a newer Infinix, which is the kind of device mix a closed test should see.
If you want to be one of the next testers paid, install PeerPlay on a real Android phone and apply as a Pro tester in your profile. Applications are reviewed by hand, emulators are not allowed, and only apps with the PRO badge pay. Make sure your PayPal account can receive money, and test every day.
Top comments (0)