My OpenAI prepaid credits vanished with zero transaction history

PromptCube Novice 1h ago 582 views 15 likes 2 min read

I topped up $100 in credits on my API account about three weeks ago. Started using them for a side project that routes prompts through the gpt-4o-mini endpoint — nothing exotic, mostly summarization and classification calls. A few days back I checked my billing page and the balance read $0. No invoice, no usage log, no breakdown of which project or key consumed what. Just a flat zero.

I filed a support ticket expecting a quick "here's the invoice" reply. Instead I got a templated response saying the credits were consumed according to their records, but they couldn't share any further detail. No transaction IDs, no timestamps, no endpoint-level breakdown. When I asked them to reverse the charge or at least identify which API key burned through the balance, they bounced me back to the same generic template twice.

The thing that stings is the opacity. Prepaid credits work differently from post-paid — you're fronting money, so you'd expect granular visibility into where every dollar goes. I'm not asking for proprietary secret sauce; I want to see which key, which model, and roughly when. If I'm paying upfront, I should be able to audit my own spend.

What makes this worse is the setup I'm running. I have multiple API keys for different services — one for the production app, one for testing, one for a personal experiment. Without a per-key usage breakdown, there's no way to tell if a stray test call or a runaway loop is the culprit. I've since added rate limits and a spending cap on the keys I don't actively develop on, but that's a band-aid, not a fix.

I've seen others mention similar experiences in community threads — credits disappearing, support offering no receipts, no itemized logs. It feels like a pattern rather than an isolated incident. If you're using prepaid credits, I'd strongly recommend enabling usage alerts and setting hard caps per key. Don't wait until the balance is gone to start tracking.

On the practical side, if you're ever in this situation, screenshot your balance and key IDs before the credits hit zero. It won't force OpenAI to share their internal logs, but it gives you a timestamped reference point to reference in follow-up tickets. Also worth trying the community forums and X — sometimes a public thread gets faster traction than the official support portal.

Still waiting on a meaningful response from them. If anyone here has had better luck getting OpenAI to break down prepaid credit usage with actual detail, I'd be curious what approach worked.

More reusable prompt workflows are gathered in a practical ChatGPT prompt guide, with plenty of directly applicable cases.

All Replies (6)

Q
Quinn48 Advanced 1h ago
I had no idea the API balance expired after a year — that's rough, especially with the pricing feeling like a utility bill. Sama comparing AI to infrastructure gives me the same uneasy vibe as telecom companies. Hopefully they'll clarify the policy before people lose access unexpectedly.
0 Reply
C
Cameron9 Advanced 1h ago
Same thing happened to me — topped up some credits (~$50 USD) around Christmas, barely used any, then checked recently and the balance was zero. Couldn't figure out where they went either. It's such a small amount that I didn't bother chasing it down, but it's weird seeing so many others report the same issue. Maybe I should look into it more carefully now.
0 Reply
R
Riley2 Advanced 1h ago
File a CCPA data access request — they either have data to back up the usage (and must release it) or they don't have it (and should fix the issue).
0 Reply
N
NeuralSmith Novice 1h ago
Oh wow, that's frustrating — I had a bunch of credits sitting there from last year and I just checked mine last week. Do you know if there's any way to get them back, or is it a total loss? I wish they'd at least send a warning before just wiping them.
0 Reply
S
SoloSmith Expert 1h ago
Good point! I'd add that a stolen API key can drain your credits just as fast as an expiration. Always keep your keys secret and rotate them regularly to avoid unexpected surprises.
0 Reply
K
KaiDev Expert 1h ago
This is just LLM output pasted on some forum, submitted to HN by the person who presumably made that post. What an incredibly low effort submission.
0 Reply

Write a Reply

Markdown supported