Enable the radar.early_fraud_warning.created webhook event in your Stripe Dashboard or via POST /v1/webhook_endpoints
When radar.early_fraud_warning.created fires, the event payload contains the charge id, payment_intent id, fraud_type (e.g. card_never_received, unauthorized_use), and actionable field indicating whether the warning can be contested
Retrieve the associated PaymentIntent and charge from your database using the charge id; check whether the order has been shipped; if goods have not been shipped, issuing a proactive refund reduces your chargeback rate
For digital goods or services already delivered, gather evidence immediately since the early fraud warning often precedes a chargeback by days to weeks
GET /v1/radar/early_fraud_warnings to list all warnings with optional filters on charge or payment_intent; use this for daily reconciliation of your fraud exposure
Known gotchas
Early fraud warnings are informational signals from card networks; receiving one does not guarantee a chargeback, but a high warning rate affects your account health and may trigger Stripe's monitoring programs
Refunding a payment after an early fraud warning does not always prevent the chargeback; the cardholder may have already filed a dispute with their bank before the warning was issued to Stripe
Radar early fraud warnings are only available on accounts with Radar enabled; Stripe Radar is included by default on most accounts but check your plan
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?