#lalith_53999

1 messages · Page 1 of 1 (latest)

pale bladeBOT
woven whale
#

So you're handling 3DS with an external provider?

#

Because Radar is somethign different

tight oxide
#

First I'm new to Stripe. I went through documentation and found that 3DS is bound with Radar rules that cover frauds. I don't need a fraud tool. at the same time i don't have 3rd party 3DS provider. I'm happy to use the Stripe for that.

woven whale
#

I went through documentation and found that 3DS is bound with Radar rules that cover frauds.
Not necessarily true. 3DS is requested by the issuing card/bank, not by Stripe. You can force 3DS with Radar rules, sure. But it's not a required part of the flow

tight oxide
#

that is good news..

#

May i know if ther is any quick guide , demo or sample code for this integration

woven whale
#

All of our payment APIs and UIs support 3DS flows out of the box, you just need to use the correct test cards to trigger the flow: https://stripe.com/docs/testing#regulatory-cards

Use test cards to validate your Stripe integration without moving real money. Test a variety of international scenarios, including successful and declined payments, card errors, disputes, and bank authentication. You can also test non-card payment methods and redirects.

tight oxide
#

do we need any confug changes to enable 3DS ?