Hello OpenAI Community & Staff,
I am a solo developer hoping to get some advice or assistance with an organization verification deadlock.
I attempted the Persona verification using my Taiwanese National ID. Because the ID is in Chinese and my OpenAI account was in English, it triggered an immediate “Identity Mismatch,” and the verification UI is now permanently locked.
I have since updated my account profile to perfectly match the English name on my physical Passport . However, I cannot retry the verification because the system does not allow it.
I submitted a support ticket (Case Number: 07832704), but the responses seem to be automated macros explaining general ID requirements, which unfortunately doesn’t resolve the locked UI.
Could an OpenAI Staff member kindly help escalate this or manually reset the Persona state for my Organization so I can verify with my Passport?
Any help would be greatly appreciated. Thank you so much!
Hi @Chenchaohsun
Welcome to the dev community!
Yeah, I get why this feels like a deadlock.
I checked on this, and it looks like your support case is already actively being worked on by a team member.
They should get back to you as soon as possible with next steps.
~Smith
Hi @OpenAI_Support (Smith),
Thank you so much for checking on this! It is a huge relief to know a human team member is actively working on my case (#07832704).
I wanted to provide one more detail that might help the team: during the failed verification attempt, a $5.00 USD authorization hold was placed on my card (ending in your records). While I understand this is likely a temporary pre-authorization by Stripe, I am mentioning it because it is the only transaction linked to this specific identity check session.
Also, I’d like to report a small system quirk: right after your helpful message, I received another automated email from “Ken” sending a macro stating “retries are not supported.”
Could you please ensure that the automated bot does not prematurely close my ticket while the specialist is working on the manual reset for org-yJ4I4iS7SUeU7hOiaYZhnblo?
I have my Passport ready and will wait for the final confirmation from the team. Thank you again for your incredible support!
Hi @CHENCHAOHSUN
Really appreciate you sharing those extra details.
Just to clarify a couple things:
- The $5 hold you saw is just a temporary authorization from Stripe during the verification attempt. It should automatically drop off and isn’t tied to a successful check.
- And yes, what Ken mentioned is correct right now, verification retries aren’t supported. That’s the current system limitation, and it’s also outlined here: API Verification
I know that’s not ideal, especially since you’ve got your documents ready to go. At the moment, there isn’t a way for support to trigger a manual reset or allow another attempt.
That said, you can absolutely continue using your organization as-is. You’ll still have access to OpenAI’s platform and existing models, and over time, some advanced models may become available more broadly without requiring verification.
~Smith
Hi @OpenAI_Support (Smith),
Thank you so much for taking the time to thoroughly investigate this and for giving me a clear, honest answer. I truly appreciate you stepping in to clarify both the $5 authorization hold and the hard system limitation regarding retries. It is infinitely better to know the technical reality than to be stuck in an automated macro loop!
Regarding the suggestion to continue using the organization as-is: while I understand older models remain accessible, the lack of verification explicitly blocks API calls to specific advanced models . Because access to these specific models is the primary requirement for modern AI development, “using it as-is” unfortunately isn’t a viable workaround. Therefore, I will have to take an alternative route (such as creating a completely new account) to ensure my project isn’t blocked.
As a developer, I would like to offer some constructive feedback regarding this verification workflow. While I don’t have access to the backend logs to confirm the exact root cause, I strongly suspect my failure was triggered by an OCR language mismatch. My local National ID is in Chinese, while my developer account profile is in English, which highly likely caused the third-party system to flag an “Identity Mismatch.”
If a simple language difference (or a minor document error) permanently locks the UI without offering a “retry with a Passport” option—and if even the Support team lacks the tools to reset the state—it effectively bricks an otherwise legitimate organization from accessing modern models.
I know I am not the only one—there are many similar reports across this forum. Implementing a manual review queue, a one-time retry for a different document type, or simply giving the Support team the database access to reset the state would save both developers and your support staff a massive amount of time.
Thank you again, Smith, for your incredible transparency and support. Keep up the great work!
Hi @CHENCHAOHSUN
Really appreciate you taking the time to share such a detailed and thoughtful response.
Completely understand your decision here, given the current limitation around verification and access to specific models, it’s definitely not an ideal situation.
I’ve made sure your feedback is captured and passed along internally, as it highlights a real pain point in the current system.
Thanks again for sharing this so constructively.
~Smith