How to protect a lifetime deal from repeat redemptions
Lifetime deal abuse costs you every month, for good. The code limits and stacking rules to set first, and where the basic fixes break.
It's 7:52 a.m. on Wednesday, and the last thing you sent your co-founder is still on your phone: "ALL 200 GONE. 8 hours 41 minutes!!" You sent it at 11:41 last night with a screenshot of the redemption counter. Now a reply has landed on your launch email. "I've read your newsletter for two years. I opened this over breakfast and the code's already dead. Who got them?"
You'd like to know that too, so you export the redemptions and sort by email. 163 of the 200 are Gmail addresses built from one name, with the dots in different places. Gmail ignores dots, so all 163 go to a single inbox. The launch you've been celebrating since last night was mostly one person.
This is a scenario, so swap in your own numbers and keep the arithmetic. Say your plan normally costs $29 a month and includes 3,000 AI credits, and your launch code made it free for life for the first 200 people. At $0.002 a credit, a fully used seat costs you $6 a month. You also added a 10,000-credit launch pack, which is $20 a seat, and set aside $4,000 for the whole campaign. Between 1 a.m. and 5 a.m., all 163 accounts spent everything they'd been given:
- 163 launch packs × $20 = $3,260
- 163 first-month allowances × $6 = $978
- Spent by morning: $4,238, which is $238 more than the entire budget
That money went to your model provider overnight. Nobody paid for those seats, so there isn't even a payment to reverse. Meanwhile 37 real people got a seat, and everyone else who opened your email got an error message. Those are the readers you wrote it for.
So you open a new tab and type lifetime deal abuse SaaS into a search bar, because the worse part has just occurred to you. A leaked discount costs you once. These seats have no end date, and on the 1st of every month those 163 accounts fill back up:
- 163 × $6 = $978 a month
- $978 × 12 = $11,736 a year
- 34 customers at $29 a month to cover it (34 × $29 = $986), before you've paid to serve any of them
If your company spends $12,000 a month, that's nearly a whole month of runway every year, for someone who paid you nothing. Run it forward and the campaign you budgeted at $4,000 looks like this:
At 9:10 a.m. your co-founder asks what you're going to do. You can honor the 163 seats and pay $61,940 over five years. You can void them, which takes back something you called lifetime on the strength of one morning's spreadsheet. Or you can open 200 more seats for the readers you shut out, and take the same risk again tonight. The number you were about to put in the investor update was 200. The real one is 37.
Why lifetime deal abuse lasts so long
Most redemption systems ask two questions: is this code real, and has it reached its limit? Neither is about the person holding it. A cap of 200 doesn't limit anyone to one seat. It only decides when the giveaway stops, so every seat one person takes comes out of someone else's share.
A code that's paid for isn't safe either, because the revenue arrives once and the cost arrives forever:
A $49 code on a $6 seat covers about 8.2 months. In month 9 it starts costing you, and it doesn't stop. Someone holding 20 of those codes paid you $980 and costs you $120 a month from then on. Stacking sharpens this: when one account can hold several codes, or add a lifetime code to a referral reward, each extra code adds cost with no new customer attached.
The obvious fix is one code per account, and you should build it. Just know it holds only until someone creates another account.
Code limits and stacking rules to set before you launch
Give every buyer their own code. One shared code with a cap can be emptied by whoever finds it, which is how codes that leak to deal sites do their damage. Single-use codes limit each leak to one seat.
Allow one redemption per account per campaign, and let the database refuse the second:
create table redemptions (
code text primary key,
campaign text not null,
account_id uuid not null,
redeemed_at timestamptz not null default now(),
unique (campaign, account_id)
);Insert with on conflict do nothing, and grant the seat in the same transaction only when a row comes back.
Write the stacking rule down. Decide how many codes one account can hold, what each extra code adds, and whether a lifetime code combines with a referral reward or a welcome bonus. Start from one code and no combining. If you sell stacks on purpose, swap the second unique rule for a stack_position column limited to 1 through 3, unique per campaign and account.
Pay rewards slowly. Hold bonus credits for 14 days. In the scenario, that takes the first night from $4,238 to $978.
Give lifetime seats a fair-use limit and their own budget, so a bad night can't use up the capacity your paying customers rely on.
Define "lifetime" in your terms. Say it means the life of the product, that it's one per person, and what lets you end a seat. Have whoever handles your legal terms read it before launch.
How the basic checks on a lifetime deal break
Every rule in that chart counts accounts, and someone with 163 accounts passes 163 times. Most teams add the checks below, and each one catches something.
| Basic fix | Catches | Misses | Wrongly blocks | Upkeep |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | 163 confirmations landing in one inbox | People whose code goes to spam | Deliverability work |
| Unique emails | The same address twice | Any address spelled differently | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains, ordinary mailboxes | People using privacy forwarding | A list updated forever |
| Gmail dots and plus addressing | One Gmail inbox written many ways | A second real mailbox | People who sort their mail with plus addresses | Upkeep as mail services change |
| CAPTCHA | Simple scripts | A patient person: 163 puzzles at 15 seconds is 41 minutes | People using screen readers | Fees, lost redemptions |
| Phone requirement | Casual repeat claims | Anyone with another number | People without a reliable mobile | A charge per text |
| Card requirement | Casual repeat claims | Anyone with another card | People who won't enter a card for a gift | Fewer redemptions |
| One per IP address | Repeats on one connection | Any other network | Agencies, campuses, households | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Everything off your list | Staff on company VPNs | Another list |
| Rate limits | Bursts of redemptions | One every 3.2 minutes (521 ÷ 163) | Real buyers in the launch rush | Tuning each deal |
| Usage caps | One seat overrunning | Each new seat's fresh cap | Your heaviest real users | Deciding when to stop |
| Shorter deal window | Slow leaks | A cap that filled in 9 hours | Readers who open email late | Less reach |
| Manual review | What a person can spot | Anything before you wake up | Whoever looks odd | 200 × 2 minutes = 6 hours 40 minutes |
A dot rule would have caught this one person, because that's how aliases work. The next person brings a second real mailbox. Stack everything else on top and your form asks a reader of two years for a verified email, a puzzle, a phone number and a card, all to accept a thank-you.
What you need to know is whether this person already has one, and your database only knows accounts. Guess wrong one way and you pay for that seat for years. Guess wrong the other way and you've turned away a real customer. A monthly promo gives you another try next month. With a lifetime deal, whatever gets through on launch night stays on your books.
Evaluate the claim before the seat exists
AbuseZero was built to tell you whether a claim like this should go through, and it picks up where those table rows ran out. It puts 140,000+ signals through multi-layer AI risk analysis that detects linked claims and flags abuse that single checks miss, and those signals are read together, never one at a time. The evaluation comes from a proprietary algorithm, with AI that checks the claim again. AbuseZero checks mailbox aliases and disposable domains, recognizes repeat devices across new accounts even when email addresses keep changing, and sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. On a paid deal, it detects repeated payment fingerprints across users, even when new accounts and emails hide the connection. For an offer with no end date, one line matters more than the rest: creating a fresh account isn't enough to erase previous activity.
You don't have to build your own abuse prevention system to run a deal you'll be honoring for years. Set the deal up as a benefit with once-per-user eligibility. Your server makes one API call before it applies the code and gets a clear allow or deny, under rules you control. Observe mode shows you what would be denied before anyone is blocked, and you can import past redemptions from earlier deals.
Frequently asked questions
What is lifetime deal abuse?
It's one person collecting more lifetime seats or codes than you meant to give them, usually across several accounts.
Should I allow code stacking on a lifetime deal?
Only if you've priced it. Work out how many months a stack pays for itself, then cap the number of codes.
How many lifetime codes should I issue?
Divide your campaign budget by a year of cost per seat at full use. $4,000 ÷ ($6 × 12) is about 55 seats.
Can I cancel lifetime seats after abuse?
That depends on your terms, so ask whoever handles them. Keep your evidence and give people a way to reply, because some will be real. See how to take back free credits after an abuse wave.
Set your rules before the next deal goes out
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 volumes and custom terms.