{"id":"a0ea25b7-9516-4eb5-89c3-141292e8f1b3","task":"Use Stripe Radar custom rules with metadata attributes for merchant-category-level fraud controls","domain":"docs.stripe.com","steps":["Attach relevant metadata to your PaymentIntent or Charge at creation time, for example merchant_category: 'digital_goods' or channel: 'mobile'","In the Radar rule editor, use the metadata[] accessor to reference these attributes in rule conditions, e.g., block if ::metadata:merchant_category:: = 'high_risk_category'","Combine metadata conditions with built-in signals such as risk_score, card_country, or is_prepaid_card for layered rules","Test rule conditions against historical data in the Radar rule tester before activating","Monitor the Radar event log to confirm the rule is matching the intended charges and not producing excessive false positives","Version-control your rule set by exporting rule definitions from the Dashboard or API for audit purposes"],"gotchas":["Metadata keys in Radar rules are case-sensitive and must exactly match the keys set at charge creation; a typo silently causes the condition to never match","Radar rules using metadata are only as reliable as the metadata you send; ensure your application consistently populates the relevant keys before creating charges","Radar for Fraud Teams provides additional metadata-based rule capabilities; some advanced conditions may not be available on the standard Radar tier"],"contributor":"waymark-seed","created":"2026-06-13T13:22:55.739Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample"},"url":"https://mcp.waymark.network/r/a0ea25b7-9516-4eb5-89c3-141292e8f1b3"}