Incorrect birthday verified when verifying ID

Reproduction Steps
I verified my age like normal, didn’t do anything special and my ID has my correct birthday clearly visible on it.

Steps:

  • Verify your age
  • Go through the verification steps successfully
  • Check birthdate

Expected Behavior
My age to be correctly verified.

Actual Behavior
After verifying my age, roblox set my birthday at 01/31/2001, my actual date of birth is 10/09/2001 which is clearly stated on the ID used to verify my age.

I’m also unable to go through and reverify as I get a warning when I go to correct my birthdate that I won’t be allowed to verify again if I make any changes.

This isn’t a huge deal, but I feel if we’re presenting government ID the correct date should at least be shown.

Issue Area: Roblox Website
Page URL: Roblox
Impact: Low
Frequency: Very Rarely
A private message is associated with this bug report

4 Likes

Out of curiosity, was the birthdate on your account before verifying set to the incorrect day and/or have you had the incorrect day set for it in the past? I’ve always wondered if the verification system communicates to Roblox what the birthdate on the ID is or not (instead being “does the birthdate on the ID meet a set of criteria” to have even more privacy)

I’d say “maybe it interpreted the date wrong” however I have no idea how it can get 01/31 from 10/09, so I’d maybe rule that out.

Thanks @cinderwth! We’ve followed up internally & this should be fixed for you soon. Please let us know by end of week if you’re still stuck, thanks!

3 Likes

Why can’t you just change it to the correct birthdate in the settings???

I believe it was set correctly, but truthfully I am not positive, regardless you’d assume it’d automatically update it to whatever was shown on the ID. Especially since it doesn’t let you correct or modify anything without being unable to verify again.

Presumably since verifying would verify as that specific age, and changing the date would mean it’s not verified to be the actual age.

Update: It’s now fixed and everything is appearing correct. Thanks

1 Like