In the Stripe Dashboard under Radar > Rules, create a new block rule targeting low-amount authorization patterns, for example: block if charge amount is less than 100 and the card has been declined more than 3 times in 24 hours.
Add a review rule for velocity on a single IP address by using the :ip_address: attribute combined with a count-over-time condition.
Use the metadata attribute in Radar rules to allow trusted internal flows to bypass rules by setting a known key-value pair on the PaymentIntent.
Enable the 'Request 3DS' rule for payments where the Radar risk score exceeds a threshold you choose based on your chargeback tolerance.
Test rules in review mode before switching to block to observe false-positive rates on real traffic.
Monitor the Radar review queue daily during the tuning period and adjust thresholds based on dispute-to-review ratios.
Known gotchas
Radar rules are evaluated in order; place more specific rules above broader ones to avoid unintended blocks on legitimate transactions.
The machine-learning Radar score reflects card-level risk, not order-level risk — combine it with your own metadata signals for best results.
Blocking at the Radar layer still incurs the authorization network fee on some acquiring setups; verify with Stripe support whether soft declines from rules trigger fees.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?