Your description does not match Stripe&#x27;s documentation.  Specifically, there&#x27;s no mention of matching geo-IP to billing address.<p>The problem I see with Stripe&#x27;s fraud prevention is that it appears to be &quot;all or none&quot;, with no visibility or control on our end.<p>The only control knob appears to be whether to allow Stripe to automatically decline things it thinks are fraud.  It doesn&#x27;t appear to provide any detail on why it thought something was fraud.<p>So it seems to leave two choices:<p>- Allow stripe to decline things, and try to address false positives manually. There is no &quot;go ahead and charge this button&quot;, by the way...you would have to contact the customer.<p>- Set stripe not to decline things, but lose even the limited visibility to &quot;stripe would have declined this&quot;.<p>The real problem, in my mind, is that fraud risk for both the banks and providers like Stripe is really small.  You risk very little.<p>The vast majority of the cost goes back the individual merchants&#x2F;sellers, who have the least visibility into what the risk of an individual transaction is.<p>Thus, there&#x27;s very little incentive for the banks, or stripe, to provide decent tools.  A shame, because your ability to see the bigger pictures means your tools would always be better than anything we can use.