Verification and Approval
The manual review process, and the common reasons products are rejected.
Every new product and every new version is tested before customers can buy or download it.
What happens after you upload
- The product is held as pending and added to the verification queue.
- A reviewer issues a test licence on a demo account and runs your EA.
- Does it ask? Your EA must check in with the test key. This proves licensing is compiled in.
- Does it obey? The test key is revoked and the EA restarted. It must stop trading. An EA that checks in but ignores the answer is rejected.
- The product is reviewed against its listing.
- On approval, the version is recorded, the customer download is built with a README, and the product is published.
Common rejection reasons
- Licensing not integrated, or the EA does not stop when revoked.
- Misleading profit or safety claims.
- Fake or unverifiable results.
- Incomplete product information.
- Unstable or crashing behaviour.
- The EA does not match the listing.
You are emailed the reason. Fix it and upload again to resubmit.
Was this guide helpful?
Thank you - that helps us improve these guides.
Need help?
Most questions are answered by the guides above. If yours is not, our team will help.
Open Support Ticket