How to stop duplicate signups with Clerk
Clerk can reject repeat emails and aliases once you turn it on. What to enable, why a user.created webhook can't refuse anyone and where duplicates still get in.
The cancellation form has "Other" picked in the reason dropdown and nothing in the comment box. It's from an agency on your $149 plan, 14 months in. You write them a real note that afternoon, not the template, and nobody writes back.
Say this is your product. Those 14 months were worth $2,086 (14 × $149), and you'd quietly counted on another $1,788 over the next year (12 × $149). You don't learn why they left until Thursday, when your model provider's invoice arrives: $7,644. Last month it was $3,100.
That can't be right, because you use Clerk. Emails get verified and nobody can sign up twice with the same address, and you filed that problem as solved the day you installed it. So you export October's new users and sit with the spreadsheet until it's dark outside. There are 1,900 new accounts. Of those, 1,420 used all 200 free credits inside a day and never came back.
- 1,420 accounts × 200 credits = 284,000 credits
- 284,000 credits × $0.016 = $4,544
- $3,100 + $4,544 = $7,644
Not one of those accounts broke a rule you had. Each is a valid Clerk user with a verified email. (This is a scenario. Swap in your own numbers and see what your month looks like.)
Then you search your logs for the agency and find 61 failed generations in two weeks. It's the same rate-limit error every time, always between 2 and 5 p.m. Your provider's per-minute quota is shared across every account you serve, and those were the hours the free accounts were burning through theirs. The agency never told you any of this. They picked "Other" and left. Nine more customers on the same plan hit the same error, so you credit each of them a month: 9 × $149 = $1,341.
That's $5,885 out the door this month ($4,544 + $1,341). If your company spends $18,000 a month, it's about 10 days of runway. The 1,900 signups in last week's investor update were at most 480 new people (1,900 minus 1,420). November's accounts are already coming in, so by 11 p.m. the choice in front of you is ugly: switch off the 200 free credits that brought you nearly every customer you have, or leave them on and pay this bill again. You type Clerk duplicate accounts into a search box.
Why Clerk duplicate accounts get through
Clerk did its job. That job is to say who's signing in, and it knows people by their identifiers. A new verified email is a new user, so someone with four mailboxes is four users, and four users collect your free credits four times.
The credits are your code, and they usually hang off the user.created webhook.
Look at where the webhook sits. By the time your handler runs, the user already exists. Clerk's docs say plainly that webhooks are asynchronous and that you can't rely on delivery as part of a synchronous flow. A webhook can record a signup, and it can never refuse one.
Delivery is also at least once, in no guaranteed order. Clerk retries until your endpoint returns a 2xx or the retries run out, so a handler that simply adds credits can add them twice. Fix that first.
import { verifyWebhook } from '@clerk/nextjs/webhooks';
import type { NextRequest } from 'next/server';
import { sql } from '@/lib/db';
export async function POST(req: NextRequest) {
let evt;
try {
evt = await verifyWebhook(req);
} catch {
return new Response('Invalid signature', { status: 400 });
}
if (evt.type === 'user.created') {
// One row per Clerk user, so a retry can't pay out twice.
await sql`
insert into free_credit_grants (clerk_user_id, credits)
values (${evt.data.id}, 200)
on conflict (clerk_user_id) do nothing
`;
}
return new Response('OK', { status: 200 });
}That protects you from Clerk's retries. It does nothing about the same person on a second Clerk user, because a new user has a new ID and the insert goes straight through. The obvious next move is to tighten the signup itself, and Clerk gives you real settings for that.
The Clerk settings to turn on, and where each one breaks
Work through these in order. Most take minutes, and each one does catch something.
Keep Verify at sign-up on. It's on by default. You'll catch typos and made-up addresses, and every account needs an inbox that works. It misses any real second inbox, and a catch-all domain can receive mail at as many addresses as its owner likes. The people it wrongly stops are the ones whose code lands in spam. There's more in does email verification stop fake accounts?
Turn on Block email subaddresses. It's on every plan and off until you enable it. Mail to jane+2@gmail.com reaches Jane's inbox, and Gmail ignores dots, so one mailbox can be written many ways. With this on, Clerk rejects a new address when its base address already has an account, and it ignores dots on Gmail. It misses a second real mailbox entirely. It can also stop someone who has a good reason for a +work account, and all they'll see is that the address is in use.
Turn on Block disposable email addresses. This one's also on every plan and off by default. It rejects domains known to be disposable, along with their subdomains. A domain nobody has listed yet walks through, and so does every ordinary mailbox. If it catches a domain your real users rely on, Clerk's docs tell you to contact support, so the fix isn't in your hands. See should you block disposable email addresses at signup?
Leave Challenge suspicious sign-ups on. It's on for new applications and challenges signups that look automated or come through VPNs, Tor or proxies. Plain scripts stop here. Someone creating accounts by hand doesn't, and a real person on a company VPN gets an extra step they didn't earn. CAPTCHA-style steps have limits of their own.
On the Business plan, set hourly limits. You can cap signups per IP address and per email domain, and block VPNs, Tor, proxies and hosting networks. The per-IP default is 15 an hour, which stops a burst from one place. October's 1,420 accounts come to about 2 an hour (1,420 ÷ 744 hours), so a slow month sits far under it. Clerk's docs warn that a real person on an office, campus or mobile network can be blocked once a shared address hits the limit. Blocking VPNs can turn away real signups the same way.
Move the credits off the webhook. Clerk's onboarding guide stores an onboardingComplete flag in publicMetadata and redirects anyone without it, and it calls that redirect a convenience, so the real gate belongs in each page or route that depends on it. Use the same shape for credits and grant them on your server when someone finishes onboarding or first asks for something expensive. Accounts that never come back now cost nothing, and you finally have a moment in your code where you can say no.
Give free traffic its own budget. A separate key and a hard spending cap for free users mean the free accounts can't eat the quota your agency's jobs run on. This does nothing about who's behind those accounts, and every honest free user hits the same cap.
The other basics, outside Clerk's settings
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs |
|---|---|---|---|---|
| Require a card | Casual second accounts | Anyone with another card | Students, people who want to try first | Fewer signups |
| Require a phone number | Casual second accounts | Anyone with another number | Countries outside Clerk's SMS allowlist | A paid Clerk plan in production |
| Fewer credits, shorter trial | Some cost per account | More accounts make up the gap | Every honest user | Fewer people reach paying |
| Rate limits | Bursts from one account | 1,420 accounts under the limit | Real users in a busy hour | Tuning per endpoint |
| Manual review | What a person can spot | Anything spread out slowly | Whoever looks odd to a tired reviewer | About 24 hours for 1,420 accounts at a minute each |
Turn on the Clerk settings and you're better off than you were, for an afternoon's work. You've stopped aliases, known throwaway domains and plain scripts. Here's who still arrives.
Every one of those is $3.20 of your money (200 × $0.016). Say November brings another 1,420 and these settings stop half of them, which is an illustrative figure because nobody can tell you the real share. The other 710 still cost $2,272 (710 × $3.20). October's 1,420 users stay put, because Clerk's protections apply to new signups and new email addresses, and existing users keep signing in. Users you create through the Backend API, in the Dashboard or by import skip the protections altogether.
Each of these settings asks about one signup. Clerk's protections page lists blocks, challenges and limits, and none of them knows that this account just got 200 credits. The question that cost you an agency is a different one: does this claim on those 200 credits look like a repeat?
Asking that question before the credits go out
AbuseZero exists to answer it, at the exact spot step 6 just gave you. Your server makes one API call before the credits move and gets a clear allow or deny, under rules you control. Second inboxes and slow months are where the settings above ran out, and that's where this starts. AbuseZero checks mailbox aliases, disposable domains and mail routing, and that's the small part. It puts 140,000+ signals through multi-layer AI risk analysis, which detects linked claims and flags abuse that single checks miss. You also get a proprietary algorithm, with AI that checks the claim again. AbuseZero 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. Creating a fresh account isn't enough to erase previous activity.
Clerk keeps running sign-in, and you don't have to build your own abuse prevention system next to it. Observe mode shows you what would be denied before anyone is blocked. The quickstart gets your first evaluation running, and protect a benefit covers the rest.
Frequently asked questions
Does Clerk prevent duplicate accounts?
It rejects an address already in use and, with Block email subaddresses on, aliases of a registered address. A different real address becomes a new user.
Can a Clerk webhook block a signup?
No. user.created tells you about a user who already exists. To say no, use a server step that runs before you grant anything.
Will these settings remove the duplicates I already have?
No. They cover new signups and newly added email addresses. Start by finding repeat users in your database, then merge them carefully.
Is every second Clerk account abuse?
No. People keep work and personal accounts. Write down what you mean to give each person before you turn anyone away.
Keep your free credits for new people
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.