Charged for credits never received

Open 💬 4 comments Opened May 9, 2026 by kyleboggess-lgtm
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

5.5 extra high

What subscription do you have?

Codex business and chatgpt plus

What platform is your computer?

windows

What issue are you seeing?

I ran out of credits in codex. It asked me to purchase more. I did. Then it never updates with my credits. I've logged out and back in. I've restarted the app. I've tried everything on my end. I purchased a product and did not receive it.

What steps can reproduce the bug?

Uploaded thread: e94261f9-fd76-4c9c-a099-2afcae875547

What is the expected behavior?

To have 500 credits

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #21240
  • #21161
  • #20904
  • #21421

Powered by Codex Action

trungnt13 · 3 months ago

thread ID: 019e1a4b-ab7d-73a1-a150-2082adbed92f

Similar issue here, all credits disappeared, also not visible in codex-cli /status

kyleboggess-lgtm · 3 months ago

It took 2 days to update with the original credits I purchased but there
have been no issues since

On Sat, May 16, 2026 at 2:03 PM Solvo @.***> wrote:

SolvoFounder left a comment (openai/codex#21973) <https://github.com/openai/codex/issues/21973#issuecomment-4468113473> you've already done the entire client-side checklist — logout/login, restart, the works — so the problem isn't on your machine, and you shouldn't burn more time on app-side fixes. you paid for 500 credits and got nothing; that's a delivery failure. free first move that fits a business+plus setup specifically: the codex credit flow has a known bug where credits get provisioned to the wrong context — and with a chatgpt business account plus personal plus on the same login, this bites harder, because the credits can land on the business workspace while the codex app is running under your personal context (or vice versa). before contacting anyone: in chatgpt, deliberately switch between your personal account and the business workspace and check the codex usage panel (chatgpt.com/codex/settings/usage) in each — the 500 credits may already be there, just attached to the side you're not running codex from. if you find them on the wrong side, switching the codex app's workspace/account context often surfaces them. if they're nowhere, go to help.openai.com logged into the exact account/workspace that was charged, open the chat widget, and frame it as a delivery failure, not a refund: "paid for 500 credits, never provisioned to either my personal or business context, thread e94261f9-..." — paid-and-undelivered plus a documented misprovision bug escalates past the standard non-refundable-credits wall, which a plain refund ask does not. if the chat widget just loops (common here, especially on business accounts that get routed oddly): i packaged a paid done-for-you escalation kit for this exact archetype — the non-queue routes in, three written-for-you messages (delivery-failure escalation / business-vs-personal context misprovision / chargeback-window preservation), and a day-by-day timeline keyed to your real chargeback deadline. $49 flat, pay only if it actually gets you to a human: https://ai-model-change-radar-west0ngs-projects.vercel.app/rescue the check-both-contexts step is free and is the right first move given your business+plus setup — the kit is only if that and the chat widget both stall. report back if the credits turn up in the other context; it'll help the next business-account person hit the same wall. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/21973#issuecomment-4468113473>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CB5GOCX25NHYMP7SJ52XHMD43DJRVAVCNFSM6AAAAACYXSDV6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINRYGEYTGNBXGM> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: @.***>
jonathan-dean · 1 month ago

I am having this same issue.