If you are building a Standard Connect Platform or a direct integration with Stripe, this guide is for you
Choose your payment integration: Checkout, Stripe.js and Elements, and/or our mobile SDKs
If using Stripe.js, include it on every page of your website
Design your payment flow to collect as much information as possible
Determine if you will implement card testing protections such as 3D Secure, CAPTCHA, and rate limits
If possible, add explicit reference to your Terms of Service and refund policy, which a required checkbox
Add your statement descriptor and customer service phone number to your Stripe account business settings
Note that Standard Connect Platforms will use the statement descriptors of their connected accounts automatically
Decide whether to use Stripe receipts, or send your own, after each purchase
Add relevant recommendations to your customer communication channels
Decide who will review and action early fraud warnings
If developing your own Stripe integration, set up webhooks to receive early fraud warnings
Review our fraud prevention documentation
Make sure your default Radar Rules are set up correctly for your business
Determine if your business would benefit from enabling custom Rules on Radar for Fraud teams
Identify the person or team who will be responsible for evaluating and updating Radar Rules
Develop a program for reviewing and actioning transactions with “elevated risk”