GitHub Education verification repeatedly rejected even though my name matches exactly

[gudlasrikanth97-hash]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

Hi GitHub Education Community,

I’m trying to apply for the GitHub Student Developer Pack, but my application has been rejected multiple times with the same verification issues.

I have checked my name carefully and it is entered using the exact same spelling and capitalization across my GitHub profile, billing information, and academic document. However, GitHub continues to report that my first name/last name does not exactly match.

The rejection messages have also mentioned:

My academic document does not appear to contain the complete school/institution name.
The document does not appear to contain a date demonstrating current academic affiliation.
My first name does not exactly match the GitHub billing information.
My last name does not exactly match the GitHub billing information.
My GitHub profile should contain my full name exactly as shown on my academic document.

I have already reviewed these details and corrected the name/capitalization where necessary.

I was also rejected on August 27, 2026, when GitHub indicated that my account was too recently created. I applied again after that, but my applications on August 31, 2026 were still rejected.

My academic document is an official document, and I can provide a document that clearly shows:

My full legal name
Complete institution/school name
Current academic year/date
Other information proving my current academic affiliation

Could someone please clarify what exactly GitHub Education verification expects in this situation?

Specifically:

Does the institution name need to be written in full on the document, or is the official logo/name abbreviation acceptable?
What type of document is recommended for Indian students if the standard academic document doesn't contain all of these details?
Does the name in GitHub billing information have to match the academic document character-for-character, including spaces and capitalization?
Is there a way to have the application manually reviewed if the automated verification repeatedly fails despite providing valid documentation?
Could the repeated rejection be related to my GitHub account being relatively new?

I’m happy to provide additional documentation if required. I just want to make sure I am submitting the correct information rather than repeatedly applying and receiving the same automated rejection.

Thank you.

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

[KaifSayed]

1. Full Institution Name vs. Abbreviation / Logo

• The full name is required. The automated OCR system matches the text on your document against official school registries.
• Acronyms (e.g., IIT, NIT, DU) or logos alone frequently trigger the error: "academic document does not appear to contain the complete school/institution name."
• Ensure your document clearly prints the complete legal/official college and university name in English text.

2. Best Document Types for Indian Students

• Best Choice: An official Bonafide Certificate issued on official college letterhead within the last 30–60 days, signed and stamped by the Registrar/Principal. It must explicitly state your full name, course, and ongoing academic year (e.g., “Enrolled for the academic year 2026–2027”).
• Second Best: A modern Student ID Card that explicitly shows a valid expiry date or current validity academic year (IDs without visible validity dates are auto-rejected).
• Avoid: Standard fee receipts (marked weak/insufficient evidence) or marks cards lacking current affiliation dates.

3. Name Matching in Billing & Profile (Character-for-Character)

• Yes, exact matching is critical.
• Navigate to Settings → Billing and plans → Billing information (you do not need to add a payment card).
• Ensure the First Name and Last Name in Billing match the Public Profile Name and the document character-for-character.
• Single-name rule: If you do not have a separate surname on your document, enter your name into both the First and Last name fields in Billing Settings.

4. Can You Request a Manual Review?

• Direct manual review cannot be initiated from the application portal, as it runs entirely on an automated verification model.
• If automated review continuously fails despite 100% compliant documents, contact GitHub Education Support via support.github.com/contact (or open a ticket under GitHub Education → Student Developer Pack) explaining that the automated checks are failing despite matching documents.

5. Impact of a New GitHub Account

• Yes, account age and activity matter. If GitHub explicitly flagged that your account was "too recently created", automated anti-abuse filters will temporarily block or heavily scrutinize rapid reapplications.

Best approach:

1. Do not spam reapplications daily; wait at least 7–10 days.
2. Populate your GitHub profile (bio, avatar, location matching your campus city).
3. Commit and push actual code/projects to establish genuine developer activity.
4. Ensure you apply directly over your college network without using a VPN/proxy.

[gudlasrikanth97-hash]

Everything is Done .Even Manual verification also removed any mail id while raising the ticket support