radar-fraud-rules

Radar & Fraud Rules

Stripe MCP Setup

Requires Stripe MCP connected via OAuth or restricted key. Docs: https://docs.stripe.com/mcp

GetMcpTools with server: "user-Stripe" (or plugin-stripe-stripe) before any call
Prefer stripe_api_search → stripe_api_details → stripe_api_read for list/retrieve
Always paginate — limit: 100, follow has_more with starting_after
Amounts are in cents unless noted
Never expose secret keys in output

Assess Current Rules

Dashboard: Radar → Rules. Document enabled vs disabled.

Default rules often include:

Block risk_level = highest
Default block lists
3DS / CVC / postal (often disabled)

Custom rules require Radar for Fraud Teams.

Recommended Rules (SaaS subscriptions)

Priority	Rule	Action
1	`:card_funding: = 'prepaid'`	Block
2	`:is_new_card_on_customer:`	Request 3DS
3	`:risk_level: = 'elevated'`	Review
4	Repeat failed CVC	Block (if enabled)

Start with Review before Block to measure false positives.

Verify Impact

After rule change, compare blocked payments in Dashboard → Payments (outcome: blocked).

search_stripe_documentation for latest Radar attribute names.

Output Template

Radar Audit

Current rules: [summary from user screenshot or API if available]
Recommended additions:
1. [rule] — [rationale]

Rollout: Review → 7d → Block