Day 9: Pro subscriber locked out — chargeback initiated, still willing to resolve (Case 08894351)

ChatGPT
,
1

This is a continuation of my previous posts on this issue (both auto-closed after 24 hours).

Day 9 — still locked out. No resolution. No ETA.

@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.

To be specific about what remains unanswered:

  1. I asked twice for a concrete ETA. Neither request received one.
  2. I asked for confirmation that engineering received the HAR file and request IDs. No confirmation.

Meanwhile, the facts have not changed:

  • The HAR file I provided on May 19 confirms HTTP 500 on POST /api/accounts/mfa/verify with error code get_chatgpt_account_error
  • This is a server-side account record issue that requires engineering intervention
  • No client-side action can resolve it
  • platform.openai.com continues to work with the same credentials

I 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.

I 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.

Case: 08894351
Account ID: 041be4ba-b157-4af9-8493-a5330c645d8e

2

Hi @hmikhail,

Thank you for your patience and for providing detailed information throughout this process. I can confirm that we restored your account access and processed a one-month subscription refund as compensation for the disruption.

We sincerely apologize for how long this took and for the frustration and inconvenience it caused.

As the issue has now been resolved, I’ll go ahead and close this thread.

~ Smith