Radar risk signals for any payment processor

Using its AI models, Radar can evaluate payments from any processor in real time and return risk signals. You can request a payment evaluation at any time in the payment lifecycle, and 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

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

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 a payment from a non-Stripe processor, you must:

• Create a tokenized PaymentMethod. We currently support 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.