Sign in
An image of the Stripe logo
Create account
Sign in
Home
Payments
Business operations
Financial services
Developer tools
No-code
All products
Home
Payments
Business operations
Home
Payments
Business operations
Financial services
Developer tools
Support
Overview
Fraud detection
    Overview
    Risk evaluation
    Risk settings
    Reviews
    Lists
    Rules
    Radar Session
    Testing
    Integration
    Disputes and fraud
    Analytics
Stripe data
Financial reports
Payment authentication reports
Revenue recognition
Startup incorporation
Climate
Identity
Tax
Financial Connections
Account
Dashboard
Radar
·
HomeBusiness operationsFraud detection

Risk settings

Set Radar's fraud blocking for your business with Radar for Fraud Teams.

Radar for Fraud Teams allows you to adjust the default risk score for blocking payments in your Radar settings:

Stripe Radar risk settings dialog

The risk settings dialog shows your block threshold, your dispute rate, and other important statistics

How it works

Stripe Radar gives each charge a numerical risk score between 0 and 99, where 0 is the lowest risk and 99 highest.

The default blocking threshold is 75, meaning Radar blocks charges with a score of 75 or higher.

For Radar to block transactions based on this threshold, you need to enable the default block rule or an equivalent custom rule.

The default manual review threshold is 65, meaning Radar sends charges with a score of 65 or higher to manual review. Changing the blocking threshold automatically changes the manual review threshold accordingly.

For Radar to send transactions to manual reviews based on this threshold, you need to enable the default review rule or equivalent custom rules.

Alternatively, use custom rules (Radar for Fraud Teams feature) to precisely control which payments Radar blocks, reviews, and allows.

When to use it

Risk Threshold Availability

The ability to increase risk score thresholds beyond their defaults isn’t immediately available to all users. If you’d like to enable this feature, contact us.

You can customize the default threshold to fit your own business needs. Setting the risk score threshold requires you to consider a tradeoff between how much fraud Radar blocks and how many payments it allows.

For example, if your business has low fraud rates and costs, you might want to increase the default blocking score so that you can allow more payments overall. As you increase the risk score, you might also allow more fraud.

Alternatively, you can decrease the score for blocking payments if you’ve experienced higher rates of fraud. As you decrease the risk score, you’re likely to block more fraud but also block more overall payments.

You can go to your Radar settings in the Dashboard to test the impact of changing risk score thresholds for your business.

If you’re increasing the risk score for blocking charges, we can’t accurately predict the impact of this change on your fraud rate (as some charges that were previously blocked will now be allowed). Be careful when adjusting the risk score in this direction.

Increasing your risk threshold in Stripe Radar

Increasing your threshold allows more payments, but may increase your dispute rate

See also

  • Risk Evaluation
  • Review
  • Integration Checklist
Was this page helpful?
Questions? Contact us.
Watch our developer tutorials.
Check out our product changelog.
Powered by Markdoc
You can unsubscribe at any time. Read our privacy policy.
On this page
How it works
When to use it
See also
Stripe Shell
Test mode
Welcome to the Stripe Shell! Stripe Shell is a browser-based shell with the Stripe CLI pre-installed. Login to your Stripe account and press Control + Backtick on your keyboard to start managing your Stripe resources in test mode. - View supported Stripe commands: - Find webhook events: - Listen for webhook events: - Call Stripe APIs: stripe [api resource] [operation] (e.g. )
The Stripe Shell is best experienced on desktop.
$