#rogeryang_popchill
1 messages · Page 1 of 1 (latest)
We're using the create checkout session api by the way.
I saw the parameter in the create payment intent api, using [payment_method_options.card.request_three_d_secure]
but not seeing in the checkout session api
Um yes it's not available in Checkout API, The general idea is Checkout is a blackbox and it optimize requesting 3DS by its own
What~~~
there's no way to force 3D auth?
we're intergrating the stripe connect's flow
so we use checkout session to intergrate the api for our connect account to create a payment
Yes the most enforcing way you can do is set every Radar rule. The most frequent one is "Request 3D Secure if 3D Secure is recommended for card". Other than that, unfortunately you can only force it with direct PaymentIntent integration rather than Checkout
but it is not 100% sure to make all the payment using 3D, right?
because some of the creditcard might not support 3D, then the radar rule will let it passed?
Yeah and that's expected. If the card does not support or not enrolled, there is no 3DS page to display
why we extremely want to force 3D, it's becaues when one payment occurs chargeback, if we used 3D then it's will reduce the success of the chargeback
Are we correct? Or, we should not insist in 3D forcing?
Yes that's correct, but you can only enforce it if the bank support. If they don't support, there is no 3DS page to show
The 3DS page is done by the bank
Yes, I know. so the card issue bank which not support 3D we don't want them to checkout
So, the only way we can reduce this happen, is using stripe radar?
For Stripe Checkout yes
I think you can do without the Team plan, but if you can't feel free to clarify with Support
ok, I see.