Rejection due to name mismatch despite full profile and billing information matching student ID

[LEKHANHDAT0412]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

I am having trouble getting verified for the GitHub Student Developer Pack for 15 times and would appreciate some help or manual review from the team.

My application keeps getting rejected instantly with the following reasons:

• Please ensure that your academic affiliation document contains your last name exactly as it appears in your GitHub billing information.

• Please ensure that your academic affiliation document contains your first name exactly as it appears in your GitHub billing information.

• You are unlikely to be verified until you have completed your GitHub user profile with your full name exactly as it appears in your academic affiliation document.

However, I have double-checked and verified that all my details are completely filled out and fully aligned:

• GitHub Public Profile: My name is set to my legal full name matching my student ID card.

• Billing Information: First and Last names are correctly separated and match my ID without duplicates or nicknames.

• School Email: I am applying using my official institutional email address issued by my university.

• Document: I captured a clear photo of my physical student ID directly via camera showing my full legal name, student ID number, university name, and enrollment period.

• Session Reset: I have logged out, cleared cache, and logged back in before reapplying, but the automated system still triggers the same instant rejection.

I suspect the automated OCR may be failing to accurately match the Vietnamese diacritics/characters on my card with the profile fields. Could an admin or staff member please take a look at my application?

Thank you for your support!

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