wafflcoptr_best-practices

[flat summit]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1288708765922889749

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[winged linden]

You can specify optional return_url on Payment Intent which changes 3DS behaviour (popup vs redirect). Is it ok not specify the url if we plan on using the Stripe JS to handle the payment intent next action (using stripe.handleCardAction(clientSecret))?
Yes, if the Payment Intent only accepts card payments, i.e. payment_method_types: ['card']

The request_three_d_secure param supports any or challenge. If we use the any as opposed to challenge does that have any sort of impact on the liability shift during disputes?
Payments that go through any form of 3DS (frictionless or challenge) will have liability shift

[brave ocean]

Thanks for the quick response.
Wrt to the second question is there any recommendation/guidelines on what flow to use if we plan on building our own fraud engine?

[winged linden]

Stripe Radar provides real-time fraud protection: https://docs.stripe.com/radar

What indicators do you plan to use for your fraud engine?

[brave ocean]

We have evaluated Radar and are unable to use it for the moment due to cost.

Initially we will have some heuristics built into our purchase process (essentially Radar custom rules) and when we detect a transaction has a high risk of fraud we want the highest guarantee 3DS will provide us that its not fraud. If the liability shift is the same on both frictionless and challenge flows it makes sense to me to use the frictionless flow since its the least impact to the customer. Is this the case?

[lost condor]

👋 taking over here

If the liability shift is the same on both frictionless and challenge flows it makes sense to me to use the frictionless flow since its the least impact to the customer. Is this the case?
Yes correct.

Ref: https://stripe.com/guides/3d-secure-2#:~:text=Even if a transaction follows the frictionless flow%2C your business will benefit from the same liability shift that it does for transactions that pass through the challenge flow.

[brave ocean]

Amazing, miss that bit on the doco.