Post a test. Verified testers use your product, record the session, and answer your form. Approve what’s useful — unused slots refund automatically.
That’s the marketplace standard. If it isn’t here, you don’t approve it.
Captured in-browser inside QATested, with an external link as a fallback. Watch playback in your dashboard, then export MP4 with your submission data.
Testers answer the questions on your form — rating scales, multiple choice, free text — so you can compare submissions side by side.
CSV, JSON, Markdown, or a ZIP with screenshots and recordings. Your QA data leaves the platform — no API keys required.
Not included as “approved work”: bug-bounty lotteries, star ratings with no recording, or auto-charges for junk submissions.
Before someone earns on QATested, they verify who they are and connect payout rails.
Testers complete identity verification before they can earn. You’re letting real people into staging — not throwaway accounts.
Approved work pays out through Stripe Connect. That keeps payouts audit-friendly and ties earnings to a verified profile.
Tier reflects rating, approval rate, and completed tests. When you set pay per slot, you can gate a test to a minimum tier.
Testers must match the devices and browsers you specify to claim a slot — so feedback matches the environment you care about.
Honest note: we’re early, so the tester pool is still growing. Higher pay per slot and looser device requirements usually fill faster. That tradeoff is yours to set — not hidden behind a sales call.
Every submission hits your dashboard for review. Watch the recording, read the answers, then approve or reject.
Incomplete or off-brief work can be rejected — the slot reopens, and you pay nothing for that submission. Thorough work with hard feedback should be approved; that’s what independent testing is for. We moderate rejects so developers and testers both stay treated fairly.
Full settlement rules: Refund Policy →
Prepaid slots up front. You keep value only for work you approve.
Slots × pay per tester + 20% platform fee. WordPress sandboxes show the per-slot hosting fee before you pay.
You only keep (and fund) completed, approved submissions. Rejections don’t auto-bill you for junk work.
Card payments processed by Stripe. Refunds for unused slots go back to the original payment method.
Details on unused slots, WordPress hosting, and timing: Refund Policy
Share only what a claimed tester needs for that test — not a forever open door.
Attach username, password, and login steps when you create a test. Claimed testers get one-tap copy-and-open — no password paste in email threads.
Plugin tests provision an isolated site per claimed slot. Sandboxes are destroyed when the test settles. WordPress testing →
Testers see what you attach for that test. When the window ends, unused access doesn’t keep accruing charges for empty slots.
Legal layer: Privacy · Terms · Tester agreement
| QATested | Enterprise QA platforms | |
|---|---|---|
| How you buy | Self-serve Stripe checkout — no sales call | Procurement, demos, custom contracts |
| What you get | Your form + in-browser recordings + export | Often account-managed reports and bug flows |
| Who holds quality | You approve thorough work; poor quality can be rejected (moderated) | Varies — less “per slot” control |
| Unused capacity | Automatic refunds for unused slots | Often pre-committed volume |
Automated scans and AI audits can surface candidates. Humans with recordings verify what matters before you ship. Developer overview →
Five minutes to set up. Evidence before your next deploy. No sales call, no minimum spend.