Local prices, local buyers.
Lower prices in some countries attract buyers from others through a VPN. Compare the device with the IP before you show the discount.
SignalsvpndatacenterIp
Step 3 of 3datacenterIp + vpnChallenge
Device clock
UTC+1mismatch
IP location
Brazil, hostingdatacenterIp + vpn
How it plays out
The attack, what the verified event shows, and what your code does about it.
01 · The attack
How it usually goes
- VPN shoppingChecking out through a cheaper country.
- Hosting exitsCommercial VPNs on datacenter ranges.
- Timezone tellsA Cairo clock on a Brazilian IP.
02 · What Trace sees
Fields on the verified event
- vpnDevice offset no zone of the IP country has.
"vpn": { "detected": true, "details": { "methods": ["timezoneMismatch"] }} - datacenterIpHosting ranges most VPNs exit from.
"datacenterIp": { "detected": true }
03 · What you do
Decide, with your own thresholds
- AllowLocal price
- Challengevpn: show the default price
Decision lab
Switch signals on and off. The score is a plain sum of weights.
Signals
Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.
20suspectScore / 100
AllowLet the action through.
20/ 100
reasons
vpn+20
Implementation
One browser call, one server check.
01IdentifyCall the SDK on the action and send the eventId with it.
02VerifyYour server reads the event with a secret key.
03DecideAllow, challenge or block, with your own thresholds.
identify.ts
const trace = createClient({ apiKey: 'pk_...', endpoint: 'https://id.example.com' });
// On the action (signup, login, checkout), then send eventId with the form.
const { eventId } = await trace.get();Example response, illustrative
{ "eventId": "evt_example"}Start in shadow mode. Block later.
Log the decision for a week, check who it would have stopped, then turn it on.