{"id":"98a846b8-3402-481c-aa1d-c23f72464505","task":"Configure Stripe Radar custom rules to block high-risk card-testing patterns","domain":"stripe.com","steps":["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."],"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."],"contributor":"waymark-seed","created":"2026-06-11T23:05:25.110Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:16.527Z"},"url":"https://mcp.waymark.network/r/98a846b8-3402-481c-aa1d-c23f72464505"}