Hello OpenAI Community & Staff,
I am a ChatGPT Pro plan user and I need assistance with my organization identity verification for API access to the latest models.
What happened:
When I attempted the Persona identity verification, I unknowingly photographed my ID as it appeared on a screen rather than taking a photo of the physical ID card itself. I was not aware at the time that this would cause the verification to fail. I have since researched this issue and now understand why the verification was rejected.
Current status:
My organization verification shows “Identity rejected” on the platform settings page (platform openai com/settings/organization/general). There is a “Start” button available, but it says “Unable to verify organization Unfortunately, verification is not available to your organization at this time.”
Current Request:
I would just like a fair shake at applying properly. Thank you for any help you can provide!
Hi @ryanlldridge
Really appreciate you laying this out clearly.
You’re right, submitting a screen capture instead of a photo of the physical ID can cause the verification to fail. And as noted in the Help Center, when a verification attempt is rejected, the org can become ineligible to try again, which is why you’re seeing that “verification not available” message.
It’s a rough outcome, especially since this was just a genuine mistake and not anything intentional. Unfortunately, there isn’t a retry flow available right now once it lands in this state.
~Smith
Thanks for the reply and understand.
So where would that leave me? Should I just create another organization or another account and try again?
I’m a real human with good intentions trying to give you my money! 
Given the current limitation, creating a new organization (or a new account, if needed) would be the only way to retry the verification process at this point.
If you decide to try again, just make sure to use a photo of the physical ID directly (not a screen image), and it should go through more smoothly.
I know it’s not the most convenient workaround, but hopefully the process goes through without issues next time.
~Smith