Send codes to people, not to fraud rings.
SMS pumping triggers thousands of verification texts to premium numbers. Check the device before you pay for the message.
SignalsvelocitybothighActivity
Step 4 of 4botBlock
Send code
+20 10 •••• 441210:00:02Allow
+20 10 •••• 441210:01:30Allow
+882 •••• 091710:01:34Block
+882 •••• 091810:01:35Block
texts not sent2
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
- OTP floodsScripts requesting codes in a loop.
- Premium numbersTexts routed to numbers that pay the attacker.
- Rotating IPsPer-IP limits never trigger.
02 · What Trace sees
Fields on the verified event
- velocityEvents per visitor, per IP and per account.
"velocity": { "detected": true, "details": { "exceeded": ["eventsPerVisitor5m"] }} - botAutomated browsers requesting codes.
"bot": { "detected": true } - highActivityHundreds of events from one visitor a day.
"highActivity": { "detected": true }
03 · What you do
Decide, with your own thresholds
- AllowFirst code
- Blockvelocity: new numbers, same visitor
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
velocity+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.