Your checkout is not a card checker.
Fraudsters run stolen cards through small payments to see which work. Trace sees the same device and script behind the burst.
SignalsvelocityautomatedInputdatacenterIp
Step 4 of 4velocity + automatedInputBlock
•••• 4242$1.00Allow
•••• 0019$1.00Challenge
•••• 7731$1.00Block
•••• 5120$1.00Block
events per visitor, 5 min threshold
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
- Micro-chargesDozens of small payments in minutes.
- Scripted checkoutAutomated forms, not people.
- Rotating cardsA new card each try, same device.
02 · What Trace sees
Fields on the verified event
- velocityEvents per visitor in 5 minutes and per hour.
"velocity": { "detected": true, "details": { "exceeded": ["eventsPerVisitor5m"] }} - automatedInputCard fields filled by a script.
"automatedInput": { "detected": true } - datacenterIpCheckouts from hosting ranges.
"datacenterIp": { "detected": true }
03 · What you do
Decide, with your own thresholds
- AllowFirst attempt
- ChallengeSame visitor, new card
- Blockvelocity
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.