#zerox20044
1 messages · Page 1 of 1 (latest)
Hi there
I'm a bit confused by what you mean here?
Ah I think I understand
You can't send that info via the server, no.
It is specifically picked up and passed via the SDK when you handle 3DS client-side here
correct
but is going to be more secure we do the payment intent on the SDK
?
our logic currently is doing it on the server side because some deals and discount being calculated prior the final charge
but with the 3d secure we want to be sure what would be the recommended approach, move that payment logic to the client side so that gathered info is sent or that would no be so relevant on the security side for show the 3ds
It is secure either way really and is just a preference for how you want your integration built
The key is that you handle 3DS client-side, but in terms of actually confirming the payment you can do that server or client-side
Just depends on your flow
thank you
Sure thing
last related question here if Stripe not have that information that the SDK send because was made via server, it makes Radar less accurate or more likely to recommend a request to 3d secure?
Not really relevant to 3DS exactly, but yeah if you aren't using the SDK then less fraud signals are picked up.
ok ok thanks!