Stripe Radar API
Stripe Radar REST API — reads fraud signals, review queues, and manages custom fraud rules to allow or block payments based on machine-learning risk scores and configurable rule logic.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Stripe maintains PCI-DSS Level 1 compliance, SOC2 Type II, and ISO 27001. Restricted API keys allow least-privilege access for Radar-only workflows. TLS 1.2+ enforced. Secret key must be stored securely — no scoped OAuth for Radar-specific access.
⚡ Reliability
Best When
You are already processing payments through Stripe and want to automate fraud review workflows or dynamically manage rules in response to threat intelligence.
Avoid When
You process payments outside Stripe or need a fraud scoring layer that works across multiple payment processors.
Use Cases
- • Agents fetching fraud review queues and automatically approving or rejecting flagged payments based on supplemental business logic
- • Agents reading Radar rule outcomes for disputed charges to build evidence packages for chargeback responses
- • Automated rule management — agents creating or updating Stripe Radar rules in response to emerging fraud patterns detected externally
- • Risk monitoring — agents polling early fraud warning (EFW) data to detect and alert on rising dispute rates by product or geography
- • Post-authorization enrichment — agents querying Radar signals on a payment to decide whether to fulfill an order or hold for manual review
Not For
- • Standalone fraud detection without Stripe — Radar only scores Stripe-processed payments; use Sift or Kount for payment-agnostic fraud scoring
- • Real-time blocking at checkout without Stripe — Radar operates inside Stripe's payment flow, not as an independent middleware layer
- • Chargeback dispute filing — Radar provides signals but the Stripe Disputes API handles actual dispute responses
Interface
Authentication
Standard Stripe secret key authentication (Bearer token). Radar endpoints are part of the core Stripe API — no separate credentials needed. Use restricted keys with only the permissions required for fraud review workflows.
Pricing
Radar is bundled with Stripe's payment processing. API access is included with a Stripe account. No separate per-call pricing for Radar API reads or rule management.
Agent Metadata
Known Gotchas
- ⚠ Radar rules use a custom DSL (Radar Rule Language) — agents generating rules must learn this syntax, not standard JSON predicates
- ⚠ Rule evaluation is asynchronous from the API call — a newly created rule does not retroactively affect past payments
- ⚠ Review queue items expire — agents must process reviews within the window or they auto-close
- ⚠ Test mode and live mode are completely separate — rules created in test mode must be recreated in live mode
- ⚠ Some Radar signals (e.g., IP risk scores) are not directly exposed via the API and are only visible in the Stripe Dashboard
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Stripe Radar API.
Scores are editorial opinions as of 2026-03-06.