GitHub Education application rejected due to Indian name initial

[Sabi0603]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Other

Body

Hello GitHub Education Community,

I am a student from India applying for GitHub Education.

My academic document shows my name as "SABARI M". My GitHub profile name is also "Sabari M".

My application was rejected because GitHub requires my billing information to match my academic document exactly. I entered:

First name: Sabari
Last name: M

However, GitHub's billing form rejects "M" with the error "Last name is too short".

I do not want to add my father's name or an incorrect surname because it would not match my academic document.

GitHub also instructed me to use my device camera for the academic document, which I will do when I reapply.

What is the correct way to enter an Indian name where the last name is represented by a single initial?

Thank you.

[Zynx095]

Hey @Sabi0603 ,
If your academic document officially shows your name as "SABARI M", I would not add your father's name or invent a surname just to satisfy the form.

Since the billing form is rejecting the single-letter last name, this looks like a limitation of the form rather than a mismatch in your academic identity.

I would try entering your name exactly as it appears on your academic document first. If the form still rejects "M" as too short, I would contact GitHub Education Support and explain that your legal/academic name genuinely uses an initial as the surname.

When you reapply, also make sure the document clearly shows your current student status and at least one relevant date. GitHub's documentation specifically recommends clear academic documentation when reapplying after a failed verification.

I would avoid entering a different surname just to get past the validation, because that could create another mismatch during verification.

Hope this helps.

[Sabi0603]

Thank you for your advice.

I did try entering my name exactly as it appears on my academic document:

First name: Sabari
Last name: M

However, GitHub's billing form rejects "M" with the error "Last name is too short".

I also tried the other combination suggested by GitHub's rejection message, but my application was rejected again.

I don't want to add my father's name or invent a surname because my academic documents officially show my name as "SABARI M".

I have also submitted a post in the GitHub Education Community to ask about the correct way to handle an Indian name where the surname is represented by a single initial.

If you know of any specific workaround or official guidance for this situation, I would really appreciate it.

Thank you!

[Zynx095]

I found a few recent GitHub Community discussions describing the same issue with legitimate one-character surnames/initials.

One recent case involved an Indian student whose documents showed their name as "Bharanidharan K". They reported that they were able to proceed by using their first name in both the first-name and last-name billing fields and removing the initial from their GitHub profile name. However, this is a community-reported workaround, not official GitHub guidance, so I wouldn't treat it as guaranteed.

There are also recent reports of the exact same "Last name is too short" validation issue from users whose legal names genuinely contain a one-character surname.

Since you've already been rejected after trying the documented name combinations, I would avoid adding a fake character, punctuation, or your father's name.

If you decide to try the community-reported workaround, keep your academic document unchanged and make sure you understand that the billing/profile information would no longer exactly reproduce "SABARI M".

The safest route is to report this as a GitHub Education verification/form-validation issue and include:

• Your GitHub username
• The exact name shown on your academic document
• The exact "Last name is too short" error
• A screenshot of the validation error
• Confirmation that your academic document and legal name use a single-letter initial

There are already multiple GitHub Community reports about this exact validation problem, so you're definitely not the only person encountering it.