How to turn off OpenAI auto-recharge (and why you should)
Last verified
Where: platform.openai.com → Billing → Payment settings. Disable automatic recharge.
Two minutes, and it is the highest-value billing change most people can make.
Why it matters more than the spend limit
A prepaid balance is a natural cap. When it hits zero, traffic stops and you lose at most what was in it. That's a bounded failure, and it's a good property.
Auto-recharge removes it. When the balance drains, your card is charged and traffic continues. Drain it again, charged again. The system that was supposed to stop at a number instead cycles.
This is why the "unexpected charges" question so often turns out to be several charges rather than one large one — see unexpected OpenAI charges: how to find the cause.
In the two scenarios that actually cost people money — a runaway loop and a leaked key — auto-recharge is the difference between "I lost the $40 that was in the account" and "I lost whatever my card would tolerate overnight."
Turning it off
- platform.openai.com
- Billing → Payment settings
- Disable automatic recharge
- While you're there: set a hard spend limit, and remove any payment method you don't need on file
What changes
When your balance runs out, API requests fail with an insufficient-quota error until you add credit manually.
That is an outage. It is also, in every scenario you actually want to be protected from, precisely the correct behaviour.
Living without it
The obvious objection is that manual top-ups mean your service can go down while you're asleep. That's fair. Manage it like this:
- Keep a comfortable buffer. Enough for 2–4 weeks of normal usage, so a top-up is never urgent.
- Set alerts well below zero. A 50% alert on your spend limit gives you days of warning.
- Check the daily number. If you know what a normal day costs, you know how long your balance lasts, and topping up becomes routine rather than reactive.
- Top up on a schedule, monthly, rather than in response to an alarm.
The pattern is: replace an automatic system that fails badly with a manual one plus enough warning that you never get near the edge.
When leaving it on is defensible
It genuinely is, in some cases:
- Real production revenue depends on uptime, and an outage costs more than the worst plausible overspend.
- You have a low top-up amount — small increments mean each cycle is small, and several charges in a day is itself a loud signal.
- Someone is actually watching daily spend, so a runaway is caught in hours rather than weeks.
If that's you, keep it on and pair it with a hard limit set well below your pain threshold, so there's still a ceiling. The failure mode to avoid is auto-recharge on, no limit, and nobody looking — which is unfortunately the default configuration.
Other providers
Every provider with prepaid credits has some version of this. Anthropic has automatic credit purchase; Google Cloud bills postpaid, which is arguably worse for surprises since there is no balance to run out at all — a Cloud Billing budget alert is the only brake, and by default it notifies rather than stops.
Whichever you use, the question is the same: is there anything in this account that stops on its own? If not, the only cap is a limit you set deliberately.