Repeated false rejections from Student Developer Pack verification despite valid school documents

[TheArpanAnand]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

I am a Class XII student in India and I have been trying to get the GitHub Student Developer Pack for a while now. The application keeps getting turned down even though I keep uploading what should be proper proof through their academic enrollment proof verification.

Initially, there were genuine issues that needed to be resolved like lack of billing information. However, even after resolving those issues, every re-application for verification keeps getting rejected with the message, "We were unfortunately not able to verify your academic status. Please address the following issues and apply again.", even though there is NO issue listed.

I have already tried:

• School ID card
• Enrollment-related documents
• Multiple lighting conditions
• Multiple live captures
• Different framing and positioning attempts
• Also cleared out cache as suggested in other discussion

Despite this, the system continues producing objectively incorrect rejection reasons.

What makes this genuinely more frustrating is the lack of any meaningful escalation or manual review path at all for legitimate students affected by false automated rejections or without getting redirected ten times, especially for institutions outside standardized Western academic formatting conventions.

I would appreciate clarification regarding:

1. What exact document structures the verification system is actually capable of recognizing
2. Whether international educational documents are being properly supported
3. Whether any non-automated escalation path exists for repeated false rejections

Currently, the process feels less like student verification and more like trying to satisfy an OCR model that rejects valid documents while failing to correctly read clearly visible institutional information.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐