Radar risk signals for multiple payment processors

Stripe Radar allows businesses to evaluate their externally-processed payments in real time and receive risk signals from the Radar AI models. You can request a payment evaluation at any time in the payment lifecycle–not only when you submit to the processor.

Fraudulent payment

The fraudulent_payment signal identifies if a payment will likely result in a dispute with a fraudulent reason code or an early fraud warning. Payment evaluations provide this signal by default.

Fraudulent dispute Private preview

The fraudulent_dispute signal identifies if a payment will likely result in a dispute and blocks these payments with a fraudulent reason code.

Early fraud warning Private preview

The early_fraud_warning signal identifies if a payment will likely result in an early fraud warning.

Prerequisites

Before you request a payment evaluation on an externally-processed transaction, you must:

• Create a tokenized PaymentMethod. We currently support only card type payment methods.
• Create a Radar Session token, which automatically collects advanced risk factors for each transaction.
• Collect the customer email by populating the billing_details.email attribute in the payment method or creating a new customer (either a customer-configured Account object or a Customer object).

The following diagram shows your initial call to create a PaymentEvaluation and the real-time response from Stripe with risk signals.