{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib7s4ejvn5kagkkipxk5pmh6gmkrqnag6mnduavlaacsapgjh5j2e",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmjgk6pc4mf2"
  },
  "path": "/t/day-9-pro-subscriber-locked-out-chargeback-initiated-still-willing-to-resolve-case-08894351/1381635#post_1",
  "publishedAt": "2026-05-23T11:45:51.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@OpenAI_Support",
    "platform.openai.com"
  ],
  "textContent": "This is a continuation of my previous posts on this issue (both auto-closed after 24 hours).\n\n**Day 9 — still locked out. No resolution. No ETA.**\n\n@OpenAI_Support Thank you for your reply on the Day 6 post, Smith. You mentioned informing the specialized team to review my case with high priority. However, it has now been 4 days since that reply, and I have received no update from the specialized team — not via email, not via this forum.\n\nTo be specific about what remains unanswered:\n\n  1. I asked twice for a concrete ETA. Neither request received one.\n  2. I asked for confirmation that engineering received the HAR file and request IDs. No confirmation.\n\n\n\nMeanwhile, the facts have not changed:\n\n  * The HAR file I provided on May 19 confirms HTTP 500 on `POST /api/accounts/mfa/verify` with error code `get_chatgpt_account_error`\n  * This is a server-side account record issue that requires engineering intervention\n  * No client-side action can resolve it\n  * platform.openai.com continues to work with the same credentials\n\n\n\nI stated in my May 20 email that I would initiate a chargeback if no resolution or timeline was provided within 24 hours. That deadline passed on May 21. I have now begun the dispute process with my payment provider for the billing period during which service has been unavailable.\n\nI want to be clear: I would prefer to resolve this directly. If the account is restored, I am happy to withdraw the dispute. But 9 days without access to a $200/month service — with 28+ support messages, 5 case numbers, and conclusive server-side evidence provided — is not a reasonable outcome.\n\nCase: 08894351\nAccount ID: 041be4ba-b157-4af9-8493-a5330c645d8e",
  "title": "Day 9: Pro subscriber locked out — chargeback initiated, still willing to resolve (Case 08894351)"
}