Leaked codes triage
Find the codes extensions spread, keep them out of extension sessions, and watch them.
Why it matters
A code made for one audience ends up on coupon sites, and extensions try it at every checkout. Each use gives away a discount you meant for someone else. Containing the leaked ones protects your margin without touching the codes your customers rely on.
Who it's for
Stores that run influencer, staff, apology or one-off codes.
The steps
Step 1: See which codes extensions use
The Checkout rules page lists the codes used most in extension sessions, and whether your policy allows them.
In Benson: Open Checkout
Step 2: Mark the codes you never share publicly
Private codes stay off the allowlist, so they don't work in extension sessions.
In Benson: Open Codes
Step 3: Turn on the strict code policy
In extension sessions, only the codes you allow work. Auto-tried and leaked codes are turned away with a friendly message.
In Benson: Open CheckoutIncluded in Stop and above
Step 4: Watch the leaked codes
Benson starts watching a code when it spreads through extension sessions. Code watch shows whether it's contained, replaced or back again.
In Benson: Open Codes
How you'll know it worked
Fewer extension uses of the codes you meant to keep private.
What to watch: Code watch state
Do this in Benson
Every store starts with a free trial, no card. Steps that need a paid plan say so, and you can switch in a minute.
Start free trial
