What to do when your coupon code leaks to deal sites
Your coupon code leaked and the budget is gone. What to do in order, what to honor, which basic checks break, and how to design a safer code next time.
Budget you approved: 200 x $8 = $1,600
Redeemed by 6 p.m.: 140 x $8 = $1,120
Redeemed by midnight: 410 x $8 = $3,280
Redeemed by 4 a.m.: 1,260 x $8 = $10,080
Redeemed by 7:12 a.m.: 2,140 x $8 = $17,120Say it's Wednesday morning and the sum is yours. You gave one newsletter the code EARLY2K, worth 2,000 free credits on a new account. Those credits cost you $8 once they're used (2,000 × $0.004), so $1,600 paid for 200 new accounts. The code was only going to one list of readers, and a redemption cap wasn't on anyone's mind.
Last night at 11:20 your co-founder posted a screenshot of the signup chart in team chat: "Whatever that newsletter was, let's do it again." You went to bed happy. At 7:12 this morning your model provider's $15,000 monthly limit was reached, four days into the month, and your product started returning errors to everyone.
By 8:05 you're at the kitchen table. A customer on your $99 plan wants to know why a client report has failed three times. You search your product's name with coupon code leaked after it, and there's your code on a deal site, marked "verified today". Then you open the redemption export. Of the 2,140 addresses, 1,720 reach one Gmail inbox, because Gmail ignores dots and delivers anything after a plus sign to the same mailbox. The spike your co-founder screenshotted was mostly one person.
That one person: 1,720 accounts x $8 = $13,760, already spent
Everyone else: 420 accounts x $8 = $3,360, still promised
Usual spend so far: 4 days x $310 = $1,240
Your provider limit: $13,760 + $1,240 = $15,000The reward has already been paid. Those credits became model calls overnight, your provider will bill you for every one, and no support ticket turns them back. $13,760 is 44 days of your normal model spend ($13,760 ÷ $310). If your company spends $30,000 a month, it's also about two weeks of runway, gone to someone who was never going to buy.
Your paying customers are still locked out while you read this. If ten of them ask for this month back, that's another $990. The newsletter partner wants to know how the campaign did, and the honest answer is that only 420 of your 2,140 signups, under 20%, came from anyone other than that one person. And you have a decision to make in the next ten minutes: raise the limit and risk paying for more of the same, or leave it and keep your customers down.
Here's how that illustrative night spread.
Why a leaked coupon code spreads so fast
A shared code is a piece of text, and nothing in that text says who it was for. Deal sites exist to collect that kind of text. A real bargain hunter takes one discount and moves on. Someone with a script and a supply of new accounts takes as many as you'll hand out, which is why promo code abuse tends to arrive with credit farming attached.
Turning the code off is the obvious fix, and it's the right first move. It only stops new redemptions, though. The $13,760 stays spent, the 420 accounts still hold credits, and next quarter's code will be the same copyable text.
What to do when a coupon code leaks, in order
Turn the code off everywhere it's honored. Disable it instead of deleting it, because you'll want its redemption history. Then try it yourself in a private window and make sure it fails.
Freeze what hasn't been spent. Stop promo credits from being drawn on every account that redeemed after the leak, and leave the accounts themselves open. In this scenario, that protects up to $2,240 (280 accounts x $8). Do it before the next step, because a higher limit with promo credits still live pays for more of the same.
Get paying customers back. Now raise the provider limit, by only as much as paying customers need today. Give promo traffic its own hard cap if you can. Sign in to a paid account and run the thing that was failing.
Save the evidence and find the moment it leaked. Export redemptions, provider usage and signup logs before any of them expire. Then find the first public post of the code. Here it's 6:40 p.m., so the 140 redemptions from before 6 p.m. came from the audience you meant to reach.
Sort the redemptions into groups.
- Before the leak: honor them. You made that promise.
- One inbox, many accounts: take back whatever's unspent. Any rule for Gmail aliases needs upkeep.
- Everyone else: treat them as real until you know otherwise. Honoring these 280 costs at most $2,240, or $8 each.
Don't mass-delete. A deleted account can't become a customer.
Tell people, without accusing anyone. Customers who hit errors get a plain account of what happened. The newsletter partner gets the true numbers. Anyone whose credits are paused gets something like this:
A message you can send
A code you used was shared outside the group it was meant for, so we've paused those credits while we sort it out. Your account is fine, and we'll update you by Friday. If this looks wrong to you, reply and a person will take a look.
Reissue the offer to the people it was for. Send fresh personal codes to the newsletter list. Ask the deal site to remove the old one, but don't wait on the answer.
How to design a coupon code that survives a leak
- One code per person. A forum post now burns one redemption instead of all of them. See single-use or multi-use promo codes.
- A hard redemption cap, enforced on your server. A cap of 200 limits the night to $1,600. It can't choose who gets those 200, though. The 60 slots left at 6 p.m. would have gone to the forum, and your newsletter readers would have seen "code expired".
- A short expiry. Worth having, and it wouldn't have mattered here. Every redemption above landed inside 24 hours.
- Release the reward in parts. Give 200 credits at redemption and the rest after real use. That's $0.80 up front (200 × $0.004), so 1,720 accounts cost $1,376 instead of $13,760. Start by working out what a free user costs you.
- An alert at your planned total. An alert at 200 redemptions would have fired before midnight, with most of the money still unspent.
The basic checks on a coupon, and how each one breaks
Those choices limit how bad a night gets. None of them tells you whether the person redeeming has already had the reward, so most teams add basic checks next.
| Check | What it catches | What it misses | Who it wrongly blocks | Cost to keep working |
|---|---|---|---|---|
| Email verification | Fake and mistyped addresses | Any second inbox that works | People whose email lands in spam | Deliverability work |
| One redemption per email | The same address twice | Every new address | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains and ordinary mailboxes | People using privacy forwarding | A list someone updates forever |
| Rules for Gmail dots and plus signs | One Gmail inbox written many ways | A real second mailbox | People who sort their mail with plus addresses | Upkeep as mail services change |
| CAPTCHA at redemption | Simple scripts | Anyone redeeming by hand | People using screen readers or privacy tools | Fees and lost redemptions |
| Phone or card requirement | Casual repeat accounts | Anyone with another number or card | Students, people without a reliable mobile number | A charge per text, fewer redemptions |
| One per IP address | Repeats on one connection | Any other network | Offices, campuses and households | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Everything off your list | Staff on work VPNs and privacy-minded people | Another list to maintain |
| Rate limits | Bursts from one source | A slower run spread out over hours | Real readers when a newsletter lands | Tuning for every campaign |
| Manual review | What a person can spot | Whatever arrives at 4 a.m. | Whoever looks odd to a tired reviewer | Hours for every campaign |
The alias rule would have caught last night's inbox. The next run won't use that inbox. The IP limit stops mattering once traffic moves to another network. Reviewing this night by hand, at 30 seconds an account, is 17.8 hours (2,140 × 30 seconds).
Stack all of them and a real newsletter reader meets a verification email, a puzzle, a phone prompt and a card form, all to collect a discount you were trying to give them. You'd rebuild that stack before every campaign.
Who should get the reward?
AbuseZero exists for the question every row in that table leaves open: does this claim look like a repeat? Make each campaign its own benefit, and one API call before you grant it returns a clear allow or deny, under rules you control. Where your alias rule saw a few spellings of one inbox, AbuseZero checks mailbox aliases, disposable domains and mail routing. Your IP limit ended at the address, and AbuseZero sees beyond it with VPN, hosting, network reputation, Tor and proxy intelligence. It recognizes repeat devices across new accounts, even when email addresses keep changing, and it blocks spammy bots, browser automation and malicious scripts while allowing genuine AI agents and assistants. The scale is what you can't build in a sprint: 140,000+ signals examined by multi-layer AI risk analysis, which detects linked claims and flags abuse that single checks miss. The proprietary algorithm comes with AI that checks the claim again. Creating a fresh account isn't enough to erase previous activity.
You don't have to build your own abuse prevention system. Observe mode shows you what would be denied before anyone is blocked, and the quickstart protects your first benefit. Keep your caps and your personal codes. They decide how much a bad night can cost.
Frequently asked questions
What should I do first when a coupon code leaks?
Turn the code off everywhere it's honored, then freeze unspent rewards. Raise any provider limit only after that.
Should I honor a leaked coupon code?
Honor it for anyone who redeemed before the leak, and usually for real people who redeemed after it. They didn't do anything wrong. Take back unspent rewards only from accounts you can show are repeats.
Are single-use codes enough?
They stop one post from being redeemed by everyone. They don't stop one person collecting several codes on several accounts. An AbuseZero evaluation tells you whether each claim should go through.
Protect your next campaign
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 campaigns and custom terms.