Back to Blog

How to stop student discount abuse in SaaS

A student offer asks two questions and most setups only ask one. How to prove who's a student, limit repeat claims, and which basic fixes break on campus.

Say you run an AI writing tool. Pro is $20 a month, and this September you've set aside $6,000 for a student push. Anyone with a school email gets a free student pack of 6,000 AI credits, which costs you $12 in model usage if it's all spent. $6,000 ÷ $12 is 500 packs. You send the offer to your newsletter at 6 p.m. on Tuesday the 8th and go to dinner.

By 9:30 p.m. there are 140 claims, and your co-founder drops a screenshot in the team chat with a row of rockets under it. Last September's student post brought in 60 signups all week. At 11 p.m. you're at 230, and you go to bed happy.

At 6:58 a.m. your model provider's $8,000 monthly limit is reached. Paying customers had used $2,400 of it so far, which left the packs $5,600 of room, and they filled it. Your product starts returning errors to everyone. You find out at 8:20, from a customer on your $99 team plan: "Nothing has generated since before 7. Are you down?" You raise the limit from the kitchen. That's 82 minutes of failures for every person who pays you.

Then you open the claims table to meet all these students. All 500 packs are gone. 463 of them went to one mailbox at one university, written 463 different ways with plus addressing. Each address was confirmed by a link clicked in that one inbox, and a script then ran each account until its credits were used up.

463 accounts x 6,000 credits = 2,778,000 credits
463 accounts x $12           = $5,556 on your model bill
$5,556 / $6,000              = 93% of the campaign, to one person

If you typed student discount abuse SaaS into a search bar this morning, you may be looking at your own version of that table. The spike your team celebrated was one person, and the reward has already been paid. Your provider charged for those credits the moment they were used, so deleting all 463 accounts gets you back exactly nothing.

Cost per real student=Campaign budgetReal students reached\text{Cost per real student} = \frac{\text{Campaign budget}}{\text{Real students reached}}

You planned on $12 a student. With 37 real students in the 500, it's $6,000 ÷ 37, about $162. If you spend $10,000 a month, $5,556 is about 17 days of runway. Credit a month to the 11 teams who complained and that's another $1,089 (11 × $99), for $6,645 in total.

At 10:15 a.m. a student writes in: "I used my school email and it says the offer's over. Did I really miss it by one night?" The people you wrote this campaign for were asleep when it ended. So now you get to choose. You can put up another $6,000 with nothing changed, or tell your whole list that the student offer lasted one evening. The screenshot with the rockets is still pinned in the chat.

Why student discount abuse gets past verification

A student offer asks two questions, and most setups only ask the first. Is this person a student? Has this person already had this? Verification answers the first one. It can't say anything about the second, because a real student passes it every single time.

That's what stings about the scenario. Your school email rule was right 463 times. That person really is a student.

So the obvious fix, tougher proof of enrollment, doesn't touch the problem. You can ask for a student ID, a class schedule and a letter from the dean, and the student who claimed 463 packs can still provide all of them.

NoYesNoYesSomeone claimsthe student offerIs this persona student?Show theregular priceAlready hadthis offer?Grant it andrecord the claimExplain why andoffer a way to ask
NoYesNoYesSomeone claimsthe student offerIs this persona student?Show theregular priceAlready hadthis offer?Grant it andrecord the claimExplain why andoffer a way to ask

Treat them as two jobs in your code, so you can improve either one without breaking the other.

How to prove someone is a student

Each basic option trades your effort against how many real students it can reach.

Verification effort vs reach (illustrative)Thorough and slowEasy and openEasy and narrowCostly and narrowLow effortHigh effortFew real studentsMost real studentsHonor checkboxSchool email listVerification serviceID upload review
Verification effort vs reach (illustrative)Thorough andslowEasy and openEasy andnarrowCostly andnarrowLow effortHigh effortFew realstudentsMost realstudentsHonor checkboxSchool email listVerification serviceID upload review

A school email list catches anyone without a school address. It misses graduates, because some schools let people keep their address after they leave, and at a $10 student rate someone who stays on for three extra years costs you $360 ($10 × 36). It wrongly turns away students at schools not on your list. .edu is mainly an American suffix, and plenty of universities elsewhere use .ac.uk or a plain national domain. Someone has to keep that list current.

An ID upload with manual review catches casual attempts. It misses a good edit, and it rejects blurry phone photos and schools that don't issue cards. At two minutes each, 500 claims is 1,000 minutes, nearly 17 hours, in the one week you wanted the offer to feel instant. You're also now storing images of people's IDs.

A student verification service reaches the most people for the least work on your side. You pay per verification, and coverage varies by country and school. An honor checkbox costs nothing and proves nothing, which can be fine for a small discount and isn't for a pack that costs you $12.

Whichever you pick, make the status expire after 12 months. And notice that moving a dot anywhere on that chart doesn't help with the second question.

The basic fixes for repeat claims, and how they break on campus

Most teams reach for these next. Each one catches something, and students are an unusually bad audience for several of them.

Basic fixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead addressesAny second working addressStudents whose school filters your mailDeliverability work
Unique emailsThe same address twiceThe same mailbox written differentlyAlmost nobodyVery little
Disposable-domain blocksKnown throwaway servicesReal school mailboxes, all of themPeople using privacy forwardingA list updated forever
Plus addressing and dotsOne inbox written several waysA second real mailboxClassmates, if applied too widelyUpkeep as mail services change
CAPTCHASimple scriptsSomeone claiming by handStudents using screen readersFees and lost signups
Phone or card requirementCasual repeat claimsAnyone with another number or cardStudents with no card, international students between plansTexting fees and far fewer signups
One per IP addressRepeats on one connectionAny other networkEveryone else in the dormExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listStudents on their school's VPNAnother list to maintain
Rate limitsBursts from one sourceA slow, steady run of claimsReal students at term startTuning every term
Manual reviewWhat a person can spotAnything overnightWhoever looks odd to a tired reviewerHours every campaign

Plus addressing and Gmail dots are facts about how email works, and they vary. Gmail ignores dots in personal addresses, and a rule built on that needs upkeep.

The IP rule is worse. A residence hall of 600 students can share a handful of public addresses, so one claim per address gives the pack to whoever got there first and turns away the rest of the building. Blocking VPNs lands on students too, since many schools run one for off-campus access.

How to limit the damage before your next student offer

None of these tells you who claimed twice. They shrink what one person can take in a night.

Write the limit down. Decide what one student gets, and how often. The student rate might be once a year, and the free pack once per person. Treat them as separate offers.

Hand out the expensive part in stages. Give 1,000 credits at claim, worth $2, and the rest across the term. In the scenario, the first night drops from $5,556 to $926 (463 × $2).

Release packs by the day. At 100 packs a day, 500 packs last five days, and the worst single night is $1,200 (100 × $12).

Give the campaign its own budget. Run it on a separate provider key with its own hard cap, so a student offer can't take paying customers down with it.

Decide what a no looks like. Some people you turn away will be real, so give them a fair message and a way to reach you.

A bad night gets a lot cheaper. The packs still go to the same person, just more slowly, and every rule in that table needs someone to patch it and apologize for it again next September. The same goes for promo codes and referrals.

The part you don't have to build

Keep whatever answers the first question, and you don't have to build your own abuse prevention system for repeat claims. Evaluating whether this claim looks like a repeat is the job AbuseZero does, starting where the unique-email rule and the per-IP limit gave out. Creating a fresh account isn't enough to erase previous activity. AbuseZero flags abuse that single checks miss. Its multi-layer AI risk analysis examines 140,000+ signals and detects linked claims. Those signals are read together, never one at a time. There's also a proprietary algorithm, with AI that checks the claim again. AbuseZero checks mailbox aliases, disposable domains and mail routing. It recognizes repeat devices across new accounts, even when email addresses keep changing, and it sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence.

Before a pack or a student rate goes out, your server makes one API call and gets a clear allow or deny, under rules you control. Eligibility can be once per user, once per calendar month or once every set number of days. Observe mode shows you what would be denied before anyone is blocked, and the quickstart gets your first benefit protected.

Frequently asked questions

What is student discount abuse?

It's one person claiming a student offer more times than you meant to give it, or someone who isn't a student claiming it at all.

Is a school email enough to verify a student?

It's a reasonable start for a small discount. It misses students at schools off your list and lets some graduates through, and it can't tell you whether that person already claimed.

What if a real student asks for a second pack?

Decide in advance, and make any exception by hand. What to do when a customer asks for a second free trial has a fair way to handle it.

Keep your student offer for students

Keep reading

Copying your prompt…

Copied the to your clipboard. Give it to your coding agent & it will handle the rest.