{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib7dnf2ik4izotvx2fcxofqcua72wytzkkon6xaz23nepplqcldlm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mntueztcp7v2"
  },
  "path": "/t/feature-request-support-mainland-china-86-phone-numbers-for-account-verification-and-binding/1383120#post_1",
  "publishedAt": "2026-06-09T07:52:46.000Z",
  "site": "https://community.openai.com",
  "textContent": "Dear OpenAI Team,\n\nI am writing to formally request that OpenAI extend its phone number verification and account binding support to include Mainland China numbers with the +86 country code.\n\nCurrently, users holding +86 phone numbers are unable to complete certain account verification steps or bind their phone numbers to their OpenAI accounts. This affects a significant population of legitimate users — including developers, researchers, students, enterprise customers, and API subscribers — who rely on OpenAI’s products professionally and academically. The inability to bind a phone number not only hinders the account security experience, but also creates a tangible gap in product accessibility for a large and technically active community.\n\nI fully acknowledge that OpenAI operates under complex regional compliance requirements, legal constraints, and risk management considerations. These are legitimate concerns that deserve careful handling. However, I would respectfully argue that a blanket exclusion of +86 numbers conflates compliance risk with geographic discrimination, and ends up penalizing responsible users who happen to be located in or associated with Mainland China.\n\nThere are practical, measured approaches that could address both sides of this tension:\n\n• Tiered verification: Introduce additional identity verification layers specifically for +86 registrations, such as email cross-verification, device fingerprinting, or manual review workflows, to mitigate abuse without blocking legitimate users outright.\n\n• Phased rollout: Begin with API users or paid subscribers who have already demonstrated a degree of commitment and accountability, before extending support more broadly.\n\n• Compliance-aware design: Work within applicable legal frameworks to offer partial binding support (e.g., for 2FA or account recovery only) without necessarily implying full regional service expansion.\n\nPhone number binding is not merely a convenience feature — it is a core component of account security, identity trust, and two-factor authentication. Denying users this capability based solely on their phone number’s country code undermines the very security posture OpenAI encourages.\n\nI sincerely hope OpenAI will consider this request thoughtfully, and at minimum provide a clear and transparent explanation of the current limitation and any roadmap considerations for +86 support in the future.\n\nThank you for your time and consideration.",
  "title": "Feature Request: Support Mainland China (+86) Phone Numbers for Account Verification and Binding"
}