Valid Kookmin University enrollment document rejected three times with incorrect reasons

[nukktae]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

Hi everyone,

My GitHub Education student application has been rejected three times with the same reasons, even though my official English Certificate of Enrollment contains all the requested information.

The document clearly shows:

• The complete school name, Kookmin University
• My full legal first and last name
• A current issue date
• A statement confirming that I am presently enrolled

My full name also matches my GitHub billing information and public profile. I updated the profile, logged out and back in, printed the certificate, and captured the complete document clearly using my phone’s rear camera. Nevertheless, the application was rejected again for supposedly missing the school name, date, and matching name.

The document is visually clear, but it may use an embedded font or format that the automated verification system cannot recognize correctly. The rejections appear to be automated and provide the same inaccurate reasons each time.

The GitHub Support page states that individual manual reviews are no longer provided. Could a GitHub Education staff member please investigate whether this is a verification-system issue, or advise me on a legitimate escalation path when a valid document repeatedly cannot be recognized?

For privacy reasons, I have not attached the certificate or any personal information to this public discussion.

Thank you for your help.

[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. ⭐