Vietnamese student — repeated rejection, name with diacritics matches billing/document exactly

[nguyenngotanhoang]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

I'm a high school student in Vietnam applying for GitHub Education (Student Developer Pack). My application has been automatically rejected more than 10 times over the past few hours, always with the same reason: that my first/last name doesn't match my academic document.

My GitHub billing information and profile name are set to my full legal name with Vietnamese diacritics (e.g. "Nguyễn Ngô Tấn Hoàng"), and this matches exactly what's printed on my academic documents (dated student ID card and a dated transcript/report card from my school, both showing my full name, school name, and a current date). I've tried:

• Re-typing the name in billing to make sure there are no hidden characters or extra spaces
• Splitting first/last name several different ways
• Submitting both a school ID and a dated transcript
• Logging out and back in before each reapplication
• Taking fresh, clear, well-lit photos each time (no glare, no screenshots)

As you can see below, my billing name exactly matches my document (with full Vietnamese diacritics):

Yet the application was rejected again immediately after, with the same name-mismatch reason:

Despite all this, I keep getting rejected with the same name-mismatch message. I suspect the automated verification may have trouble reading/matching Vietnamese diacritics correctly (either in OCR of the document or in the text comparison).

Has anyone else from Vietnam (or with a diacritic-heavy name) run into this and found a combination that actually works? Any guidance would be really appreciated — I understand individual manual reviews aren't available anymore, but I'm hoping someone here has a workaround.

Thanks in advance!

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

[iawaisahmd]

after 10 immediate rejections with the same reason, i'd stop reapplying for now. repeated attempts with different first/last name splits may make troubleshooting harder. since the legal name already matches exactly, this does sound worth reporting specifically as a possible unicode/diacritics matching issue. include one successful-quality document photo, the exact billing name, and the rejection screenshot, and ask whether names containing Vietnamese characters are being normalized correctly during verification.