Supported payment methods with Radar
Configure how Radar evaluates transactions against default risk controls.
Radar fraud protection is active by default for all Stripe users. Radar screens all payment methods against default risk controls, and blocks all high-risk transactions.
Default risk controls for all payments
Radar users on Standard or above are protected by a set of default risk controls that block high-risk payments. Radar is on by default, and applies to all payment methods. Radar supports most preview payment methods, but not deprecated payment methods.
You can view blocked payments on the Radar risk controls page in the Dashboard.
Radar Lite users
Stripe might still block payments for a variety of reasons, including but not limited to fraud risk, sanctions, and other compliance and regulatory considerations.
Custom risk settings
If your plan supports this feature, you can customize your risk settings for the following payment methods:
| Category | Payment methods | Status |
|---|---|---|
| Cards | Credit and debit cards, card-backed digital wallets 1 | Supported |
| Bank Debits | ACH, the related setting | Supported |
| the related setting, AU Becs, Bacs, NZ Becs, PayTo | Private preview | |
| Buy Now Pay Later | Affirm, Afterpay, Klarna | Private preview |
| Digital wallets | Cash App, PayPal | Private preview |
| Stablecoin and crypto wallets | Any compatible crypto wallet | Private preview |
1 For example, Apple Pay or Google Pay.
Risk controls
Private preview
To customize risk controls for any payment methods in private preview, you’ll need to opt in.
You can customize your risk controls with these features:
- Block and allow lists : Automatically block or allow transactions based on email address, IP address, email domain, and more.
- Custom rules : Create tailored fraud prevention logic using attributes .
- Rule backtesting : Test changes against historical data before implementing them.
- Radar analytics : View consolidated fraud and performance metrics across all of your payment volume.
Payment method rules
By default, all supported payment methods inherit your active Radar rules and settings. You can adjust individual payment method rules with the :payment_method_type: attribute.
For example, this rule applies only to transactions using Bacs Direct Debit, where the customer IP address has a high number of disputes:
Block if:payment_method_type: = 'bacs_debit' and:dispute_count_on_ip_weekly: > 3
Request early access
Request to join the preview for custom risk controls.
Enter your email to request access.
See also
- Customize Radar block and allow lists
- Customize Radar rules
- Monitor transactions with Radar analytics