Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management

Stripe's risk scoreDeprecated

Evaluate the level of fraud risk associated with an authorization.

Incorporate Stripe’s risk assessment into your business needs when deciding whether to approve or reject an authorization. The following statistics provide directional guidance on the performance of our tools, and depend on what you’re goals are: approval rate or fraud prevention. While these settings might not be customized to your business model, geography, or cardholder behavior, you can use them as a source of directional guidance when using Stripe’s tools. Contact us for support in adjusting these thresholds.

Network toolsStripe Issuing fraud tools
Optimizing for fraud preventionBalancing fraud prevention and approval rateOptimizing for approval rate
Precision: How likely the flagged charge is true fraud2%10-15%15-20%25-30%
Recall: % of all fraud caught by tooling by transaction volume2%25-30%20-25%10-15%
% Volume Impact: Estimated authorization volume impacted by fraud tooling0.10%0.06% - 0.07%0.02% - 0.04%0.01% - 0.02%

Stripe provides a composite score and risk categorization to help you assess the risk level of an authorization. The values exist on a 0-99 scale, with higher values representing higher risk. In addition to the risk score, Stripe provides an assessment of the authorization’s riskiness in an enum value. We label every authorization as ‘normal’ or ’high’.

We recommend backtesting your data against the score to assess opportunities to use the score to drive down fraud rates. For example, you might find that fraud_score > 20 and risk_level = normal equates to particularly risky authorizations for your portfolio and opt to block authorizations that satisfy those conditions.

Precision and recall are inversely related. When you block more transactions, the false positive rate increases while the likelihood of allowing fraud decreases. When you block fewer transactions, the false positive rate decreases. Set your blocking thresholds accordingly based on rigorous backtesting of your data and your own risk tolerance.

Learn more about the Stripe’s risk score.

Fraud classification

While our model is reliable, it inevitably flags:

  • False positives: Non-fraudulent transactions as high risk
  • False negatives: Fraudulent transactions as non-high risk

As Stripe refines the performance of its risk models, you can actively contribute to our refinement process by flagging both fraudulent transactions that we might not accurately identify and non-fraudulent transactions. You’ll also be strengthening the fraud prevention capabilities of the industry as a whole: when you flag a false negative, we send a fraud report to card networks, telling them about the fraudulent activity.

Use the API to report false positives and negatives

You can report false positives and false negatives while validating correct assessments (true positives and true negatives) through the Fraud Classification API. Using this API is optional for accessing Stripe’s risk score. However, your contributions improve the model over time. Due to this, we recommend automating reporting with this API in the early stages of your implementation

Learn more about the Fraud Classification API.

Stripe’s risk score is currently limited to beta users. You must be an Issuing customer to join the beta. To request access to the beta, log in to your Stripe account and refresh the page. Contact Stripe for more information.

Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc