Stripe Radar
Payment fraud (chargeback risk, stolen card, velocity)
- Triggers:
- Hosted Stripe Checkout · Payment webhooks · Customer Portal updates
- Data shared:
- Stripe-internal payment object
Read-only demo account · Enterprise
The Awesome Company, Inc.
All capabilities enabled · unlimited quotas · 42 active agents · 4 workspaces
Account
Signals raised against your account once a vendor is live. None are live today.
No fraud-detection vendors currently process Intramedial customer data. When a vendor is live, every signal it raises about you appears here — no operator-private subset, and no invented inventory.
Every signal — score, action, provider, dispute status. Click "Dispute this signal" to challenge anything you disagree with.
Sign-in from Berlin shortly after a sign-in from San Francisco — flagged as geographically incompatible. Step-up authentication recommended.
Routine payment screening — no risk flagged.
Bulk API key issuance pattern flagged — 47 keys issued in 90 minutes across 3 IP ranges. Score reflects the combined velocity. You filed a dispute below.
"Bulk key issuance was intentional — we rotated all production runner keys for the May 19 SOC 2 attestation pen test sample. The 3 IP ranges are our CI runners (Vercel + GitHub Actions + Cloudflare Workers Builds). Happy to provide the runner inventory + the pen-test attestation reference."
Sign-in from a known Cloudflare WARP exit — VPN/proxy traffic is normal for many of our customers but logged for awareness.
This list matches /.well-known/fraud-providers.json. It stays empty until a vendor actually processes customer data.
Payment fraud (chargeback risk, stolen card, velocity)
Account fraud + ATO + fake account + payment fraud
Account takeover, suspicious login, credential stuffing
KYC + crypto fraud + sanctions
KYC + KYB document verification (Enterprise-only)
IP risk + proxy/VPN/TOR detection + geolocation anomaly
Disposable-email + phone-validation + IP/device fingerprinting