{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreia3phzh3cm37na3z7a5vibzmkm2hwqdmy34rva6ufba5dfappx774",
"uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mk7ghyz7dq22"
},
"path": "/t/requesting-staff-assistance-verification-locked-due-to-ocr-language-mismatch-case-07832704/1379490#post_5",
"publishedAt": "2026-04-24T01:03:45.000Z",
"site": "https://community.openai.com",
"tags": [
"@OpenAI_Support"
],
"textContent": "Hi @OpenAI_Support (Smith),\n\nThank 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!\n\nRegarding 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.\n\nAs 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.”\n\nIf 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.\n\nI 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.\n\nThank you again, Smith, for your incredible transparency and support. Keep up the great work!",
"title": "Requesting Staff Assistance: Verification locked due to OCR language mismatch (Case #07832704)"
}