LuisEgusquiza

[pastel schooner]

Hello! If you want to do this you'll need to either write a custom radar rule or implement this logic on your end

[radiant vessel]

can that rule be configured somewhere in stripe?

And about the internal lodge, do you have an idea of ​​how I can leave?

[severe cliff]

Hi there 👋 jumping in as my teammate needs to step away soon.

As they mentioned, there are two approaches to this. If you're using Radar for Fraud Teams, or would like to, then you can use that to write custom Radar rules in your Stripe dashboard. We aren't too familiar with that rule writing (we primarily focus on helping with our API) but this is a good point in our documentation to go to start learning about how those rules work and how to build them:
https://stripe.com/docs/radar/rules

The alternative approach is to adjust your payment process so that you get a Payment Method object earlier in the process. That allows you to write code that inspects the details of that Payment Method, and determine if it is one that you would like to let your customer use. If not, you would then redirect them back to a page where they can provide details for a new payment method. That process is a bit involved, but our guide for that type of flow can be found here:
https://stripe.com/docs/payments/build-a-two-step-confirmation

[radiant vessel]

Thank you very much for the answers.