DeactivatedWorkspaceModal / payments page error, owner locked out of billing (ready to pay)

ChatGPT Support
, , ,
1

I am the owner of a ChatGPT Business workspace (“GK ink”, 14 seats) that was deactivated on 18 June 2026 after a payment for an added seat did not go through (insufficient funds on the card at that time). I now have a valid international card with funds ready, and I want to pay the outstanding balance — but I physically cannot reach the billing page.

The problem is the same billing loop several others here are reporting:

  • Signing in as the workspace owner (including incognito, extensions disabled, cache cleared, different browsers/devices) does NOT open the workspace. I am dropped into my personal account instead.
  • Opening https://chatgpt.com/admin/billing does not load the workspace billing portal — it errors / redirects away.
  • The reactivation flow shows the orange banner “An error occurred on the payments page. Please try again” and crashes (the known DeactivatedWorkspaceModal issue / 402 responses).
  • The only billing I can reach is for my personal account, and the UI only offers to create a NEW workspace — which does not help, since a new workspace starts blank and would not restore the existing “GK ink” data (two years of our team’s chats).

So self-service reactivation is impossible from my side: the balance can only be paid through the workspace, and the workspace is exactly what is blocked. Only OpenAI can break this loop.

I already have an open Support ticket (Case #10221361) and have provided a screen recording of the error, but the case has stalled. I would really appreciate:

  1. a fix for the DeactivatedWorkspaceModal / payments page error so I can pay myself, or
  2. a direct payment link / invoice I can pay without entering the blocked workspace, or
  3. manual reactivation from OpenAI’s side.

If any OpenAI staff or moderator can help escalate this, I’d be very grateful. Happy to complete any ownership verification. This is affecting a 14-person team’s daily work.

Thanks in advance to anyone who can point me in the right direction — and if you’re hitting the same bug, please reply so they can see how many of us are affected.

2

Thanks for flagging this @Bill1

I’ve sent you a message in support ticket #10221361, and we’ll continue the investigation there.

To avoid duplication and keep communication streamlined, I’ll close this thread for now. Any further updates or follow-up will take place through the support ticket.

~ Smith