Struggling with Document Verification - Need Advice

[Danielkombou]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Evidence and Image Capture

Hi everyone,

Hi everyone,

I've been trying to get verified for the GitHub Student Developer Pack for a while now, but I keep getting rejected, and I'm not sure what else to do. I'm hoping someone here can point me in the right direction.

Here's my situation:

I'm a student at University of the People (online, US-accredited).
My name is Daniel Kombou – this matches exactly on my GitHub billing, profile, and all academic documents.
I've submitted multiple documents so far: payment receipts, transcripts, course registration screenshots, and enrollment pages.

The problem:
Every time I submit, I get a rejection mentioning one or more of these:
Document doesn't show my full name (even though it does)
Document doesn't show the school name in text
Document doesn't have a current date showing enrollment
The image is unclear or unreadable

Latest attempt:
I submitted a screenshot of my UoPeople "MY COURSES" page showing:

My full name ✅
Current date (July 4, 2026) ✅
Two courses registered for June 2026: "Registered" status ✅
The URL bar showing uopeople.edu
But it was still rejected because the image was "unable to be read" and the school name wasn't visible in text.

My questions:

Has anyone from University of the People successfully gotten verified? What document worked?
How strict is the "current enrollment" requirement? Does showing "Registered" for the current term count?
Any tips on getting a clearer image accepted – especially for online-only students who don't have physical documents?

I'd appreciate any advice or experience you can share.

Thanks in advance!
Daniel Kombou

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