Bot abuse prevention

Bot abuse occurs when bots attempt payments on your platform, violating your terms of service or bypassing your anti-bot policies. Radar evaluates whether a payment was likely made by a bot.

How bot score works

Stripe Radar assigns payments made on Stripe Checkout a numerical bot score between 0 and 99, where 0 is the lowest likelihood and 99 is the highest likelihood that a bot made the payment.

A high score indicates that a bot likely made the payment, not that the payment is fraudulent or the bot is malicious. Use the bot score to enforce your anti-scripting or anti-bot policies, instead of as a standalone fraud signal.

Block payments using bot score

Use the bot score with your policies against scripted or automated payments, such as preventing bots from buying limited-availability inventory.

You can:

• View the bot score in the Risk scores section on each payment details page
• Write custom rules on :bot_score: to block payments that exceed a threshold you define

Block payments using bot risk control

Use the bot risk control to automatically block Checkout payments that exceed a bot score threshold, without requiring custom rules. It scores Checkout payments only.

How bot risk control works

1. Stripe Radar assigns a bot score to each Checkout payment.
2. Radar blocks payments with a bot score that exceeds the configured threshold.

You can also write your own threshold logic to block payments using the bot score.