How to protect regional pricing from abuse
A regional discount is worth hundreds per seat and it's paid out at checkout. What it costs you, which basic fixes break, and how to keep the price fair.
One seat of your product costs $480 a year at list price. In your lowest regional tier the same seat costs $144, because you took 70% off so a freelancer in Nairobi or a two-person studio in Dhaka could afford what a team in Chicago can. This whole post is a scenario, and every figure in it is an assumption to swap for your own. Follow the sum down anyway:
One seat at list price: $480 a year
The same seat at 70% off: $144 a year
Lost on one seat sold wrongly: $480 - $144 = $336
One 8-seat team sold wrongly: 8 x $336 = $2,688
30 teams like it in a year: 30 x $2,688 = $80,640If you typed regional pricing abuse SaaS into a search bar, you already suspect you've got a line like that last one somewhere in your billing export.
You find it by accident. An 8-seat team that paid you $3,840 last year didn't renew, and your email asking why goes unanswered. Two days later, at 10:20 in the morning, you're clearing the new subscriptions report and there's their company name on a brand new account: 8 seats, annual, lowest tier, $1,152 paid in full. You go back through the year by hand and count 30 teams that look like this one. That's 240 seats.
The reward went out the moment each of those orders cleared. That team holds 12 months of access at a price your own checkout offered them. Getting the $2,688 back means invoicing a company that never agreed to it and arguing about your own pricing page, 30 times over. So the loss is final on the day of the sale, and you're reading about it months later.
The other 600 regional seats you sold this year went to the customers you built the program for, and they paid you 600 × $144 = $86,400. For every dollar the program earned from them, it gave away about 93 cents somewhere else ($80,640 ÷ $86,400).
Bars are what honest regional seats have paid so far. The line is what the wrong seats have cost.
Say each seat costs you $60 a year to serve. A list seat leaves you $420 and a regional seat leaves $84, so every seat sold wrongly takes 4 new honest regional seats to make up ($336 ÷ $84). 240 seats × 4 = 960 new seats, and the whole program has 600. If you spend $25,000 a month, $80,640 is a little over three months of runway. If only half of those teams would ever have paid list, it's still $40,320, more than six weeks of runway.
So somebody proposes the fix you can ship this week: cut the discount to 50%, which makes the regional price $240. Say a third of your honest seats can't pay that and leave:
Honest seats left: 600 - 200 = 400
Their revenue now: 400 x $240 = $96,000
Still lost: 240 x $240 = $57,600$96,000 beats $86,400, so the spreadsheet calls it a win. Two hundred of the seats you built this for are gone, that freelancer in Nairobi may be one of them, and the 240 you were worried about are still $240 short of list. That's the decision on your desk: keep paying for it yourself, or send the bill to the customers you wanted.
Why regional pricing is so exposed
A free trial might give away a few dollars of compute. A regional price gives away hundreds of dollars per seat in a single moment at checkout, and it does it again at every renewal. Behind that moment, your pricing page makes a guess about where a visitor is, shows a number and never asks again.
The claims that cost you tend to look like these:
- A list-price customer cancels and comes back on a new account at the regional price.
- One buyer picks up discounted seats across several accounts, sometimes to resell them.
Right beside them sit people who've done nothing wrong, like someone who moved last year. Nothing here is about the countries on your list. Those customers are doing what you asked them to do.
This post won't cover how someone gets a price meant for somewhere else. You don't need that to fix the problem. The obvious fix is a better location check, and location answers a different question. At best it tells you where a connection seems to be during checkout. It can't tell you that this new account is the team that paid full price last month.
What the basic regional pricing fixes catch, and where they fail
What you really want to know is whether this buyer is who the price was for. Each of these gets at a small piece of that. Email rules show the limit quickly: Gmail ignores dots, and plus-tagged mail reaches the same inbox, so two addresses that look different can be one mailbox. A unique-email rule only compares strings.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| IP country check | Casual visitors from elsewhere | Whether the price fits this buyer | Locals on roaming or company networks | A location database to keep current |
| VPN blocks | Known VPN ranges | Everything off your list | People who use one for safety or work | Another list, forever |
| Card country rule | Cards from outside the region | Who's using the card | Locals with a card from a bank abroad | Declined payments and tickets |
| Email verification | Typos and dead addresses | Any real second inbox | People whose code lands in spam | Deliverability work |
| Gmail dots and plus addressing | One inbox written several ways | A second real mailbox | Almost no one, and it catches little | Upkeep as mail services change |
| One per IP address | Repeat orders on one connection | Any other network | Shared offices, cafes and campuses | Exceptions and tickets |
| Proof of address | Buyers with no local paperwork | Anything that changes after that day | People with no bill in their name | Reviewing and storing documents |
| Manual review | What a person can spot | Claims spread out over months | Whoever looks odd to a tired reviewer | Hours every month |
Manual review is the fallback, so price it. Your 840 regional seats came from about 430 orders: 400 honest orders averaging 1.5 seats, plus those 30 teams. At 12 minutes an order that's 5,160 minutes, or 86 hours a year, and a reviewer looking at a name and an address is still guessing.
Every fix also has a first ticket, and it rarely comes from the buyers you meant to stop. Turn on a card country rule and it comes from a designer in Lagos whose only card is from a bank abroad. Ask for proof of address and it comes from someone renting a room with no bill in their name, and now you're storing documents you never wanted. Block VPNs and it comes from someone who needs one to work safely. Each of them is a customer the regional price was for, being told they don't qualify.
What to change before you shrink the discount
None of this needs anything clever, and most of it makes a wrong claim cheaper.
Write down who the price is for. Say on the pricing page where a buyer has to be based, and whether a company with staff abroad counts. A plain written policy lets you refuse people fairly.
Sell your deepest tier monthly only. A wrong seat then costs $28 a month ($40 minus $12) instead of $336 up front, and an 8-seat team costs $224 a month, which you can stop. Some honest customers will miss the annual plan.
Cap seats at the regional price. At 3 seats per account, a wrong claim costs 3 × $336 = $1,008 instead of $2,688. A real 8-person studio would then pay $2,832 instead of $1,152 (5 × $480 + 3 × $144), so give them a way to ask for more. Each new account still starts with a fresh cap.
Run your rule again at renewal. Store the price each subscription was sold at, and look again before next year's discount goes out.
Write the refusal first. Show the list price, say why and give people a way to reach you, because some you turn away will be real.
Do all five and you'll lose less on each wrong claim, which is worth a lot at $336 a seat. What they can't settle is whether this claim should go through at all. A new account shows up with no history, at your best price, and your records have nothing to compare it to.
Evaluate the claim before the discount applies
You don't have to build your own abuse prevention system, and nobody should spend the next five years keeping a VPN list current. Where an IP country check gives up at a location, AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Email rules stop at a string, while AbuseZero checks mailbox aliases, disposable domains and mail routing. AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing, and it detects repeated payment fingerprints across users, even when new accounts and emails hide the connection. Its multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and there's a proprietary algorithm too, with AI that checks the claim again. Creating a fresh account isn't enough to erase previous activity.
Make your regional price a benefit. Before checkout applies the discount, your server makes one API call and gets a clear allow or deny, under rules you control. On allow, the regional price goes through. On deny, the buyer sees list price and your way to get in touch. Eligibility can be once ever or once per rolling number of days, and Observe mode shows you what would be denied before anyone is blocked, so you can watch a month of regional claims first. Protecting a benefit takes you through it, and your checkout still handles payment and tax.
Frequently asked questions
What counts as regional pricing abuse?
A buyer getting a price you set for a region they aren't part of, or claiming it again on new accounts. Write your own definition first, because you may be happy with a company that has staff abroad.
Should I drop regional pricing because of abuse?
Try monthly billing on the deepest tier and seat caps first. Dropping it hands the whole loss to the customers it was meant for, as removing a free tier does.
How deep can a regional discount go?
Start from your cost to serve. At $60 a seat, $144 leaves you $84. Anything below $60, which is 87.5% off $480, loses money on every honest seat too.
Keep the price you meant to offer
Start with Builder
Pay as you go. Evaluate your first regional claim today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.