While it’s true that most testers participate to earn payouts, it’s not always about the payout alone. Sometimes bugs are technically valid but don’t meet the required severity for payment. These bugs should still be acknowledged—not necessarily with payout, but at least through backend review or developer insights.

Having a neutral way to record such valid but non-payout bugs would help avoid discouraging testers and ensure potentially useful findings are not lost. This approach would also prevent unnecessary negative impact on BRAP scores caused by rejecting technically valid reports.

Suggestion:

Implement a system to track and acknowledge valid bugs that do not meet payout severity thresholds. This could include a “neutral” status or tag that does not affect BRAP scores negatively but flags reports for backend or developer review. This would encourage testers to submit useful bugs without fear of penalty and improve overall report quality.