How to take back free credits after an abuse wave
How to claw back free credits after an abuse wave: what you can still save, rollback rules, what to tell customers, and which basic fixes won't hold.
If you're trying to take back free credits after an abuse wave, some of them are already gone. Go back to late Sunday night, when you're on slide 4 of the deck for Monday morning's investor call. Slide 4 is the good one: new accounts this week. It read 392 five minutes ago, so you refresh, see 412, change the figure and feel good for the first time all weekend. You close the laptop at 12:10.
Those last 20 accounts came from a script. Follow this scenario with your own numbers in mind. Say every new account gets 300 free credits and a credit costs you $0.015 in model usage, so a used-up grant costs $4.50. Since 11:47 p.m., something has been creating 4 accounts a minute and spending each grant the moment it lands.
You're asleep, so nobody knows, and not knowing costs 4 × $4.50, or $18 a minute. You'd used $3,698 of your $8,000 monthly limit at your model provider, which leaves $4,302, and $4,302 ÷ $18 is 239 minutes. At 3:46 a.m. the limit is reached and every AI request in your product starts failing, for everyone.
Your alarm goes off at 7:05 with 14 messages waiting. Customers in Europe have been at work for hours, and the latest message reads: "Still nothing working here. Should we be looking at other options?" The people who pay you have been getting errors for 3 hours and 19 minutes. You open the admin panel in bed and do the sums.
11:47 p.m. to 7:05 a.m. = 438 minutes
Accounts created: 438 x 4 = 1,752
Spent everything: 239 x 4 = 956 accounts
956 x $4.50 = $4,302 already gone
Still holding credits: 1,752 - 956 = 796 accounts
796 x $4.50 = $3,582 not spent yetSay 120 customers pay you $49 a month, so $5,880 comes in each month. One night took 73% of that. If 12 of them ask for this month back, that's another $588, or $4,890 in total. At a burn of $15,500 a month, you've lost about nine and a half days of runway since you closed the laptop. Slide 4 still says 412. The dashboard now says 2,144.
Then there's the decision. Raise the limit and your paying customers come back, but so do those 796 accounts, still trying to spend $3,582. Leave it and the people who pay you stay locked out. And the script is adding $18 of new credits every minute you spend deciding.
So you search for how to claw back free credits, and the answer comes in two halves. Credits that were spent are gone, because you've already been charged for them. Credits that weren't spent can still be saved, if you reach them before the script does.
Those figures are a scenario. This next one happened:
From our early beta
A team in our early beta woke up to a $6,000 OpenAI bill. Someone had created hundreds of free accounts and used up the complimentary AI credits on every one of them.
Why you can't claw back credits that were already spent
A free credit is a row in your database until someone uses it. After that it's a line on your provider's invoice, and editing the row doesn't touch the invoice. Plan as if your provider won't refund it, because the requests ran on your account.
The fix that comes to mind at 7:11 a.m. is one UPDATE that sets every overnight balance to zero. Here, 956 of those accounts are already at zero, so it saves nothing there. It also empties the balance of any real person who signed up overnight, keeps no record of what each balance was, and does nothing about the new accounts arriving behind it. You want something a few minutes slower that you can undo.
How to claw back free credits, step by step
Everything before day 8 in this rollback can be reversed.
Minutes 0 to 5: stop new grants. Flip the flag that hands out credits, and keep signup open. If the wave is still climbing, the first-hour runbook covers the rest.
Minutes 5 to 15: freeze what's left. A frozen balance stays on the account but can't be spent. Pin down the start and end of the wave, then count before you change anything:
select count(*), sum(remaining_signup_credits)
from accounts
where created_at between :wave_start and :wave_end
and first_paid_at is null
and remaining_signup_credits > 0;Here that returns 796 accounts and 238,800 credits. If your count looks wrong, stop and find out why.
Minutes 15 to 20: raise the limit, then test it. Set it no higher than paying customers need today. The limit that took your product down was also holding back that $3,582, which is why this step comes third. Then sign in to a paid account and test it.
Hours 1 to 4: sort the accounts and tell people. Use the decision tree and the messages below.
Days 1 to 7: restore real people. Anyone who writes in gets their credits back the same day. Being wrong costs you $4.50 at most. Losing someone who'd have paid $49 a month costs $588 in the first year.
Day 8: reverse the rest, under these rules.
- Add a reversing entry, never overwrite a balance. Give it a batch ID and a reason, so one query can undo the batch.
- Take only unspent free credits. Purchased credits and anything support granted stay put.
- Stop at zero. Don't push a free account negative to recover what it spent.
- Read your terms first. If they aren't clear about changing free credits, ask your lawyer.
You handed out $7,884 of credits that night (1,752 × $4.50). The rollback saves up to $3,582. The other $4,302, or 55%, is a loss.
Which accounts should lose their free credits
You won't prove who's fake before your investor call, and a freeze means you don't have to. Sort on plain facts and let the appeal catch your mistakes.
What to tell customers when you take credits back
Most frozen addresses will never read your message, so write it for the few real people who will.
To accounts you froze
We've paused the free credits on your account after a wave of automated signups on Sunday night. If you signed up yourself, sorry about this. Reply within 7 days and we'll turn them back on.
Paying customers get the facts before they have to ask again.
To paying customers
From 3:46 to 7:25 this morning, AI features failed for everyone. A wave of fake accounts used up our model capacity. It's fixed, and your credits weren't touched. Reply here if this cost you work.
As for slide 4, change it back: "392 new accounts this week. Overnight, fake signups cost us $4,302 and took AI features down for 3 hours and 39 minutes. Here's what we changed."
The fixes you'll ship next, and how they break
By Monday afternoon you'll reach for this list. Each item catches something real, and none of them lasts on its own.
| Fix | Catches | Misses | Wrongly blocks | Upkeep |
|---|---|---|---|---|
| Email verification | Dead addresses | Any inbox a script can open | People whose code lands in spam | Deliverability work |
| Unique emails | The same address twice | Every new address | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | Next week's domains | Privacy forwarding users | A list, forever |
| CAPTCHA | Simple scripts | Better automation | Screen reader users | Fees, lost signups |
| Phone or card required | Casual second accounts | Anyone with another one | Students, people without a stable number | Text charges, fewer signups |
| One signup per IP | Repeats on one connection | Any other network | Offices, campuses, households | Exceptions and tickets |
| VPN blocks | Listed VPN ranges | Anything unlisted | Staff on company VPNs | Another list |
| Rate limits | Bursts from one source | 4 accounts a minute | Busy offices | Tuning per route |
| Usage caps | One account overrunning | Each new account's fresh cap | Anyone at the cap | Choosing when you stop |
| Smaller grants, shorter trials | Some cost per account | More accounts make it up | Every honest user | Fewer people reach paying |
| Manual review | What a person can spot | Anything at 3 a.m. | Whoever looks odd | 14.6 hours here, at 30 seconds an account |
Gmail ignores dots in a personal address, and mail to name+anything@gmail.com reaches name@gmail.com, so one inbox has endless spellings and each looks new to a unique-email rule.
Two changes do shrink the next rollback:
- Put free usage on its own hard cap, apart from paid. A $500 daily cap stops this night around 12:15 a.m. ($500 ÷ $18 is about 28 minutes), with paying customers still running. Real free users get nothing until it resets.
- Release credits in slices, say 50 an hour instead of 300 at once. You can only claw back what hasn't been spent. Some real new users will leave at the wait.
Neither tells you whether this account should have had the credits at all.
Make the decision before the credits go out
You don't have to build your own abuse prevention system, or rerun this rollback after every wave. AbuseZero makes that call while the credits are still yours: one API call from your server, a clear allow or deny, under rules you control. A single check looks at one thing. AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. There's also a proprietary algorithm, with AI that checks the claim again. Your domain list goes stale, and AbuseZero checks mailbox aliases, disposable domains and mail routing. An IP rule stops at one address, and AbuseZero sees beyond it with VPN, hosting, network reputation, Tor and proxy intelligence. A CAPTCHA can't tell a useful assistant from a script, and AbuseZero blocks spammy bots, browser automation and malicious scripts while allowing genuine AI agents and assistants. Creating a fresh account isn't enough to erase previous activity.
Observe mode shows you what would be denied before anyone is blocked, and the quickstart protects your first benefit. When you do take credits back, you can report the reversal, and that claim still counts as received.
Frequently asked questions
Can I claw back free credits that were already spent?
No. Once a credit is used, you've paid for the work it bought. Clawing back only saves credits still in a balance.
Should I delete the fake accounts?
Not during the rollback. Keep them until your appeal window closes, so you can undo a mistake.
How do I keep the next wave away from my credits?
Cap free usage and evaluate each claim before you grant it. An AbuseZero evaluation returns allow or deny before any credits move. See how to protect signup credits in an AI app.
Keep the next wave out of your investor update
Start with Builder
Pay as you go. Evaluate your first claim today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High-volume credits and custom terms.