Credits and approvals
Earn credits
Every new member receives 150 welcome credits when the account is opened. Simply registering for a campaign does not count as a completed test and earns no additional credits.
Each screenshot and comment submitted during one of the three open periods earns 10 credits, for up to 30 credits. Final feedback earns 10 credits after fourteen full days and all three proofs. A confirmed issue adds a one-time 10-credit bonus for the whole program. The standard total is 40 credits, with a maximum of 50 credits.
Tests started under the previous program keep their five periods and original rates (60 standard credits, up to 70).
Use credits
Publishing an application is free and reserves no credits. The requested tester count is a recruitment goal; it does not prove remaining capacity or official Google Play enrollment.
Funding, when offered, requires a separate developer action: 50 credits per new place are reserved for rewards and the possible bonus. Rewards are paid from this reserve. Closing recruitment returns unallocated funds; already funded participations keep their budgets. Remaining participation funds are returned under the closure rules.
Without explicit funding, rewards are granted by the platform and are not charged to the developer. There is no automatic one-credit charge per test or general pause at a zero balance. Credits cannot be withdrawn as money.
Action scale
| Action | Effect |
|---|---|
| Create an account | +150 welcome credits |
| Join a mission | 0 credits |
| Submit a screenshot and comment during an open period | +10 credits for the tester |
| Complete all three periods | up to +30 credits for the tester |
| Submit the complete final comment | +10 credits for the tester |
| Have a bug confirmed by the application owner | +10 additional credits for the tester |
| Publish a campaign | 0 credits |
| Explicitly fund a new place, if available | 50 credits reserved from the developer |
| Pay a funded reward | Transfer from the reserve to the tester |
Example
A developer with 150 credits publishes an application for free. Funding two places at 50 credits leaves 50 available and 100 reserved. Each tester can earn 40 credits for a complete program, plus 10 for a confirmed issue. A funded campaign with 12 places would require 600 credits; the 150 welcome credits would not cover it.
For 15 testers, reserve 15 × 50 = 750 credits. If you have no funding entitlement yet, complete 19 tests of other members’ apps: 19 × 40 = 760 credits of entitlement. The 150 welcome credits count toward your wallet balance but do not replace those tests. A confirmed bug bonus increases your balance, not your funding entitlement. Reserved funds that are not paid out are returned under the closure rules.
Participation states
| State | Meaning |
|---|---|
| Proof saved | The server accepted a period's proof and comment; its reward is paid once. |
| Final feedback available | Fourteen full days have passed and all three proofs exist. |
| Final feedback submitted | The feedback is saved with its 10-credit reward; general owner approval is not required. |
| Issue confirmed | The owner, or an administrator in an eligible dispute, confirms the one-time bonus. |
A missed period currently prevents final feedback. Rewards already earned remain earned. Financial disputes concern reserved budgets and do not automatically review all feedback.